Bridge Pattern

Lastly - The Bridge Design Pattern! The Bridge pattern is a structural design pattern that decouples an abstraction from its implementation, allowing both to evolve independently. This pattern is particularly useful when you want to avoid a permanent binding between an abstraction and its concrete implementation.

In this lesson, you will:

• Understand the Bridge pattern and its purpose.
• Learn how to implement the Bridge pattern through a detailed example with multiple components.
• See how the Bridge pattern helps in creating flexible and scalable systems.

Let's dive into the Bridge pattern through a practical example.

The goal of the Bridge pattern is to decouple the abstraction from its implementation, allowing both to evolve independently and providing greater flexibility and scalability.

We will be implementing this pattern with devices like Printer and Scanner, which will run on different operating systems like Windows and MacOS.

First, let's define the OperatingSystem interface. This interface will declare the run method, which will be implemented by different operating systems.

OperatingSystem.java:

public interface OperatingSystem {
    void run(String device);
}

In this interface, the run method takes a device name and performs an operation on it.

Next, we need concrete classes that implement the OperatingSystem interface. These classes will perform specific operations based on the operating system.

WindowsOS.java:

public class WindowsOS implements OperatingSystem {
    @Override
    public void run(String device) {
        System.out.println("Running " + device + " on Windows OS.");
    }
}

MacOS.java:

public class MacOS implements OperatingSystem {
    @Override
    public void run(String device) {
        System.out.println("Running " + device + " on MacOS.");
    }
}

These classes implement the run method for Windows and MacOS, respectively.