Skip to main content

Design Patterns: Singleton

Tyipically the first design pattern most people learn, often wrongly ☺ To give an introduction, we can say that singleton is one of the creational design patterns which ensures only one class instance with single point of access thru entire application. 

Because it is relatively simple to implement, the Singleton pattern is sometimes misapplied in situations where it is not the most suitable choice.


When to use it?

Here are the few examples of corrent usage of singleton:

  • Configuration Management Centralized configuration settings for consistent use thru entire application
  • Caching Maintaning Single istance of cached objects for easy and fast acces
  • Logging Ensure unified mechanism to avoid duplication of log files, formats, etc
  • Global State Management Centralized management of the state which is needed to be shared accross the application
  • Resource sharing Thread pools, database connection, I/O operations


When not to use it?

On the other hand, here are few examples on when  NOT to use it:

  • When you have multiple instances of the application by infrastructure design. Here you need to be careful because in most cases it won't behave as expected, because every process will have its own instance.
  • When you can solve problem easy without overcomplicating. Strive to keep your design as simple as possible and avoid unnecessary complexity.
  • When by design you need stateless service. Here singleton does more harm than help
  • When application needs to overwrite initialization parameters frequently. This is clear sign to not use it in this place.

  • High cuncerrency systems. Here, singleton instance can become bottleneck and actually be missused in order to keep it synced all the time.

Code Example

Here, we will give a thread safe C# implementation of the pattern.
public sealed class Singleton
{
    private static Singleton _instance;
    private static readonly object _lock = new object();
    private Singleton()
    {
        // initialization code
    }

    public static Singleton Instance
    {
        get
        {
            if (_instance == null)
            {
                lock (_lock)
                {
                    if (_instance == null)
                    {
                        _instance = new Singleton();
                    }
                }
            }
            return _instance;
        }
    }

    public void Hello()
    {
        Console.WriteLine("Hello from singleton.");
    }
}

class Program
{
    static void Main(string[] args)
    {
        Singleton.Instance.Hello();
    }
}

Labels:

Comments

Post a Comment

Popular posts from this blog

Design Patterns: Strategy

The Strategy Pattern is a behavioral design pattern that defines a family of algorithms, encapsulates each one, and makes them interchangeable. This pattern allows the algorithm to be selected at runtime, providing flexibility in designing software. It’s particularly useful when you have multiple ways of performing a task, and you want to choose the implementation dynamically without altering the client code. When To Use It? You Have Multiple Algorithms or Behaviors. Use it when you have a need for muplitple ways of performing a task, and you want to make these implementations interchangeable. Examples: Different sorting algorithms, payment methods, discount calculations... You Want to Eliminate Conditional Logic.  If you find yourself writing large if-else or switch statements to decide which algorithm to use, this pattern can simplify and clean up your code. Examples: A game character with different attack styles  You Need Runtime Flexibility.  Use this pattern if the ...
Post a Comment
Read more

Design Patterns: Builder

This is also, like a Singleton , one of the creational design patterns. It provides the way of creating complex objects step by step by simple chaining and every particular step is independent of other steps. Let us dive into the real example of usage. For showing purpose we have created an example in C# which creates simple SQL queries using described pattern.  using System; using System.Text; namespace BuilderPatternExample { public interface ISqlQueryBuilder { ISqlQueryBuilder Select(string columns); ISqlQueryBuilder From(string table); ISqlQueryBuilder Where(string condition); ISqlQueryBuilder OrderBy(string columns); string Build(); } public class SelectQueryBuilder : ISqlQueryBuilder { private readonly StringBuilder _queryBuilder; public SelectQueryBuilder() { _queryBuilder = new StringBuilder(); } public ISqlQueryBuilder Select(string columns) { ...
Post a Comment
Read more