Connect with me
The Bridge Design Pattern is a structural pattern that decouples an abstraction from its implementation so that both can vary independently. It is commonly used when a class grows in two orthogonal dimensions and inheritance alone cannot prevent the explosion of subclasses.
The Flyweight pattern is one of the most resource-conscious patterns in existence. While the Singleton pattern was created to ensure a single instance of a class exists, the Flyweight pattern was created to handle millions of instances without crashing your memory.
The Decorator Design Pattern allows us to attach additional responsibilities to an object at runtime while keeping the original object unchanged. In other words, the pattern promotes flexible behavior extension without subclassing.
The Proxy pattern provides a substitute for another object, controlling access and allowing additional functionality before or after requests reach the original object; useful for lazy loading, security, and resource management.Retry
The Facade Design Pattern simplifies complex systems by providing a unified interface. It hides intricate operations behind a clean layer, making code easier to use, maintain, and extend without exposing internal details.
The Composite Design Pattern allows objects to be organized in a tree hierarchy, enabling uniform treatment of individual and grouped elements.
Adapter pattern enables integration of new interfaces with existing implementations, allowing reuse of legacy code without rewriting them for newer interfaces.
The Factory pattern is the second most commonly used design pattern. It is based on the idea that we can create objects of a common super type, while allowing their actual implementations to differ in subsequent subclasses.
The Prototype Design Pattern is a creational pattern that lets us create new objects by cloning existing ones instead of instantiating them from scratch.
The Builder pattern helps create complex objects step-by-step while keeping them immutable and enforcing any required rules. It avoids messy constructors, makes code more readable, and is perfect when you have both required and optional fields.
