Why structural patterns organize class relationships in LLD - Architecture Impact

System Overview - Why structural patterns organize class relationships

Structural patterns help organize how classes and objects relate to each other. They make it easier to build flexible and reusable software by defining clear ways classes connect and work together.

Architecture Diagram

User
  |
  v
Client Class
  |
  v
Adapter Pattern
  |
  v
Adaptee Class

Decorator Pattern
  |
  v
Component Interface <-> Concrete Component
  |
  v
Decorator Class

Facade Pattern
  |
  v
Facade Class
  |
  v
Subsystem Classes

Components

Client Class

class

Uses interfaces to interact with other classes

Adapter Pattern

structural_pattern

Allows incompatible interfaces to work together by wrapping one class

Adaptee Class

class

Existing class with incompatible interface

Decorator Pattern

structural_pattern

Adds behavior to objects dynamically without changing their class

Component Interface

interface

Defines common methods for components and decorators

Concrete Component

class

Original object to be decorated

Decorator Class

class

Wraps component to add new behavior

Facade Pattern

structural_pattern

Provides a simple interface to a complex subsystem

Facade Class

class

Simplifies interactions with multiple subsystem classes

Subsystem Classes

class

Complex classes that perform detailed work

Request Flow - 6 Hops

Client Class → Adapter Pattern

Adapter Pattern → Adaptee Class

Client Class → Decorator Pattern

Decorator Pattern → Concrete Component

Client Class → Facade Class

Facade Class → Subsystem Classes

Failure Scenario

Component Fails:Adapter Pattern

Impact:Client cannot use adaptee due to incompatible interface

Mitigation:Use alternative adapter or refactor adaptee interface

Architecture Quiz - 3 Questions

Which structural pattern helps make incompatible interfaces work together?

A Decorator Pattern

B Adapter Pattern

C Facade Pattern

D Singleton Pattern

Design Principle

Structural patterns organize class relationships to improve flexibility and reuse. They define clear ways classes connect, making complex systems easier to understand and extend without changing existing code.

Practice

1. What is the main purpose of structural design patterns in organizing class relationships?

easy

A. To simplify system design by organizing how classes relate

B. To improve the speed of the program execution

C. To handle user input and output operations

D. To store data persistently in databases

Solution

1. Step 1: Understand the role of structural patterns

   Structural patterns focus on how classes and objects are composed to form larger structures.

2. Step 2: Identify the main goal

   The main goal is to simplify the design by making relationships flexible and clear.

3. Final Answer:

   To simplify system design by organizing how classes relate -> Option A

4. Quick Check:

   Structural patterns simplify class relationships [OK]

Hint: Structural patterns simplify class connections [OK]

Common Mistakes:

• Confusing structural patterns with performance optimization
• Thinking structural patterns manage data storage
• Mixing structural patterns with user interface handling

2. Which of the following is a correct example of a structural pattern that organizes class relationships?

easy

A. Factory pattern

B. Singleton pattern

C. Adapter pattern

D. Observer pattern

Solution

1. Step 1: Recall common structural patterns

   Adapter, Decorator, and Composite are examples of structural patterns.

2. Step 2: Match options to pattern types

   Adapter is a structural pattern; Singleton is creational; Observer is behavioral; Factory is creational.

3. Final Answer:

   Adapter pattern -> Option C

4. Quick Check:

   Adapter = Structural pattern [OK]

Hint: Adapter is a classic structural pattern [OK]

Common Mistakes:

• Confusing creational patterns with structural ones
• Selecting Observer which is behavioral
• Choosing Factory which is creational

3. Given the following class structure using the Decorator pattern, what is the main benefit of this design?

class Coffee {
  cost() { return 5; }
}
class MilkDecorator {
  constructor(coffee) { this.coffee = coffee; }
  cost() { return this.coffee.cost() + 2; }
}

medium

A. It speeds up the cost calculation by caching results

B. It allows adding features dynamically without changing original classes

C. It restricts the coffee class from being extended

D. It stores coffee objects in a database

Solution

1. Step 1: Analyze the Decorator pattern usage

   The MilkDecorator wraps a Coffee object and adds extra cost dynamically.

2. Step 2: Understand the benefit

   This design allows adding new features (like milk) without modifying the original Coffee class.

3. Final Answer:

   It allows adding features dynamically without changing original classes -> Option B

4. Quick Check:

   Decorator adds features dynamically [OK]

Hint: Decorator adds features without changing original class [OK]

Common Mistakes:

• Thinking it caches results for speed
• Believing it restricts class extension
• Assuming it handles data storage

4. Identify the error in this Adapter pattern implementation:

class OldSystem {
  oldRequest() { return 'Old response'; }
}
class Adapter {
  constructor(oldSystem) { this.oldSystem = oldSystem; }
  request() { return this.oldSystem.request(); }
}

medium

A. Adapter should inherit from OldSystem

B. OldSystem class should not have any methods

C. Constructor is missing in OldSystem

D. Adapter calls a non-existent method 'request' instead of 'oldRequest'

Solution

1. Step 1: Check method calls in Adapter

   Adapter calls this.oldSystem.request(), but OldSystem has only oldRequest() method.

2. Step 2: Identify the mismatch

   The Adapter should call oldRequest() to adapt it to request().

3. Final Answer:

   Adapter calls a non-existent method 'request' instead of 'oldRequest' -> Option D

4. Quick Check:

   Method name mismatch in Adapter [OK]

Hint: Check method names carefully in Adapter calls [OK]

Common Mistakes:

• Assuming inheritance is required in Adapter
• Thinking OldSystem should be empty
• Ignoring method name differences

5. You need to design a system where multiple objects form a tree structure and clients treat individual objects and compositions uniformly. Which structural pattern best organizes this relationship?

hard

A. Composite pattern

B. Facade pattern

C. Proxy pattern

D. Bridge pattern

Solution

1. Step 1: Understand the problem requirements

   The system needs to treat individual objects and groups (tree structure) uniformly.

2. Step 2: Match with structural patterns

   The Composite pattern allows composing objects into tree structures and clients treat them the same.

3. Step 3: Eliminate other options

   Facade simplifies interfaces, Proxy controls access, Bridge separates abstraction from implementation; none fit the tree structure need.

4. Final Answer:

   Composite pattern -> Option A

5. Quick Check:

   Tree structure uniform treatment = Composite [OK]

Hint: Composite handles tree structures uniformly [OK]

Common Mistakes:

• Confusing Facade with Composite
• Choosing Proxy for access control only
• Mixing Bridge with structural composition