Regarding static holder singleton pattern

Solution 1:

This pattern is beneficial for at least 3 reasons:

1. Static factory
2. Lazy initialization
3. Thread safe

The JVM defers initializing the InstanceHolder class until it is actually used, and because the Singleton is initialized with a static initializer, no additional synchronization is needed. The first call to getInstance by any thread causes InstanceHolder to be loaded and initialized, at which time the initialization of the Singleton happens through the static initializer.

Static holder pattern is also considered as the smartest replace for Double-check-locking antipattern.

Solution 2:

This is a way to make a thread-safe lazy singleton by exploiting the way how JVM loads classes. You can read more about why and how to correctly implement it in Bloch's Effective Java book.

Remember, that from the testable code point of view singletons (and global state in general) are not beneficial and should be avoided.