Java Singleton Pattern - Best Ways to Implement Singleton in Java

🎓 Top 15 Udemy Courses (80-90% Discount): My Udemy Courses - Ramesh Fadatare — All my Udemy courses are real-time and project oriented courses.

▶️ Subscribe to My YouTube Channel (178K+ subscribers): Java Guides on YouTube

▶️ For AI, ChatGPT, Web, Tech, and Generative AI, subscribe to another channel: Ramesh Fadatare on YouTube

Introduction

The Singleton Design Pattern is one of the most commonly used creational design patterns in Java. At its core, it ensures that only one instance of a class exists throughout the application and provides a global access point to that instance.

Although this pattern seems simple, implementing it correctly—especially in multi-threaded and distributed environments—requires careful consideration.

Why Use the Singleton Pattern?

Resource Management: Ideal for scenarios like database connections, logging, caching, and configuration settings.
Global Access Point: Ensures a single, consistent instance across the application.
Performance Optimization: Reduces overhead by reusing the same instance instead of creating multiple objects.

Common Pitfalls of Singleton Pattern

Many developers make mistakes while implementing Singleton, leading to performance issues, security vulnerabilities, and broken design principles. These include:

✅ Using synchronized methods unnecessarily, leading to performance bottlenecks.
✅ Ignoring serialization issues, causing multiple instances on deserialization.
✅ Not handling reflection and cloning attacks, which can break the Singleton guarantee.

Let’s dive into the right ways to implement Singleton in Java.

Best Ways to Implement Singleton in Java

1. Eager Initialization (Simple but Memory-Heavy)

This is the simplest approach where the instance is created at class loading.

public class EagerSingleton {
    
    // Singleton instance is created eagerly
    private static final EagerSingleton INSTANCE = new EagerSingleton();

    // Private constructor prevents instantiation
    private EagerSingleton() {}

    // Public method to access the instance
    public static EagerSingleton getInstance() {
        return INSTANCE;
    }
}

Pros & Cons

✔ Thread-safe by default.
✔ No additional synchronization is required.
❌ Memory inefficient if the instance is never used.

2. Static Block Initialization (Handles Exceptions)

This approach is similar to eager initialization but allows exception handling.

public class StaticBlockSingleton {

    private static final StaticBlockSingleton INSTANCE;

    static {
        try {
            INSTANCE = new StaticBlockSingleton();
        } catch (Exception e) {
            throw new RuntimeException("Exception while creating singleton instance", e);
        }
    }

    private StaticBlockSingleton() {}

    public static StaticBlockSingleton getInstance() {
        return INSTANCE;
    }
}

Pros & Cons

✔ Handles exceptions during initialization.
❌ Still creates the instance at class loading, leading to unnecessary memory use.

3. Lazy Initialization (Not Thread-Safe)

Creates the instance only when needed.

public class LazySingleton {

    private static LazySingleton instance;

    private LazySingleton() {}

    public static LazySingleton getInstance() {
        if (instance == null) {
            instance = new LazySingleton();
        }
        return instance;
    }
}

Pros & Cons

✔ Efficient memory usage—instance is created only when needed.
❌ Not thread-safe! Multiple threads might create multiple instances.

4. Thread-Safe Singleton (Using Synchronized Method)

Adding synchronized makes it thread-safe, but it comes at a cost.

public class ThreadSafeSingleton {

    private static ThreadSafeSingleton instance;

    private ThreadSafeSingleton() {}

    public static synchronized ThreadSafeSingleton getInstance() {
        if (instance == null) {
            instance = new ThreadSafeSingleton();
        }
        return instance;
    }
}

Pros & Cons

✔ Ensures only one instance is created, even in multi-threaded environments.
❌ Slow performance due to method-level synchronization.

5. Double-Checked Locking (Best Performance for Multithreading)

This is the optimized version that reduces synchronization overhead.

public class DoubleCheckedLockingSingleton {

    private static volatile DoubleCheckedLockingSingleton instance;

    private DoubleCheckedLockingSingleton() {}

    public static DoubleCheckedLockingSingleton getInstance() {
        if (instance == null) {  // First check (no lock)
            synchronized (DoubleCheckedLockingSingleton.class) {
                if (instance == null) { // Second check (with lock)
                    instance = new DoubleCheckedLockingSingleton();
                }
            }
        }
        return instance;
    }
}

Pros & Cons

✔ High performance, as synchronization is done only once.
✔ Ensures thread safety with the volatile keyword.

6. Bill Pugh Singleton (Best Practice)

This method leverages Java’s class-loading mechanism for lazy initialization without synchronization overhead.

public class BillPughSingleton {

    private BillPughSingleton() {}

    private static class SingletonHelper {
        private static final BillPughSingleton INSTANCE = new BillPughSingleton();
    }

    public static BillPughSingleton getInstance() {
        return SingletonHelper.INSTANCE;
    }
}

Pros & Cons

✔ Best performance—no synchronization required.
✔ Lazy initialization & thread safety guaranteed.

7. Enum Singleton (Ultimate Protection)

Using enum prevents reflection and serialization attacks.

public enum EnumSingleton {
    INSTANCE;

    public void showMessage() {
        System.out.println("Singleton using Enum!");
    }
}

Pros & Cons

✔ Safe from reflection and serialization issues.
✔ Thread-safe by default.
❌ Less flexible, as enum doesn’t allow lazy initialization.

Singleton Pitfalls and How to Fix Them

1. Preventing Reflection Attack

Reflection can break Singleton by calling the private constructor.
✅ Fix: Throw an exception if the instance already exists.

public class ReflectionSafeSingleton {

    private static ReflectionSafeSingleton instance;

    private ReflectionSafeSingleton() {
        if (instance != null) {
            throw new RuntimeException("Use getInstance() method to create");
        }
    }

    public static ReflectionSafeSingleton getInstance() {
        if (instance == null) {
            instance = new ReflectionSafeSingleton();
        }
        return instance;
    }
}

2. Preventing Serialization Attack

By default, deserialization creates a new instance, breaking Singleton.
✅ Fix: Implement readResolve().

protected Object readResolve() {
    return getInstance();
}

Final Thoughts

The Singleton pattern is useful but must be implemented correctly to avoid common pitfalls.

Best Singleton Implementations

For Performance & Thread Safety → Bill Pugh Singleton
For Security → Enum Singleton
For Lazy Loading with Multi-threading → Double-Checked Locking Singleton

Key Takeaways

✔ Avoid synchronized methods due to performance overhead.
✔ Ensure proper serialization handling to prevent multiple instances.
✔ Reflection and cloning can break Singleton—handle them properly.
✔ Use Enum Singleton where possible—it’s the most secure and efficient.

Following these best practices, you can implement a secure, high-performance, and scalable Singleton in Java. Happy Coding! 🚀

My Top and Bestseller Udemy Courses. The sale is going on with a 70 - 80% discount. The discount coupon has been added to each course below:

Spring Boot + RabbitMQ Course - The Practical Guide