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: 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

Why Do Employers Lie In Interviews?

This is a very common subject that many of us have already experienced. But when you realize that half of what has been said at interviews is actually a lie, you are already at least six months in the company, you have already started some project and it wouldn’t be appropriate to leave the company at that moment. Why is this happening? First of all, let us see how the usual interview process looks like in software development companies. First round interview in most of these companies is an interview with HR. This is the first insight about the company. A person who works in HR is usually someone who, in most cases, doesn’t understand what the software is and how the software development process goes. Big respect to those companies where HR knows these things. This phase usually contains some standard questions about your personality, what do you like about the company, how this company is something that you are actually looking for, where you see yourself in five/ten  years etc… ...
Post a Comment
Read more