The Bridge Design Pattern solves this by putting the Editor Window abstraction and the implementation in separate class hierarchies. Below is the code for the  Vehicle class: After defining the types of vehicles, we are not implementing specifications classes, like ProduceBike, AssembleBike, ProduceCar , or  AssembleCar. It increases the loose coupling between class abstraction and it’s implementation. Java Design Pattern: Bridge In brief, Bridge Design Pattern is a two layer abstraction. 4. This design pattern mainly decouples an … 2. To indicate this, I am creating a dedicated method minWorkTime() for each of the concrete vehicles. Also, sometimes we need to separate the code so that it is reusable and easy to maintain. Bridge Pattern in Java. Today we will look into Bridge Design Pattern in java. Liked the article? Prasad Kharkar is a java enthusiast and always keen to explore and learn java technologies. When you don't want a permanent binding between the functional abstraction and its implementation. Below is the code for the ProduceWorkShop class: Below is the code for the AssembleWorkShop  class: Below is the code for the PaintWorkShop class: Below is the code for the RepairWorkShop class: Below is the code for the TestWorkShop class: To make this example a little more interesting, I am putting a timed-sleep for a few milliseconds to indicate that the workshop takes different times in the manufacturing of different types of vehicles. The pattern can be explained with the help of below components – 1. behaviour part. To achieve this, we have created the interface WorkShop, which will act as a bridge between types of vehicles and concrete workshops (implementors) to perform manufacturing work with the work() method. We are going to see yet another design pattern in this article. Together, this is called the implementation. As a result, any change made to one aff… This pattern involves an interface which acts as a bridge which makes the functionality of concrete … Below is the code for the  WorkShop interface: This workshop interface will act as a bridge between various types of vehicles and its manufacturing work (implementors). Now, we need to create implementors of the Workshop to define various types of workshops required to perform the manufacturing work. Eg) A project developed with Angular for the front end and Java at the backend. The Bridge Pattern is also known as Handle or Body. 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 Pattern. Create a QuestionManager class that will use Question interface which will act as a bridge.. Bridge Pattern by Example. It also maintains the Implementer reference. Bridge Pattern là gì? One is the abstracted class that contains all of the complex codes. and the method will have different values based on the implementor concrete classes. All the vehicle has to do is use the WorkShop to produce, assemble, or quality check (test) its work using the  work() method for production. Create a JavaQuestions implementation class that will implement Question interface. Bridge in Java Bridge is a structural design pattern that divides business logic or huge class into separate class hierarchies that can be developed independently. Happy coding! The bridge pattern applies when there is a need to avoid permanent binding between an abstraction and an implementation and when the abstraction and implementation need to vary independently. Please don't forget to click that like button. Vehicles and workshops are connected via the WorkShop Bridge interface and are separate and independent of each other. Java applications can run on different platforms, so the client code should be able to create a Component without committing to a concrete implementation.