Adapter Pattern
It is about making two interfaces that are not compatible, compatible.
Facade Pattern
It is about taking a bunch of complex interactions and creating a single interface that you can use instead of dealing with all those complex objects and complex interactions.
Proxy Pattern
It is placed between the client and something that you want to call. So instead of calling
A method directly, you call the proxy who calls that method.
Bridge Pattern
It works with separate hierarchies that can be expanded independently
with one hierarchy containing a reference to another
Decorator Pattern
It is a way of adding behaviour to a class without changing the class.
Client
This module contains the existing business logic of the program
IAdapter
This module describes a protocol that other modules must follow to be able to collaborate with the
client code.
Product
This module provides a service. The client cannot use it directly because it has an incompatible
interface
Adapter
This module can work with both the client and the service: it implements the client interface,
while wrapping the service object.
Adapter Pattern Statements
-You can separate the interface or data conversion code from the primary business logic of the program
-You need to introduce a set of new interfaces and classes.
Bridge Pattern Statements
- You can create platform-independent classes and apps.
- The client code works with high-level abstractions. It is not exposed to the platform details.
- You can introduce new abstractions and implementations independently from each other.
- You can focus on high-level logic in the abstraction and on platform details in the
implementation. - Since we can change the reference to the implementer in the abstraction, we are able to change the
implementer at run-time - We apply the pattern to a highly cohesive class.
