Why Composite pattern in LLD? - Purpose & Use Cases

The Big Idea

What if you could treat a single file and a whole folder the exact same way in your code?

The Scenario

Imagine you have a folder with files and subfolders, and you want to perform actions like opening or deleting on them. Doing this manually means writing separate code for files and folders, and then more code to handle folders inside folders, which quickly becomes messy.

The Problem

Manually handling each file and folder type separately leads to repetitive code and lots of special cases. It's easy to forget to handle a new folder inside a folder, causing bugs. The code becomes hard to read and maintain as the structure grows.

The Solution

The Composite pattern treats individual objects and groups of objects uniformly. It lets you write one interface for both files and folders, so you can perform actions on any item without worrying about its type. This simplifies code and scales naturally.

Before vs After

✗ Before

if item is file:
    open_file(item)
else if item is folder:
    for child in item.children:
        open(child)

✓ After

item.open()  # Works for both file and folder

What It Enables

It enables building flexible, tree-like structures where clients can treat individual and grouped objects the same way, making complex hierarchies easy to manage.

Real Life Example

File explorers use the Composite pattern to let users open, move, or delete files and folders seamlessly, no matter how deeply nested they are.

Key Takeaways

Composite pattern unifies handling of single and grouped objects.

Reduces code duplication and complexity in hierarchical structures.

Makes adding new components easier without changing client code.

Practice

1. What is the main purpose of the Composite pattern in system design?

easy

A. To create a single instance of a class

B. To separate interface from implementation

C. To provide a way to access elements of a collection sequentially

D. To treat individual objects and compositions of objects uniformly

Solution

1. Step 1: Understand the Composite pattern goal

   The Composite pattern allows treating individual objects and groups of objects the same way.

2. Step 2: Compare with other design patterns

   Other options describe different patterns: Singleton (A), Iterator (D), Bridge (B).

3. Final Answer:

   To treat individual objects and compositions of objects uniformly -> Option D

4. Quick Check:

   Composite pattern = treat objects uniformly [OK]

Hint: Composite = treat single and group objects the same [OK]

Common Mistakes:

• Confusing Composite with Singleton pattern
• Thinking Composite only manages single objects
• Mixing Composite with Iterator or Bridge patterns

2. Which of the following is the correct way to declare a composite interface method in a class diagram for the Composite pattern?

easy

A. int calculateSum(int a, int b);

B. void add(Component component);

C. String toString();

D. boolean equals(Object obj);

Solution

1. Step 1: Identify typical Composite interface methods

   Composite pattern usually includes methods like add(), remove(), and getChild() to manage children.

2. Step 2: Match method signature to Composite pattern

   Only void add(Component component); fits the pattern's purpose of managing child components.

3. Final Answer:

   void add(Component component); -> Option B

4. Quick Check:

   Composite interface method = add(Component) [OK]

Hint: Composite interface manages children with add/remove methods [OK]

Common Mistakes:

• Choosing unrelated method signatures
• Confusing standard Object methods with Composite methods
• Ignoring the need to manage child components

3. Given the following code snippet in a Composite pattern implementation, what will be the output?

class Component:
  def operation(self):
    pass

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

class Composite(Component):
  def __init__(self):
    self.children = []
  def add(self, component):
    self.children.append(component)
  def operation(self):
    results = []
    for child in self.children:
      results.append(child.operation())
    return "Composite(" + ", ".join(results) + ")"

leaf1 = Leaf()
leaf2 = Leaf()
composite = Composite()
composite.add(leaf1)
composite.add(leaf2)
print(composite.operation())

medium

A. Composite(Leaf, Leaf)

B. Leaf, Leaf

C. Composite()

D. Leaf

Solution

1. Step 1: Understand Leaf operation output

   Each Leaf's operation returns the string "Leaf".

2. Step 2: Understand Composite operation output

   Composite calls operation on each child and joins results with commas inside "Composite(...)".

3. Final Answer:

   Composite(Leaf, Leaf) -> Option A

4. Quick Check:

   Composite operation = Composite(Leaf, Leaf) [OK]

Hint: Composite operation joins child operations in parentheses [OK]

Common Mistakes:

• Expecting just 'Leaf' output
• Ignoring the Composite wrapper in output
• Confusing list join syntax

4. In the following Composite pattern code, what is the main error?

class Component:
  def operation(self):
    pass

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

class Composite(Component):
  def __init__(self):
    self.children = []
  def add(self, component):
    self.children.append(component)
  def operation(self):
    results = []
    for child in self.children:
      child.operation()
    return "Composite(" + ", ".join(results) + ")"

medium

A. The add method does not check component type

B. The Composite class does not initialize children list

C. The operation method does not collect child results

D. The Leaf class does not inherit from Component

Solution

1. Step 1: Analyze operation method in Composite

   The loop calls child.operation() but does not append results to the list.

2. Step 2: Identify missing result collection

   Without appending, results remains empty, causing incorrect output.

3. Final Answer:

   The operation method does not collect child results -> Option C

4. Quick Check:

   Missing append in loop = operation method error [OK]

Hint: Check if child results are collected in operation method [OK]

Common Mistakes:

• Ignoring missing append to results list
• Thinking add method type check is mandatory
• Assuming inheritance error without evidence

5. You are designing a UI framework using the Composite pattern. You want to add a feature to calculate the total number of visible elements in a nested component tree. Which approach best fits the Composite pattern principles?

hard

A. Add a countVisible() method to the Component interface, implemented by Leaf and Composite classes

B. Use a global counter variable updated externally during rendering

C. Only count visible elements in Leaf nodes, ignoring Composite nodes

D. Traverse the tree manually outside the classes to count visible elements

Solution

1. Step 1: Apply Composite pattern principle of uniformity

   Adding countVisible() to Component interface lets all nodes handle counting uniformly.

2. Step 2: Implement counting in Leaf and Composite

   Leaf returns 1 if visible, 0 otherwise; Composite sums counts from children.

3. Final Answer:

   Add a countVisible() method to the Component interface, implemented by Leaf and Composite classes -> Option A

4. Quick Check:

   Uniform method in Component = best Composite design [OK]

Hint: Add counting method to Component interface for uniformity [OK]

Common Mistakes:

• Using external counters breaking encapsulation
• Counting only leaves ignoring composites
• Manual traversal outside object methods