Design Patterns

Design patterns help us to create robust applications by solving common problems using known and proven solutions.

The Adapter design pattern works when you have different or incompatible interfaces, and you need the client to use both in the same way.

The Adapter design pattern says in its definition that it converts an interface or class into another interface that the client needs.

The Builder design pattern allows you to create objects that are usually complex using another object that builds them step by step.

The Composite design pattern allows you to create objects from an interface by making them all similar and allowing them all to be treated in the same way.

The Decorator pattern allows you to add new features to classes without modifying their structure.

The Facade design pattern simplifies the complexity of a system through a simpler interface.

It improves access to our system by allowing other systems or subsystems to use a common access point that reduces complexity, minimizing interactions and dependencies.

The Factory design pattern is mainly used when we have a class or interface with many subclasses or implementations, and according to some input, we need to return one of these specific subclasses.

The Observer’s design pattern is used primarily when we are interested in any change of status being notified to anyone who needs to know about that change.

In the observer design pattern, the object that looks at the state of another object is called “Observer” and the object that is “looking” those changes is called “Subject”.

The Proxy design pattern is simply an intermediary that is designed over a class to add some additional functionality, without modifying the original class.

This is one of the best-known patterns and is perhaps the first that comes to mind when you ask us about design patterns in Java.

The goal is to have only one instance of a class involved and ensure that this happens every time this instance is needed.