When we define a class as static, as soon as application is ready, instance of this class gets created by the CLR. Hence
Application will create instance of the class irrespective of consumption of it.
Memory allocation for static object falls under Generation 2. Hence garbage collector does not clean memory even when it’s not used.
Static does not support inheritance.
where as if we go for Singleton design pattern,
Instance gets created in memory when the application requests first time for it’s instance.
As application creates instance on demand, memory performance is better compare to static.
We can inherit singleton class .
To discuss just the differences:
Static is a keyword while Singleton concept is a design pattern
Fundamental difference is that Singleton gives you an object while static classes proved static methods(methods decorated with static keyword).
Singleton is a creational pattern with only single instance of the class, it can implement interfaces, inherit from other classes and aligns with object oriented concepts. While using static can restrict usage of inheritance and some OOPS concepts.
Also that singleton can be passed as a reference too and supports object disposal.
Also to be noted that static objects can be used part of singleton pattern to help maintain global object. In addition singleton concept can include lazy loading, thread safety and encapsulation.
Welcome for any new inputs or additions
A singleton allows a class for which there is just one, persistent instance across the lifetime of an application. A Singleton can implement interfaces, inherit from other classes and allow inheritance. A static class allows only static methods and and you cannot pass static class as parameter.
~~When we define a class as static, as soon as application is ready, instance of this class gets created by the CLR. Hence
Application will create instance of the class irrespective of consumption of it.Static class instance doesn’t create till it’s any property or method doesn’t call