bridge pattern

1. Bridge pattern

2. Bridge pattern
Purpose:
- Decouple an abstraction from its
implementation so that they can vary
independently.

3. Bridge pattern
Motivation:
- Inheritance binds an implementation to
the abstraction permanently.

4. Bridge pattern

5. Bridge pattern
Applicability:
- Need to avoid a permanent binding between an
abstraction and implementation.
- When abstractions and implementations should be
extensible through subclassing.
- When implementation changes should not impact
clients.

6. Bridge pattern

7. Bridge pattern

8. Bridge pattern

9. Bridge pattern

10. Bridge pattern
Consequences:
- Decouples interface and implementation.
- Improves extensibility.
- Related patterns:
- Abstract factory
- Adapter