Singleton is also a very popular design pattern, although when not used appropriately it does become an anti- pattern. It is used when we need an object to be unique and easily accessible from all parts of the application e.g. database handler or loggers are frequently used. It is often considered an anti-pattern because is a pain in the ass to test, but not impossible.
Let's start with the implementation and then we'll go into testing. In order to create a singleton:
- Create a singleton class
X - Make its constructor private (so that clients cannot instantiate it)
- Add a private static member of type
Xthat holds a reference to the unique instance - Add a public static
X getInstance()method that create the unique instance (lazily and returns it)
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
public class X { private static X instance { get;set;} private X() { } public static X Instance { get { if(instance == null) { instance = new X(); } return instance; } } } |