Implementing the singleton pattern in Java

by

Before going the singleton route, reconsider. Do you really need a singleton? If you’re asking for scenarios when you need to implement singletons, it’s because the need for them didn’t really express. You’re better off not introducing singletons in your code base just because it feels cool to follow design patterns.

Clean Code Talks – Global State and Singletons

Once Is Not Enough

Performant Singletons

However, what’s really worth knowing is Dependency Injection.

Now if you really want to implement singletons in Java, I would recommend Joshua Bloch’s “Effective Java” way of implementing them:

public class Singleton
{
  public static Singleton getInstance() {
    return SingletonHolder.instance;
  }

  private Singleton() {}

  private static final class SingletonHolder {
    static final Singleton instance = new Singleton();    
  }
}

The JLS guarantees the JVM will not initialize instance until someone calls getInstance();

Final note, the Double Checked Locking Pattern is broken in Java up to Java 5. The Java 5 memory model makes the DCL pattern thread safe but it makes it slower than the SingletonHolder class method while the original intent was performance optimization.

EDIT: As @Luno pointed out, since the second edition of the book, the preferred way is:

As of release 1.5, there is a third approach to implementing singletons. Simply make an enum type with one element:

// Enum singleton - the preferred approach
public enum Elvis {
    INSTANCE;

    public void leaveTheBuilding() { ... }
}

This approach is functionally equivalent to the public field approach, except that it is more concise, provides the serialization machinery for free, and provides an ironclad guarantee against multiple instantiation, even in the face of sophisticated serialization or reflection attacks. While this approach has yet to be widely adopted, a single-element enum type is the best way to implement a singleton.

More Related Contents:

  1. What is an efficient way to implement a singleton pattern in Java? [closed]
  2. Setting Singleton property value in Firebase Listener
  3. Why is volatile used in double checked locking
  4. Implementing Singleton with an Enum (in Java)
  5. What is the best approach for using an Enum as a singleton in Java?
  6. Singleton design pattern vs Singleton beans in Spring container
  7. Using Singleton design pattern for SQLiteDatabase
  8. Singleton class with several different classloaders
  9. What’s Alternative to Singleton
  10. Singleton with Arguments in Java
  11. Thread safe multitons in Java
  12. Singleton Design Pattern: Pitfalls [closed]
  13. Java Singleton and Synchronization
  14. Why implementing a Singleton pattern in Java code is (sometimes) considered an anti-pattern in Java world?
  15. Is spring default scope singleton or not?
  16. How to mock an enum singleton class using Mockito/Powermock?
  17. Using different classloaders for different JUnit tests?
  18. Android: Cannot perform this operation because the connection pool has been closed
  19. should a db connection be a singleton?
  20. Singleton across JVM or Application instance or Tomcat instance
  21. Get application context from non activity singleton class
  22. Java Singleton Pattern
  23. Why use a singleton instead of static methods?
  24. When would the garbage collector erase an instance of an object that uses Singleton pattern?
  25. Java serialization: readObject() vs. readResolve()
  26. How to create a singleton class
  27. Static references are cleared–does Android unload classes at runtime if unused?
  28. Accessing scala.None from Java
  29. Pattern for lazy thread-safe singleton instantiation in java
  30. Singleton Object in Java Web service

Leave a Comment