Today we will look into Bridge Design Pattern in java. When we have interface hierarchies in both interfaces as well as implementations, then bridge design pattern is used to decouple the interfaces from implementation and hiding the implementation details from the client programs.
Just like Adapter pattern, bridge design pattern is one of the Structural design pattern. According to GoF bridge design pattern is:
Decouple an abstraction from its implementation so that the two can vary independently
The implementation of bridge design pattern follows the notion to prefer Composition over inheritance.
If we look into bridge design pattern with example, it will be easy to understand. Lets say we have an interface hierarchy in both interfaces and implementations like below image. Now we will use bridge design pattern to decouple the interfaces from implementation. UML diagram for the classes and interfaces after applying bridge pattern will look like below image. Notice the bridge between Shape
and Color
interfaces and use of composition in implementing the bridge pattern. Here is the java code for Shape and Color interfaces. Color.java
package com.journaldev.design.bridge;
public interface Color {
public void applyColor();
}
Shape.java
package com.journaldev.design.bridge;
public abstract class Shape {
//Composition - implementor
protected Color color;
//constructor with implementor as input argument
public Shape(Color c){
this.color=c;
}
abstract public void applyColor();
}
We have Triangle and Pentagon implementation classes as below. Triangle.java
package com.journaldev.design.bridge;
public class Triangle extends Shape{
public Triangle(Color c) {
super(c);
}
@Override
public void applyColor() {
System.out.print("Triangle filled with color ");
color.applyColor();
}
}
Pentagon.java
package com.journaldev.design.bridge;
public class Pentagon extends Shape{
public Pentagon(Color c) {
super(c);
}
@Override
public void applyColor() {
System.out.print("Pentagon filled with color ");
color.applyColor();
}
}
Here are the implementation classes for RedColor and GreenColor. RedColor.java
package com.journaldev.design.bridge;
public class RedColor implements Color{
public void applyColor(){
System.out.println("red.");
}
}
GreenColor.java
package com.journaldev.design.bridge;
public class GreenColor implements Color{
public void applyColor(){
System.out.println("green.");
}
}
Lets test our bridge pattern implementation with a test program. BridgePatternTest.java
package com.journaldev.design.test;
import com.journaldev.design.bridge.GreenColor;
import com.journaldev.design.bridge.Pentagon;
import com.journaldev.design.bridge.RedColor;
import com.journaldev.design.bridge.Shape;
import com.journaldev.design.bridge.Triangle;
public class BridgePatternTest {
public static void main(String[] args) {
Shape tri = new Triangle(new RedColor());
tri.applyColor();
Shape pent = new Pentagon(new GreenColor());
pent.applyColor();
}
}
Output of above bridge pattern example program is:
Triangle filled with color red.
Pentagon filled with color green.
Bridge design pattern can be used when both abstraction and implementation can have different hierarchies independently and we want to hide the implementation from the client application.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
While we believe that this content benefits our community, we have not yet thoroughly reviewed it. If you have any suggestions for improvements, please let us know by clicking the “report an issue“ button at the bottom of the tutorial.
Hi Pankaj, Nice explanation. Can you please clarify below. If implementation of applyColor() method is different for both Triangle and Pentagon classes, then this design patterns is not suitable right?
- Prasad
Thanks Pankaj Very self explanatory tutorials. Any chance of that you will upload design-pattern vedioes?
- Dilip Kumar Pandey
Please elaborate on how the decoupling has happened between abstraction and implementation here. Still if we add any abstract method in Shape abstract class, implementation for it is to be provided in Triangle and Pentagon classes. Similarly if any method is declared in interface Color, its implementation needs to be provided in RedColor and GreenColor classes, so how is the decoupling achieved here…
- KranthiC
Hi Pankaj , Nice , simple explanation , after googling so many Design Pattern , its is one of most simple , that why i have saved as screen shoot . It would be favor for all , if u just shared the code as downloadable .
- Ashakant
The opening sentence, “When we have interface hierarchies in both interfaces as well as implementations”… Did you mean ‘inheritance hierarchies’, when you say ‘interface hierarchies’…?
- yousuf
Cool explanation as always. Which tool are you using for UML diagram.?
- Anil
Thanks Pankaj for the wonderful article on Design patterns, but you may want to correct the first line on this “Bridge pattern” page: "When we have interface hierarchies in both interfaces as well as implementations, then builder design " It is supposed to be bridge pattern and not builder.
- Jay
Please, change builder to bridge in the first line of the article
- 12
Please modify UML diagram, you draw association and describing it as composition.
- Anurag
Great article, I read 2 prior articles which described this pattern, but in no way demonstrated why you would ever have a need to use it. This article does both, and very simply.
- Paul