Why Structural patterns (Adapter, Decorator, Facade) in Software Engineering? - Purpose & Use Cases

The Big Idea

What if you could connect any device or feature without rewriting everything from scratch?

The Scenario

Imagine you have several different devices and software components that need to work together, but each speaks a different language or expects different inputs. You try to connect them manually by writing lots of custom code for each pair, like building a new bridge every time two parts need to communicate.

The Problem

This manual approach is slow and confusing. Every time you add a new device or feature, you must rewrite or duplicate code. It's easy to make mistakes, and the system becomes hard to maintain or expand. You spend more time fixing connections than building new features.

The Solution

Structural patterns like Adapter, Decorator, and Facade provide smart, reusable ways to connect, enhance, or simplify parts of a system. They act like translators, enhancers, or simple front doors, so components can work together smoothly without changing their core code.

Before vs After

✗ Before

if device == 'A': connectA()
if device == 'B': connectB()
# lots of repeated connection code

✓ After

adapter = DeviceAdapter(device)
adapter.connect()
# one interface for all devices

What It Enables

These patterns enable building flexible, maintainable systems where components fit together easily and can grow without chaos.

Real Life Example

Think of a universal remote control (Facade) that lets you operate many devices with one simple interface, or a phone charger adapter that lets your charger fit different sockets (Adapter), or adding a protective case to your phone without changing the phone itself (Decorator).

Key Takeaways

Manual connections between parts are slow and error-prone.

Structural patterns provide clean, reusable ways to connect and enhance components.

They make systems easier to build, maintain, and expand.

Practice

1. Which structural pattern allows incompatible interfaces to work together by converting one interface into another?

easy

A. Decorator

B. Adapter

C. Facade

D. Singleton

Solution

1. Step 1: Understand the role of Adapter pattern

   The Adapter pattern converts the interface of one class into another interface clients expect, enabling incompatible interfaces to work together.

2. Step 2: Compare with other patterns

   Decorator adds features, Facade simplifies interfaces, Singleton controls instance creation. Only Adapter changes interfaces for compatibility.

3. Final Answer:

   Adapter -> Option B

4. Quick Check:

   Interface conversion = Adapter [OK]

Hint: Adapter = interface converter between incompatible parts [OK]

Common Mistakes:

• Confusing Decorator with Adapter
• Thinking Facade changes interfaces
• Mixing Singleton with structural patterns

2. Which of the following is the correct way to describe the Decorator pattern?

easy

A. It converts one interface to another.

B. It provides a simple interface to a complex system.

C. It adds new responsibilities to objects dynamically.

D. It ensures a class has only one instance.

Solution

1. Step 1: Identify the purpose of Decorator pattern

   Decorator adds new features or responsibilities to objects dynamically without changing their structure.

2. Step 2: Eliminate other options

   It provides a simple interface to a complex system. describes Facade, It converts one interface to another. describes Adapter, It ensures a class has only one instance. describes Singleton pattern.

3. Final Answer:

   It adds new responsibilities to objects dynamically. -> Option C

4. Quick Check:

   Decorator = add features dynamically [OK]

Hint: Decorator = add features without changing original object [OK]

Common Mistakes:

• Mixing Decorator with Facade
• Confusing Adapter with Decorator
• Thinking Singleton is a structural pattern

3. Consider a system where a Facade pattern is used to simplify multiple complex subsystems. What is the main benefit when a client uses the Facade?

medium

A. The client interacts with a simple interface hiding complexity.

B. The client must adapt its interface to each subsystem.

C. The client can access all subsystem details directly.

D. The client can add new features to subsystems dynamically.

Solution

1. Step 1: Understand Facade pattern role

   Facade provides a simple unified interface to a set of interfaces in a subsystem, hiding complexity from the client.

2. Step 2: Analyze options

   The client can access all subsystem details directly. is wrong because Facade hides details. The client must adapt its interface to each subsystem. describes Adapter. The client can add new features to subsystems dynamically. describes Decorator.

3. Final Answer:

   The client interacts with a simple interface hiding complexity. -> Option A

4. Quick Check:

   Facade = simple interface to complex system [OK]

Hint: Facade hides complexity behind a simple interface [OK]

Common Mistakes:

• Thinking Facade exposes all subsystem details
• Confusing Facade with Adapter or Decorator
• Assuming Facade adds features dynamically

4. A developer tries to use an Adapter pattern but the client code still fails due to interface mismatch. What is the most likely error?

medium

A. The client code is using the correct interface.

B. The Decorator pattern was used instead of Adapter.

C. The Facade pattern was applied to simplify the interface.

D. The Adapter does not implement the target interface correctly.

Solution

1. Step 1: Identify Adapter pattern requirement

   Adapter must implement the target interface expected by the client to convert calls properly.

2. Step 2: Analyze failure cause

   If the client still fails, likely the Adapter does not correctly implement or map the target interface methods.

3. Final Answer:

   The Adapter does not implement the target interface correctly. -> Option D

4. Quick Check:

   Adapter interface mismatch = implementation error [OK]

Hint: Adapter must match target interface exactly [OK]

Common Mistakes:

• Confusing Decorator or Facade with Adapter errors
• Assuming client code is always correct
• Ignoring interface method signatures

5. You have a legacy payment system with a complex API. You want to provide a simple interface for new clients and also add logging features without changing the legacy code. Which combination of structural patterns should you use?

hard

A. Facade to simplify interface and Decorator to add logging

B. Decorator to simplify interface and Adapter to add logging

C. Adapter to add logging and Facade to simplify interface

D. Adapter to simplify interface and Decorator to add logging

Solution

1. Step 1: Identify pattern for simplifying complex API

   Facade provides a simple interface to a complex system, ideal for the legacy payment system.

2. Step 2: Identify pattern for adding features without changing code

   Decorator adds new responsibilities like logging dynamically without modifying original code.

3. Step 3: Combine patterns logically

   Use Facade to simplify the interface for clients, then wrap with Decorator to add logging features.

4. Final Answer:

   Facade to simplify interface and Decorator to add logging -> Option A

5. Quick Check:

   Simplify = Facade, Add features = Decorator [OK]

Hint: Facade simplifies, Decorator adds features without code change [OK]

Common Mistakes:

• Using Adapter to simplify interface instead of Facade
• Confusing roles of Adapter and Decorator
• Trying to add logging via Adapter