Singleton Design Pattern || Implementation with Eager & Lazy Loading ✌🏻 

Very knowledgeable lecture. Thank u so much.

Very important concept😍❤ Thank you🙏

Thank you for sharing this concept video, it’s so important you made it easy to understand 😊

There are two null checks inside the getInstance() method because it is possible for the instance variable to be null even after the synchronized block. This can happen if two threads enter the synchronized block at the same time. The first thread will check if the instance variable is null, and if it is, it will create a new instance of the Singleton class. However, before the first thread can assign the new instance to the instance variable, the second thread may also enter the synchronized block and check if the instance variable is null. If it is, the second thread will also create a new instance of the Singleton class. This would result in two instances of the Singleton class being created, which is not desired.

Does that mean that we reduce the 4 lines each time when we use a lazy block

is that double null check important?