Use Case in case of failure, make sure that the failed service doesn’t affect the entire system that can happen if the volume of calls to the failing service is high, and for each call we would need to wait for a timeout to occur before moving on making the call to the failed service and waiting would use resources … More The Circuit Breaker design pattern
I strongly believe that every good software engineer should now the value coming from Dependency Inversion principle – it allows on writing better code which is easier to short – just shortly speaking. And in general, you can follow it without any IoC container, framework, implementation like Google Guice and Spring IoC. But as it’s harder, … More Using Spring Framework wisely …
Are you using IoC ? If yes, do you know the answer on the question: where should we compose object graphs? If not, take a look on Mark Seemann article which is explaining the Composition Root pattern.
If you have some technology (ADO.NET/NHibernate/WCF/etc.. ) related components in your project and you wish to decouple other layer from that but many, many lines, APIs exist in whole product, there is the super pattern for you. Yes, it is simple and well-known pattern with simple name – Adapter. You can encapsulate existing APIs in … More Design Patterns after few years – Adapter, Factory Method, Factory
Decorator Pattern Another Example Proxy Pattern Bridge Pattern Composite Pattern Flyweight Pattern Adapter Pattern Two Way Adapter Pattern Pluggable Adapter Pattern Facade Pattern Prototype Pattern Factory Method Pattern Singleton Pattern Generic Singleton Pattern Abstract Factory Pattern Builder Pattern Strategy Pattern State Pattern Template Method Pattern Chain Of Responsibility Pattern Command Pattern Iterator Pattern Mediator Pattern … More C# Design Patterns Tour