Singleton pattern

In software engineering, the singleton pattern is a software design pattern that restricts the instantiation of a class to one "single" instance. This is useful when exactly one object is needed to coordinate actions across the system. The term comes from the mathematical concept of a singleton.

Critics consider the singleton to be an anti-pattern in that it is frequently used in scenarios where it is not beneficial, introduces unnecessary restrictions in situations where a sole instance of a class is not actually required, and introduces global state into an application.[1][2][3]


The singleton[4] design pattern is one of the twenty-three well-known "Gang of Four" design patterns that describe how to solve recurring design problems to design flexible and reusable object-oriented software, that is, objects that are easier to implement, change, test, and reuse.

The singleton design pattern solves problems like:[5]

  • How can it be ensured that a class has only one instance?
  • How can the sole instance of a class be accessed easily?
  • How can a class control its instantiation?
  • How can the number of instances of a class be restricted?

The singleton design pattern describes how to solve such problems:

  • Hide the constructor of the class.
  • Define a public static operation (getInstance()) that returns the sole instance of the class.

The key idea in this pattern is to make the class itself responsible for controlling its instantiation (that it is instantiated only once).
The hidden constructor (declared private) ensures that the class can never be instantiated from outside the class.
The public static operation can be accessed easily by using the class name and operation name (Singleton.getInstance()).

Common uses

  • The abstract factory, builder, and prototype patterns can use singletons in their implementation.
  • Facade objects are often singletons because only one facade object is required.
  • State objects are often singletons.
  • Singletons are often preferred to global variables because:
    • They do not pollute the global namespace (or, in languages with nested namespaces, their containing namespace) with unnecessary variables.[4]
    • They permit lazy allocation and initialization, whereas global variables in many languages will always consume resources.


An implementation of the singleton pattern must:

  • ensure that only one instance of the singleton class ever exists; and
  • provide global access to that instance.

Typically, this is done by:

The instance is usually stored as a private static variable; the instance is created when the variable is initialized, at some point before the static method is first called. The following is a sample implementation written in Java.

public final class Singleton {

    private static final Singleton INSTANCE = new Singleton();

    private Singleton() {}

    public static Singleton getInstance() {
        return INSTANCE;

C# implementation

public sealed class Singleton {

    private static readonly Singleton INSTANCE = new Singleton();

    private Singleton() {}

    public static Singleton Instance {
        get {
            return INSTANCE;

In C# you can also use static classes to create singletons, where the class itself is the singleton.

public static class Singleton {

    private static readonly MyOtherClass INSTANCE = new MyOtherClass();

    public static MyOtherClass Instance {
        get {
            return INSTANCE;

Lazy initialization

A singleton implementation may use lazy initialization, where the instance is created when the static method is first invoked. If the static method might be called from multiple threads simultaneously, measures may need to be taken to prevent race conditions that could result in the creation of multiple instances of the class. The following is a thread-safe sample implementation, using lazy initialization with double-checked locking, written in Java.[lower-alpha 1]

public final class Singleton {

    private static volatile Singleton instance = null;

    private Singleton() {}

    public static Singleton getInstance() {
        if (instance == null) {
            synchronized(Singleton.class) {
                if (instance == null) {
                    instance = new Singleton();

        return instance;

Delphi and Free Pascal implementation

GetInstance is thread safe implementation of Singleton.

unit SingletonPattern;


  TTest = class sealed
  strict private
    FCreationTime: TDateTime;
    constructor Create;
    property CreationTime: TDateTime read FCreationTime;

function GetInstance: TTest;


  , SyncObjs

  FCriticalSection: TCriticalSection;
  FInstance: TTest;

function GetInstance: TTest;
    if not Assigned(FInstance) then
      FInstance := TTest.Create;

    Result := FInstance;

constructor TTest.Create;
  inherited Create;
  FCreationTime := Now;

  FCriticalSection := TCriticalSection.Create;




procedure TForm3.btnCreateInstanceClick(Sender: TObject);
  i: integer;
  for i := 0 to 5 do


  1. In Java, to avoid the synchronization overhead while keeping lazy initialization with thread safety, the preferred approach is to use the initialization-on-demand holder idiom.


  1. Scott Densmore. Why singletons are evil, May 2004
  2. Steve Yegge. Singletons considered stupid, September 2004
  3. Clean Code Talks - Global State and Singletons
  4. Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides (1994). Design Patterns: Elements of Reusable Object-Oriented Software. Addison Wesley. pp. 127ff. ISBN 0-201-63361-2.CS1 maint: multiple names: authors list (link)
  5. "The Singleton design pattern - Problem, Solution, and Applicability". Retrieved 2017-08-16.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.