Structural patterns (Adapter, Decorator, Facade) in Software Engineering - Time & Space Complexity

Time Complexity: Structural patterns (Adapter, Decorator, Facade)

O(n)

Understanding Time Complexity

We want to understand how the time it takes to use structural patterns changes as the size of the input or system grows.

Specifically, how do Adapter, Decorator, and Facade patterns affect the speed of a program?

Scenario Under Consideration

Analyze the time complexity of the following example using the Decorator pattern.

class Component:
    def operation(self):
        return "Base"

class Decorator(Component):
    def __init__(self, component):
        self.component = component
    def operation(self):
        return f"Decorated({self.component.operation()})"

component = Component()
decorated = Decorator(component)
result = decorated.operation()

This code wraps a base component with a decorator that adds extra behavior when calling operation.

Identify Repeating Operations

Look for repeated calls or loops that affect performance.

• Primary operation: Calling operation() on the decorator which calls the wrapped component's operation().
• How many times: Once per call, but can be nested if multiple decorators wrap each other.

How Execution Grows With Input

As you add more decorators wrapping each other, each call to operation() triggers more calls inside.

Number of Decorators (n)	Approx. Calls to operation()
1	2
5	6
10	11

Pattern observation: The number of calls grows linearly with the number of decorators.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the operation grows directly in proportion to how many decorators are added.

Common Mistake

[X] Wrong: "Using these patterns does not affect performance at all."

[OK] Correct: Each added layer (like a decorator or adapter) adds extra method calls, which can increase execution time especially if many layers are stacked.

Interview Connect

Understanding how structural patterns impact time helps you explain design choices clearly and shows you think about both design and performance.

Self-Check

What if we replaced the Decorator pattern with a Facade that calls multiple components internally? How would the time complexity change?

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