The bridge pattern is a design pattern used in software engineering that is meant to "decouple an abstraction from its implementation so that the two can vary independently", introduced by the Gang of Four. The bridge uses encapsulation, aggregation, and can use inheritance to separate responsibilities into different classes. When a class varies often, the features of object-oriented programming become very useful because changes to a program's code can be made easily with minimal prior knowledge about the program. The bridge pattern is useful when both the class and what it does vary often. The class itself can be thought of as the abstraction and what the class can do as the implementation. The bridge pattern can also be thought of as two layers of abstraction. When there is only one fixed implementation, this pattern is known as the Pimpl idiom in the C++ world. The bridge pattern is often confused with the adapter pattern, and is often implemented using the object adapter pattern; e.g., in the Java code below. Variant: The implementation can be decoupled even more by deferring the presence of the implementation to the point where the abstraction is utilized.

Overview

The Bridge design pattern is one of the twenty-three well-known GoF design patterns that describe how to solve recurring design problems to design flexible and reusable object-oriented software, that is, objects that are easier to implement, change, test, and reuse. What problems can the Bridge design pattern solve? When using subclassing, different subclasses implement an abstract class in different ways. But an implementation is bound to the abstraction at compile-time and cannot be changed at run-time. What solution does the Bridge design pattern describe? This enables to configure an with an object at run-time. See also the Unified Modeling Language class and sequence diagram below.

Structure

UML class and sequence diagram

In the above Unified Modeling Language class diagram, an abstraction is not implemented as usual in a single inheritance hierarchy. Instead, there is one hierarchy for an abstraction and a separate hierarchy for its implementation, which makes the two independent from each other. The interface is implemented in terms of (by delegating to) the interface. The UML sequence diagram shows the run-time interactions: The object delegates implementation to the object (by calling on ), which performs the operation and returns to.

Class diagram

Example

C#

Bridge pattern compose objects in tree structure. It decouples abstraction from implementation. Here abstraction represents the client from which the objects will be called. An example implemented in C# is given below The Bridge classes are the Implementation that uses the same interface-oriented architecture to create objects. On the other hand, the abstraction takes an instance of the implementation class and runs its method. Thus, they are completely decoupled from one another.

Crystal

Output API1.circle at 1.0:2.0 - radius: 3.075 API2.circle at 5.0:7.0 - radius: 11.275

C++

Output: API01.circle at 1.000000:2.000000 - radius: 3.075000 API02.circle at 5.000000:7.000000 - radius: 11.275000

Java

The following Java program defines a bank account that separates the account operations from the logging of these operations. It will output: info: withdraw 75 result true warning: withdraw 10 result true warning: withdraw 100 result false

PHP

Output: API1.circle at 1:3 radius 17.5 API2.circle at 5:7 radius 27.5

Scala

Python