Facade and Adapter Design Patterns Explained

Welcome! In this lesson, we'll dissect two main software design patterns: the Facade and Adapter patterns. We aim to unravel how these patterns ensure backward compatibility while adding new features. Backward compatibility means that new updates don't break existing systems, allowing for new functionalities without affecting the current code. Think of the Facade and Adapter patterns as cassette-shaped tape adapters for CD players, bridging the new and the old.

Design patterns are recognized solutions to frequent problems in software design and are time-tested methods resulting from the craftsmanship of seasoned developers. Among many design patterns, we're focusing on the Facade and Adapter patterns today. The Facade pattern provides a simplified interface to a complex subsystem, whereas the Adapter pattern enables classes with incompatible interfaces to work together. Let's delve deeper to unravel their use cases.

The Facade pattern simplifies complex processes by providing a higher-level interface. Consider an online shopping application. When a user places an order, it triggers many operations. By using the Facade pattern, we can create an OrderFacade class to simplify these operations:

// Without Facade
let order = new Order();
let product = new Product();
let payment = new Payment();
let delivery = new Delivery();

order.create();
product.check_availability();
payment.process_payment();
delivery.arrange_delivery();

// With Facade
class OrderFacade {
    constructor() {
        this.order = new Order();
        this.product = new Product();
        this.payment = new Payment();
        this.delivery = new Delivery();
    }

    placeOrder() {
        this.order.create();
        this.product.check_availability();
        this.payment.process_payment();
        this.delivery.arrange_delivery();
    }
}

let orderFacade = new OrderFacade();
orderFacade.placeOrder();

Here, assume the Order, Product, Payment, and Delivery are already correctly implemented in a different place, with all the necessary methods.

The Facade pattern, as demonstrated in the online shopping application example, ensures backward compatibility by consolidating complex subsystem interactions (ordering, payment, delivery) behind a simple OrderFacade interface. This allows the underlying subsystems to evolve independently (e.g., changing the payment process or delivery options) without necessitating changes to the client code, thereby preserving the interface's constancy over time. In addition, it makes the code more decoupled, allowing all order steps to be updated independently.