Bridge Pattern

Bridge is useful when one inheritance tree is trying to represent two different reasons to change.

In Java, that often appears when an abstraction such as Notification, Report, or DeviceCommand must support multiple operational back ends such as email, SMS, PDF, REST, or hardware drivers. If those concerns stay fused, subclass growth becomes predictable and painful.

Bridge separates the abstraction side from the implementation side so each can evolve on its own. That makes the pattern more architectural than adapter. Adapter translates one awkward dependency. Bridge deliberately designs two dimensions of variation from the start.

In this section

• Implementing Bridge in Java
  Implement the Bridge pattern in Java by separating the abstraction your clients use from the implementation family that actually does the work.
• Decoupling Abstraction and Implementation
  Understand why the Bridge pattern separates client-facing abstractions from implementation details in Java and when that split is worth the complexity.
• Bridge Pattern vs. Adapter Pattern
  Compare Bridge and Adapter in Java so interface translation and two-axis abstraction design do not get confused.
• Bridge Pattern Use Cases and Examples in Java
  See where the Bridge pattern fits in Java systems, especially where abstraction and platform or transport concerns evolve separately.