Singleton over static class

Question

When would you prefer singleton over static class? Please give a real world example with proper reasoning.

Anil Kumar · Answer

Polymorphism, OO, i don't think are heavy words anymore.. Below I have provided some scenarios below where you can apply the both Use static classes where you have bunch of similar functions like math class for add, subtract, multiply, divide etc.. We normally use static classes for helper classes or similar utilities classes where we can't afford to initial the class each time we want to use the function. Singelton - Use singelton where you want instance of a object to be globally available to all users. You can you singelton in Thread pools, SQL Connection Pools, Registry objects, Objects handling user preferences, Caches, Factory classes, Builder classes and Statistics utilities like a hit counter etc..

Ramesh Maruthi · Answer

Hi Vineet : http://www.c-sharpcorner.com/UploadFile/akkiraju/singleton-vs-static-classes/ http://dotnet.dzone.com/news/c-singleton-pattern-vs-static-

Riddhi Valecha · Answer

Hi... http://www.c-sharpcorner.com/UploadFile/e70b61/real-example-of-singleton-design-pattern/

Vineet Kumar · Answer

Hi Anil I appreciate your response, but as said in question, I need a real world example where you can apply these concepts. The heavy weight words (such as polymorphism, OO blah blah) are not something I am looking for :)

Anil Kumar · Answer

Main advantage of Singleton over static is that former is more object oriented than later. With Singleton, you can use Inheritance and Polymorphism to extend a base class, implement an interface and capable of providing different implementations So, When you need a class with full OO capability , chose Singleton, while if you just need to store bunch of static methods together, than use static class