Benefits of the Java Collections Framework

The Java Collections Framework provides the following benefits:

• Reduces programming effort: By providing useful data structures and algorithms, the Collections Framework frees you to concentrate on the important parts of your program rather than on the low-level "plumbing" required to make it work. By facilitating interoperability among unrelated APIs, the Java Collections Framework frees you from writing adapter objects or conversion code to connect APIs.
• Increases program speed and quality: This Collections Framework provides high-performance, high-quality implementations of useful data structures and algorithms. The various implementations of each interface are interchangeable, so programs can be easily tuned by switching collection implementations. Because you're freed from the drudgery of writing your own data structures, you'll have more time to devote to improving programs' quality and performance.
• Allows interoperability among unrelated APIs: The collection interfaces are the vernacular by which APIs pass collections back and forth. If my network administration API furnishes a collection of node names and if your GUI toolkit expects a collection of column headings, our APIs will interoperate seamlessly, even though they were written independently.
• Reduces effort to learn and to use new APIs: Many APIs naturally take collections on input and furnish them as output. In the past, each such API had a small sub-API devoted to manipulating its collections. There was little consistency among these ad hoc collections sub-APIs, so you had to learn each one from scratch, and it was easy to make mistakes when using them. With the advent of standard collection interfaces, the problem went away.
• Reduces effort to design new APIs: This is the flip side of the previous advantage. Designers and implementers don't have to reinvent the wheel each time they create an API that relies on collections; instead, they can use standard collection interfaces.
• Fosters software reuse: New data structures that conform to the standard collection interfaces are by nature reusable. The same goes for new algorithms that operate on objects that implement these interfaces.

Who is Raghuram Rajan?

Raghuram Rajan, Chief Economic Advisor in the finance ministry, has been appointed as the next governor of the Reserve Bank of India, becoming the 23rd Governor of the central bank.

Born into a Tamil family in Bhopal, he is a former alumni of IIM-Ahmedabad, IIT-Delhi and MIT. He was a professor at the University of Chicago's Booth School of Business before being appointed as the youngest-ever Economic Counselor and Director of Research at the International Monetary Fund from October 2003 to December 2006. 

Spring's bean (Singleton Objects) are thread safe?

Consider we are using Singleton Object for Dependency Injection in our Service Class. 

By default, we need to make sure, 

•       the singleton object are threadsafe and 
•       it is immutable Object.

But during our coding, we are not considering any of the above points in our development. We let the spring to create the bean and simply we are using it(reference).

Does the spring has his design to take care of this threadSafe?.

At which scenario, we would need to explicitly take care of Synchronized operation?.