Why State pattern in LLD? - Purpose & Use Cases

The Big Idea

Discover how a simple design trick can turn your tangled state logic into clean, manageable code!

The Scenario

Imagine you are building a vending machine that can be in different states like 'Idle', 'HasMoney', 'Dispensing', or 'OutOfStock'. You try to handle all these states using many if-else or switch-case statements scattered everywhere in your code.

The Problem

This manual approach quickly becomes messy and hard to maintain. Adding a new state means changing many places, increasing bugs and confusion. It's like juggling too many balls at once and dropping them often.

The Solution

The State pattern organizes each state into its own class with clear behavior. The vending machine just delegates actions to the current state object. This keeps code clean, easy to extend, and reduces errors.

Before vs After

✗ Before

if(state == 'Idle') { if(moneyInserted) state = 'HasMoney'; } else if(state == 'HasMoney') { if(selectItem) state = 'Dispensing'; }

✓ After

state.handleMoneyInserted(); // state object changes itself internally

What It Enables

It enables building flexible systems where adding or changing states is simple and safe without breaking existing code.

Real Life Example

Think of a music player app that changes behavior when playing, paused, or stopped. Using the State pattern, each mode handles play, pause, or stop commands differently without complex condition checks.

Key Takeaways

Manual state handling leads to complex, error-prone code.

State pattern encapsulates state-specific behavior in separate classes.

It makes systems easier to extend and maintain.

Practice

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

easy

A. To provide a global point of access to a resource

B. To create multiple instances of a class efficiently

C. To allow an object to change its behavior when its internal state changes

D. To separate the construction of a complex object from its representation

Solution

1. Step 1: Understand the role of the State pattern

   The State pattern helps an object change its behavior based on its internal state without changing its class.

2. Step 2: Compare with other design patterns

   Other options describe Singleton (A), Prototype (B), and Builder (C) patterns, which are unrelated to state behavior changes.

3. Final Answer:

   To allow an object to change its behavior when its internal state changes -> Option C

4. Quick Check:

   State pattern = behavior change by internal state [OK]

Hint: State pattern changes behavior with state, not object creation [OK]

Common Mistakes:

• Confusing State pattern with Singleton or Builder patterns
• Thinking it manages object creation instead of behavior
• Assuming it provides global access to resources

2. Which of the following is the correct way to define a state interface in a typical State pattern implementation?

easy

A. interface State { void handle(); }

B. class State { void handle() {} }

C. enum State { START, STOP }

D. struct State { int status; }

Solution

1. Step 1: Identify the correct interface syntax

   The State pattern requires a State interface with a method like handle() to define behavior.

2. Step 2: Eliminate incorrect options

   class State { void handle() {} } is a class, not an interface; C is an enum, not behavior; D is a struct without behavior.

3. Final Answer:

   interface State { void handle(); } -> Option A

4. Quick Check:

   State interface defines behavior method [OK]

Hint: State pattern needs interface with behavior method [OK]

Common Mistakes:

• Using enum or struct instead of interface/class for behavior
• Defining empty methods without interface
• Confusing class and interface roles

3. Consider this simplified code snippet using the State pattern:

class Context {
  State state;
  void request() { state.handle(this); }
  void setState(State s) { state = s; }
}

class State {
  void handle(Context c) { c.setState(new StateB()); }
}

class StateB extends State {
  void handle(Context c) { c.setState(new State()); }
}

Context ctx = new Context();
ctx.setState(new State());
ctx.request();
ctx.request();

What is the final state of ctx after these two requests?

medium

A. An instance of State

B. An instance of StateB

C. Null (no state)

D. An error occurs

Solution

1. Step 1: Trace first request()

   Initially, ctx.state = State instance. Calling request() calls State.handle(ctx), which sets state to new StateB.

2. Step 2: Trace second request()

   Now ctx.state = StateB instance. Calling request() calls StateB.handle(ctx), which sets state back to new State.

3. Final Answer:

   An instance of State -> Option A

4. Quick Check:

   State and StateB toggle on requests [OK]

Hint: State and StateB toggle on each request call [OK]

Common Mistakes:

• Assuming state stays the same after first request
• Confusing which handle method is called
• Ignoring state changes inside handle methods

4. In the following State pattern code, what is the main issue causing incorrect behavior?

interface State {
  void handle(Context c);
}

class Context {
  State state;
  void request() {
    state.handle(this);
  }
}

class ConcreteStateA implements State {
  void handle(Context c) {
    // Missing state transition
    System.out.println("State A handling");
  }
}

Context ctx = new Context();
ctx.state = new ConcreteStateA();
ctx.request();
ctx.request();

medium

A. State interface method signature is incorrect

B. Context's state is never updated inside handle, so state never changes

C. Context does not initialize state before request

D. ConcreteStateA does not implement handle method

Solution

1. Step 1: Analyze state transitions in handle()

   ConcreteStateA.handle() prints a message but does not update Context's state, so no state change occurs.

2. Step 2: Check other options

   State interface method is correct; Context initializes state before request; ConcreteStateA implements handle properly.

3. Final Answer:

   Context's state is never updated inside handle, so state never changes -> Option B

4. Quick Check:

   State transition missing inside handle() [OK]

Hint: State must update Context's state inside handle() [OK]

Common Mistakes:

• Forgetting to update state inside handle method
• Assuming printing is enough for state change
• Ignoring initialization of state before request

5. You are designing a traffic light system using the State pattern. The traffic light cycles through Green, Yellow, and Red states. Which design choice best applies the State pattern to handle state transitions and behavior?

hard

A. Use a global variable to track color and update it externally without encapsulating behavior

B. Use a single class with a variable holding the current color and switch behavior using if-else statements

C. Implement the traffic light as a simple timer without state classes

D. Create separate state classes for Green, Yellow, and Red, each implementing a next() method to switch to the next state

Solution

1. Step 1: Understand State pattern application

   The pattern suggests encapsulating each state in its own class with behavior and transitions.

2. Step 2: Evaluate options for scalability and clarity

   Create separate state classes for Green, Yellow, and Red, each implementing a next() method to switch to the next state cleanly separates states and their transitions. Options B, C, and D mix logic or lack encapsulation, reducing maintainability.

3. Final Answer:

   Create separate state classes for Green, Yellow, and Red, each implementing a next() method to switch to the next state -> Option D

4. Quick Check:

   Separate classes with transitions = State pattern [OK]

Hint: Separate states as classes with next() method for transitions [OK]

Common Mistakes:

• Using if-else instead of separate state classes
• Not encapsulating state behavior inside classes
• Relying on external variables without behavior