Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.geeksforgeeks.org/system-design/singleton-design-pattern-in-java/ below:

Singleton Design Pattern in Java

Last Updated : 11 Jan, 2024

Singleton Design Pattern is a creational design pattern that ensures a class has only one instance and provides a global point of access to it. This pattern is particularly useful when exactly one object is needed to coordinate actions across the system.

Consider a scenario where you need to manage a configuration object for an application, and you want to ensure that there is only one instance of this configuration object throughout the system.

• Private Constructor: The Singleton class has a private constructor to prevent the instantiation of the class from external entities.
• Private Instance: The class contains a private static instance of itself.
• Static Method: A static method is provided to access the instance, and it ensures that only one instance is created if it doesn't exist.

Here, We are making SingleObject as an class, whereas SingleObject is behaving as like instance it will create private static instance, we will call the class in main and function we will create getInstance and showMessage, getInstance will return the object, showMessage will print the message.

Let's implement a Singleton class step by step in Java.

/*package whatever //do not write package name here */

import java.io.*;

public class Singleton {
    // Step 1: Private static instance
    private static Singleton instance;

    // Step 2: Private constructor
    private Singleton() {
        // Initialization, if needed
    }

    // Step 3: Static method to get the instance
    public static Singleton getInstance() {
        if (instance == null) {
            instance = new Singleton();
        }
        return instance;
    }
}

Use Case of Singleton:

• Database Connection Management: Ensuring a single connection instance throughout the application.
• Logger Classes: Managing a single logger instance to centralize log information.

Problem Statement: In a software application, managing database connections efficiently is crucial for performance. Creating a new database connection for each request can be resource-intensive and impact system performance. We want to ensure that there is only one instance of a database connection manager throughout the application to handle connections effectively.

Solution: Singleton Design Pattern

Identifying the Need:

• Problem: Excessive creation of database connection instances.
• Solution: Implement a Singleton to manage a single instance of the database connection manager.

Singleton Class Implementation (Java):

/*package whatever //do not write package name here */

import java.io.*;

public class DatabaseConnectionManager {
    private static DatabaseConnectionManager instance;

    private DatabaseConnectionManager() {
        // Private constructor to prevent external instantiation
    }

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

    // Additional methods for managing database connections...
}

Usage in the Application:

public class Application {
    public static void main(String[] args) {
        // Accessing the single instance of DatabaseConnectionManager
        DatabaseConnectionManager connectionManager = DatabaseConnectionManager.getInstance();
        // Using the connection manager to handle database connections...
    }
}

Explanation:

• The Singleton ensures there's only one instance of DatabaseConnectionManager.
• Any part of the application needing a database connection can access the single instance, promoting resource efficiency.

Advantages in this Use Case:

• Resource Efficiency: Ensures that only one instance of the connection manager exists, preventing the overhead of creating multiple connections.
• Centralized Management: All database-related activities can be managed centrally through the singleton instance.

Conclusion: The Singleton Design Pattern in this use case ensures efficient management of database connections, preventing unnecessary instantiation of connection managers and promoting a more streamlined and resource-efficient application.

1. Single Instance

• Advantage: Ensures that a class has only one instance.
• Explanation: This avoids unnecessary instantiation and guarantees that there's a single point of access to that instance.

2. Global Point of Access

• Advantage: Provides a global point of access to the instance.
• Explanation: Any part of the application can access the Singleton instance, promoting a centralized and easily reachable point for shared resources.

3. Lazy Initialization

• Advantage: Supports lazy initialization.
• Explanation: The instance is created only when it is needed for the first time, improving resource efficiency.

4. Efficient Resource Management

• Advantage: Efficiently manages resources.
• Explanation: In scenarios where creating multiple instances is resource-intensive, the Singleton pattern ensures optimal usage of resources.

5. Prevents Duplicate Configuration

• Advantage: Helps prevent duplicate configuration settings.
• Explanation: In scenarios where a single configuration should be maintained throughout the application, Singleton ensures that only one configuration instance exists.

1. Global State

• Disadvantage: Can introduce a global state in the application.
• Explanation: As a single instance is accessible globally, changes to its state can affect the entire application, potentially leading to unintended consequences.

2. Testing Challenges

• Disadvantage: Singleton can make unit testing challenging.
• Explanation: Since the Singleton instance is globally accessible, it can be difficult to isolate and test individual components independently.

3. Violates Single Responsibility Principle

• Disadvantage: Violates the Single Responsibility Principle.
• Explanation: The Singleton class is responsible for both managing its instance and its primary functionality, which can lead to a lack of separation of concerns.

4. Limited Extensibility

• Disadvantage: Can hinder extensibility.
• Explanation: Introducing subclasses or alternative implementations of the Singleton can be challenging without modifying the existing code.

5. Potential for Unintended Consequences

• Disadvantage: Changes to the Singleton instance can impact the entire application.
• Explanation: Modifying the state of the Singleton may have unintended consequences in other parts of the system due to its global accessibility.

The Singleton Design Pattern in Java ensures that a class has only one instance and provides a way to access it globally. While it solves the problem of having a single instance, it's essential to consider its use carefully, especially in multi-threaded environments, and weigh the advantages and disadvantages based on the specific application requirements.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4