Bridge pattern

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. ^[1] 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. ^[1]

What problems can the Bridge design pattern solve? ^[2]

• An abstraction and its implementation should be defined and extended independently from each other.
• A compile-time binding between an abstraction and its implementation should be avoided so that an implementation can be selected at run-time.

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?

• Separate an abstraction (Abstraction) from its implementation (Implementor) by putting them in separate class hierarchies.
• Implement the Abstraction in terms of (by delegating to) an Implementor object.

This enables to configure an Abstraction with an Implementor object at run-time.
See also the Unified Modeling Language class and sequence diagram below.

Structure

UML class and sequence diagram

A sample UML class and sequence diagram for the Bridge design pattern.

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

Class diagram

Abstraction (abstract class)

defines the abstract interface

maintains the Implementor reference.

RefinedAbstraction (normal class)

extends the interface defined by Abstraction

Implementor (interface)

defines the interface for implementation classes

ConcreteImplementor (normal class)

implements the Implementor interface

Bridge in LePUS3 (legend)

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

// Helps in providing truly decoupled architecturepublicinterfaceIBridge{voidFunction1();voidFunction2();}publicclassBridge1:IBridge{publicvoidFunction1(){Console.WriteLine("Bridge1.Function1");}publicvoidFunction2(){Console.WriteLine("Bridge1.Function2");}}publicclassBridge2:IBridge{publicvoidFunction1(){Console.WriteLine("Bridge2.Function1");}publicvoidFunction2(){Console.WriteLine("Bridge2.Function2");}}publicinterfaceIAbstractBridge{voidCallMethod1();voidCallMethod2();}publicclassAbstractBridge:IAbstractBridge{publicIBridgebridge;publicAbstractBridge(IBridgebridge){this.bridge=bridge;}publicvoidCallMethod1(){this.bridge.Function1();}publicvoidCallMethod2(){this.bridge.Function2();}}

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

abstractclassDrawingAPIabstractdefdraw_circle(x:Float64,y:Float64,radius:Float64)endclassDrawingAPI1<DrawingAPIdefdraw_circle(x:Float,y:Float,radius:Float)"API1.circle at #{x}:#{y} - radius: #{radius}"endendclassDrawingAPI2<DrawingAPIdefdraw_circle(x:Float64,y:Float64,radius:Float64)"API2.circle at #{x}:#{y} - radius: #{radius}"endendabstractclassShapeprotectedgetterdrawing_api:DrawingAPIdefinitialize(@drawing_api)endabstractdefdrawabstractdefresize_by_percentage(percent:Float64)endclassCircleShape<Shapegetterx:Float64gettery:Float64getterradius:Float64definitialize(@x,@y,@radius,drawing_api:DrawingAPI)super(drawing_api)enddefdraw@drawing_api.draw_circle(@x,@y,@radius)enddefresize_by_percentage(percent:Float64)@radius*=(1+percent/100)endendclassBridgePatterndefself.testshapes=[]ofShapeshapes<<CircleShape.new(1.0,2.0,3.0,DrawingAPI1.new)shapes<<CircleShape.new(5.0,7.0,11.0,DrawingAPI2.new)shapes.eachdo|shape|shape.resize_by_percentage(2.5)putsshape.drawendendendBridgePattern.test

Output

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

C++

#include<iostream>#include<string>#include<vector>classDrawingAPI{public:virtual~DrawingAPI()=default;virtualstd::stringDrawCircle(floatx,floaty,floatradius)const=0;};classDrawingAPI01:publicDrawingAPI{public:std::stringDrawCircle(floatx,floaty,floatradius)constoverride{return"API01.circle at "+std::to_string(x)+":"+std::to_string(y)+" - radius: "+std::to_string(radius);}};classDrawingAPI02:publicDrawingAPI{public:std::stringDrawCircle(floatx,floaty,floatradius)constoverride{return"API02.circle at "+std::to_string(x)+":"+std::to_string(y)+" - radius: "+std::to_string(radius);}};classShape{public:Shape(constDrawingAPI&drawing_api):drawing_api_(drawing_api){}virtual~Shape()=default;virtualstd::stringDraw()const=0;virtualfloatResizeByPercentage(constfloatpercent)=0;protected:constDrawingAPI&drawing_api_;};classCircleShape:publicShape{public:CircleShape(floatx,floaty,floatradius,constDrawingAPI&drawing_api):Shape(drawing_api),x_(x),y_(y),radius_(radius){}std::stringDraw()constoverride{returndrawing_api_.DrawCircle(x_,y_,radius_);}floatResizeByPercentage(constfloatpercent)override{returnradius_*=(1.0f+percent/100.0f);}private:floatx_,y_,radius_;};intmain(intargc,char**argv){constDrawingAPI01api1{};constDrawingAPI02api2{};std::vector<CircleShape>shapes{CircleShape{1.0f,2.0f,3.0f,api1},CircleShape{5.0f,7.0f,11.0f,api2}};for(auto&shape:shapes){shape.ResizeByPercentage(2.5);std::cout<<shape.Draw()<<std::endl;}return0;}

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.

// Logger has two implementations: info and warning@FunctionalInterfaceinterfaceLogger{voidlog(Stringmessage);staticLoggerinfo(){returnmessage->System.out.println("info: "+message);}staticLoggerwarning(){returnmessage->System.out.println("warning: "+message);}}abstractclassAbstractAccount{privateLoggerlogger=Logger.info();publicvoidsetLogger(Loggerlogger){this.logger=logger;}// the logging part is delegated to the Logger implementationprotectedvoidoperate(Stringmessage,booleanresult){logger.log(message+" result "+result);}}classSimpleAccountextendsAbstractAccount{privateintbalance;publicSimpleAccount(intbalance){this.balance=balance;}publicbooleanisBalanceLow(){returnbalance<50;}publicvoidwithdraw(intamount){booleanshouldPerform=balance>=amount;if(shouldPerform){balance-=amount;}operate("withdraw "+amount,shouldPerform);}}publicclassBridgeDemo{publicstaticvoidmain(String[]args){SimpleAccountaccount=newSimpleAccount(100);account.withdraw(75);if(account.isBalanceLow()){// you can also change the Logger implementation at runtimeaccount.setLogger(Logger.warning());}account.withdraw(10);account.withdraw(100);}}

It will output:

info: withdraw 75 result true warning: withdraw 10 result true warning: withdraw 100 result false 

PHP

interfaceDrawingAPI{functiondrawCircle($x,$y,$radius);}classDrawingAPI1implementsDrawingAPI{publicfunctiondrawCircle($x,$y,$radius){echo"API1.circle at $x:$y radius $radius.\n";}}classDrawingAPI2implementsDrawingAPI{publicfunctiondrawCircle($x,$y,$radius){echo"API2.circle at $x:$y radius $radius.\n";}}abstractclassShape{protected$drawingAPI;publicabstractfunctiondraw();publicabstractfunctionresizeByPercentage($pct);protectedfunction__construct(DrawingAPI$drawingAPI){$this->drawingAPI=$drawingAPI;}}classCircleShapeextendsShape{private$x;private$y;private$radius;publicfunction__construct($x,$y,$radius,DrawingAPI$drawingAPI){parent::__construct($drawingAPI);$this->x=$x;$this->y=$y;$this->radius=$radius;}publicfunctiondraw(){$this->drawingAPI->drawCircle($this->x,$this->y,$this->radius);}publicfunctionresizeByPercentage($pct){$this->radius*=$pct;}}classTester{publicstaticfunctionmain(){$shapes=array(newCircleShape(1,3,7,newDrawingAPI1()),newCircleShape(5,7,11,newDrawingAPI2()),);foreach($shapesas$shape){$shape->resizeByPercentage(2.5);$shape->draw();}}}Tester::main();

Output:

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

Scala

traitDrawingAPI{defdrawCircle(x:Double,y:Double,radius:Double)}classDrawingAPI1extendsDrawingAPI{defdrawCircle(x:Double,y:Double,radius:Double)=println(s"API #1 $x$y$radius")}classDrawingAPI2extendsDrawingAPI{defdrawCircle(x:Double,y:Double,radius:Double)=println(s"API #2 $x$y$radius")}abstractclassShape(drawingAPI:DrawingAPI){defdraw()defresizePercentage(pct:Double)}classCircleShape(x:Double,y:Double,varradius:Double,drawingAPI:DrawingAPI)extendsShape(drawingAPI:DrawingAPI){defdraw()=drawingAPI.drawCircle(x,y,radius)defresizePercentage(pct:Double){radius*=pct}}objectBridgePattern{defmain(args:Array[String]){Seq(newCircleShape(1,3,5,newDrawingAPI1),newCircleShape(4,5,6,newDrawingAPI2))foreach{x=>x.resizePercentage(3)x.draw()}}}

Python

"""Bridge pattern example."""fromabcimportABCMeta,abstractmethodNOT_IMPLEMENTED="You should implement this."classDrawingAPI:__metaclass__=ABCMeta@abstractmethoddefdraw_circle(self,x,y,radius):raiseNotImplementedError(NOT_IMPLEMENTED)classDrawingAPI1(DrawingAPI):defdraw_circle(self,x,y,radius):returnf"API1.circle at {x}:{y} - radius: {radius}"classDrawingAPI2(DrawingAPI):defdraw_circle(self,x,y,radius):returnf"API2.circle at {x}:{y} - radius: {radius}"classDrawingAPI3(DrawingAPI):defdraw_circle(self,x,y,radius):returnf"API3.circle at {x}:{y} - radius: {radius}"classShape:__metaclass__=ABCMetadrawing_api=Nonedef__init__(self,drawing_api):self.drawing_api=drawing_api@abstractmethoddefdraw(self):raiseNotImplementedError(NOT_IMPLEMENTED)@abstractmethoddefresize_by_percentage(self,percent):raiseNotImplementedError(NOT_IMPLEMENTED)classCircleShape(Shape):def__init__(self,x,y,radius,drawing_api):self.x=xself.y=yself.radius=radiussuper(CircleShape,self).__init__(drawing_api)defdraw(self):returnself.drawing_api.draw_circle(self.x,self.y,self.radius)defresize_by_percentage(self,percent):self.radius*=1+percent/100classBridgePattern:@staticmethoddeftest():shapes=[CircleShape(1.0,2.0,3.0,DrawingAPI1()),CircleShape(5.0,7.0,11.0,DrawingAPI2()),CircleShape(5.0,4.0,12.0,DrawingAPI3()),]forshapeinshapes:shape.resize_by_percentage(2.5)print(shape.draw())BridgePattern.test()

See also

• Adapter pattern
• Strategy pattern
• Template method pattern

References

1. Gamma, Erich; Helm, Richard; Johnson, Ralph; Vlissides, John (1994). Design Patterns: Elements of Reusable Object-Oriented Software . Addison-Wesley. p.  151. ISBN   0-201-63361-2.
2. "The Bridge design pattern - Problem, Solution, and Applicability". w3sDesign.com. Retrieved 2017-08-12.
3. "The Bridge design pattern - Structure and Collaboration". w3sDesign.com. Retrieved 2017-08-12.

External links

• Bridge in UML and in LePUS3 (a formal modelling language)
• C# Design Patterns: The Bridge Pattern. 2002-12-20.{{cite book}}: |work= ignored (help) From: James W. Cooper (2003). C# Design Patterns: A Tutorial. Addison-Wesley. ISBN   0-201-84453-2.