Design Patterns: Singleton 

Design patterns are solutions to recurring problems; guidelines on how to tackle certain problems I have included implementations of some design patterns in C# to help beginners like me get their feet wet. 

This is the first of an eight part series where I am joined by Phil Japikse to discuss design patterns. A design pattern is a best practice you can use in your code to solve a common problem.  In this episode, Phil demonstrates the Command and Memento patterns. 

Episodes in this series:

• Command/Memento patterns (this episode)
• Strategy pattern
• Template Method pattern (to be published 7/20)
• Observer/Publish-Subscribe patterns (to be published 7/25)
• Singleton pattern (to be published 8/8)
• Factory patterns (to be published 8/10)
• Adapter/Facade patterns (to be published 8/15)
• Decorator pattern (to be published 8/17) 

Design patterns for microservices 

The Polly documentation has a great explanation of the circuit-breaker pattern  

Tech Debt Cleanup with nDepend  

Singleton design pattern is one of the simplest design patterns: it involves only one class throughout the application which is responsible to instantiate itself, to make sure it creates not more than one instance; in the same time it provides a global point of access to that instance. In this case the same instance can be used from everywhere, being impossible to invoke directly the constructor each time. 

Analyzing code quality of widely-known open-source projects 

- Developers LOVE complexity.
- Architects HATE complexity.