Why Command pattern in LLD? - Purpose & Use Cases

The Big Idea

What if you could press a button and instantly undo or schedule any action without rewriting your code?

The Scenario

Imagine you have a remote control with many buttons, and each button does a different task. Now, you want to add undo and redo features, or queue commands to run later. Doing all this by writing separate code for each button and feature quickly becomes messy and confusing.

The Problem

Manually handling each action means you mix the code for what to do with when and how to do it. This leads to tangled code that is hard to change or extend. Adding new commands or features like undo requires rewriting many parts, increasing bugs and slowing development.

The Solution

The Command pattern wraps each action into its own object. This separates the 'what to do' from 'when and how to do it'. It makes adding new commands, undo, redo, or queuing simple and clean without changing existing code.

Before vs After

✗ Before

if(button == 'play') { playSong(); } else if(button == 'stop') { stopSong(); } // no undo support

✓ After

command = new PlayCommand(song); remote.setCommand(command); remote.pressButton(); // supports undo, redo, queue

What It Enables

It enables flexible, reusable, and extendable command execution with features like undo, redo, and scheduling without messy code changes.

Real Life Example

In text editors, every user action like typing or deleting is a command object. This lets the editor easily undo or redo actions by replaying or reversing these commands.

Key Takeaways

Separates actions into command objects for clean code.

Makes adding undo, redo, and queuing easy.

Improves flexibility and maintainability of complex systems.

Practice

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

easy

A. To create multiple instances of a class efficiently

B. To ensure only one instance of a class exists

C. To define a family of algorithms and make them interchangeable

D. To encapsulate a request as an object, allowing parameterization and queuing of requests

Solution

1. Step 1: Understand the Command pattern role

   The Command pattern encapsulates a request as an object, which allows you to parameterize clients with queues, requests, and operations.

2. Step 2: Compare with other patterns

   Creating multiple instances relates to Prototype or Factory, a family of algorithms to Strategy, and a single instance to Singleton; these are not Command.

3. Final Answer:

   To encapsulate a request as an object, allowing parameterization and queuing of requests -> Option D

4. Quick Check:

   Command pattern = encapsulate request [OK]

Hint: Command pattern = wrap action as object for flexibility [OK]

Common Mistakes:

• Confusing Command with Singleton or Factory patterns
• Thinking Command creates instances instead of encapsulating actions
• Mixing Command with Strategy pattern

2. Which of the following is the correct method signature for the execute method in a Command interface?

easy

A. void execute(String[] args);

B. void execute();

C. boolean execute(String commandName);

D. int execute(int commandId);

Solution

1. Step 1: Recall Command interface basics

   The Command interface typically defines a simple execute() method without parameters to perform the action.

2. Step 2: Analyze options

   The options with parameters (String[], int commandId, String commandName) or return types are not standard in Command pattern interfaces; the command object itself holds necessary data.

3. Final Answer:

   void execute(); -> Option B

4. Quick Check:

   Command execute method = void execute() [OK]

Hint: Command execute usually has no parameters [OK]

Common Mistakes:

• Adding parameters to execute method unnecessarily
• Confusing Command with other patterns that require arguments
• Assuming execute returns a value

3. Given the following code snippet implementing the Command pattern, what will be the output?

class Light {
  turnOn() { console.log('Light is ON'); }
  turnOff() { console.log('Light is OFF'); }
}

class TurnOnCommand {
  constructor(light) { this.light = light; }
  execute() { this.light.turnOn(); }
}

class TurnOffCommand {
  constructor(light) { this.light = light; }
  execute() { this.light.turnOff(); }
}

class RemoteControl {
  setCommand(command) { this.command = command; }
  pressButton() { this.command.execute(); }
}

const light = new Light();
const remote = new RemoteControl();
remote.setCommand(new TurnOnCommand(light));
remote.pressButton();
remote.setCommand(new TurnOffCommand(light));
remote.pressButton();

medium

A. Light is ON\nLight is OFF

B. Light is OFF\nLight is ON

C. Light is ON\nLight is ON

D. Light is OFF\nLight is OFF

Solution

1. Step 1: Trace first command execution

   The remote sets the command to TurnOnCommand and calls execute, which calls light.turnOn(), printing 'Light is ON'.

2. Step 2: Trace second command execution

   The remote sets the command to TurnOffCommand and calls execute, which calls light.turnOff(), printing 'Light is OFF'.

3. Final Answer:

   Light is ON\nLight is OFF -> Option A

4. Quick Check:

   TurnOn then TurnOff commands print ON then OFF [OK]

Hint: Follow command set and execute calls step-by-step [OK]

Common Mistakes:

• Mixing order of commands
• Assuming commands execute immediately without setting
• Confusing method names turnOn and turnOff

4. In the following code, what is the main issue that prevents the Command pattern from working correctly?

class Light {
  turnOn() { console.log('Light is ON'); }
}

class TurnOnCommand {
  constructor() { }
  execute() { this.light.turnOn(); }
}

const light = new Light();
const command = new TurnOnCommand();
command.execute();

medium

A. The execute method should return a value

B. The Light class is missing the turnOff method

C. The TurnOnCommand constructor does not receive or store the Light object

D. The command object is not instantiated properly

Solution

1. Step 1: Check TurnOnCommand constructor

   The constructor does not accept or assign the Light object to this.light, so this.light is undefined.

2. Step 2: Analyze execute method call

   Calling this.light.turnOn() fails because this.light is undefined, causing an error.

3. Final Answer:

   The TurnOnCommand constructor does not receive or store the Light object -> Option C

4. Quick Check:

   Missing light reference in command = error [OK]

Hint: Ensure command stores receiver object before execute [OK]

Common Mistakes:

• Ignoring missing receiver object in command
• Thinking missing turnOff method causes error here
• Assuming execute must return a value

5. You are designing a text editor with undo functionality using the Command pattern. Which design choice best supports undo operations efficiently?

hard

A. Store a history stack of Command objects and call an undo() method on the last command

B. Keep a log of all text changes as strings and replay them to undo

C. Use a single Command object that modifies text directly without history

D. Implement undo by reloading the entire document from disk

Solution

1. Step 1: Understand undo with Command pattern

   Each Command object should implement both execute() and undo() methods to reverse its action.

2. Step 2: Evaluate design choices

   Storing a history stack of Command objects allows calling undo() on the last command efficiently. Other options either lack command encapsulation or are inefficient.

3. Final Answer:

   Store a history stack of Command objects and call an undo() method on the last command -> Option A

4. Quick Check:

   Undo = command history stack with undo() [OK]

Hint: Undo needs command history with undo method [OK]

Common Mistakes:

• Using string logs instead of command objects
• Not implementing undo in commands
• Reloading entire document is inefficient