State diagrams in LLD - System Design Guide

Problem Statement

When software components have complex behaviors that depend on many conditions, it becomes hard to track all possible states and transitions. This confusion leads to bugs, unexpected behavior, and difficulty in maintenance.

Solution

State diagrams visually map out all possible states of a component and the transitions triggered by events. This clear visualization helps developers understand, design, and implement behavior systematically, reducing errors and improving communication.

Architecture

┌───────────┐      event1      ┌───────────┐
│  State A  │ ───────────────▶ │  State B  │
└───────────┘                  └───────────┘
     ▲                              │
     │          event2              │ event3
     └──────────────────────────────┘
                 

This diagram shows two states, A and B, with arrows representing events that cause transitions between them.

Trade-offs

✓ Pros

→

Provides a clear, visual way to understand complex state-dependent behavior.

→

Helps identify all possible states and transitions, reducing missed edge cases.

→

Improves communication among developers and stakeholders by using a common visual language.

✗ Cons

→

Can become cluttered and hard to read if the system has too many states or transitions.

→

Requires upfront effort to create and maintain diagrams as the system evolves.

→

May oversimplify behavior if not detailed enough, leading to false confidence.

Use when a component or system has multiple states with complex transitions, especially when behavior depends on events or conditions. Ideal for UI workflows, protocol handling, or business logic with clear states.

Avoid for very simple components with linear or stateless behavior, or when the number of states is extremely large and better modeled with other techniques like state machines in code.

Real World Examples

Uber

Uses state diagrams to model ride lifecycle states such as requested, accepted, in-progress, and completed to manage driver and rider interactions.

Netflix

Models streaming session states like buffering, playing, paused, and stopped to handle user controls and network conditions.

Airbnb

Uses state diagrams to represent booking states such as requested, confirmed, canceled, and completed to coordinate host and guest actions.

Code Example

The before code uses a boolean flag without clear state management, which can become confusing as complexity grows. The after code uses an explicit state enum to represent door states, making transitions clear and easier to maintain.

LLD

### Before: No clear state management
class Door:
    def __init__(self):
        self.is_open = False

    def open(self):
        if not self.is_open:
            print("Door opened")
            self.is_open = True

    def close(self):
        if self.is_open:
            print("Door closed")
            self.is_open = False


### After: Using state pattern with explicit states
from enum import Enum

class DoorState(Enum):
    CLOSED = 1
    OPEN = 2

class Door:
    def __init__(self):
        self.state = DoorState.CLOSED

    def open(self):
        if self.state == DoorState.CLOSED:
            print("Door opened")
            self.state = DoorState.OPEN
        else:
            print("Door is already open")

    def close(self):
        if self.state == DoorState.OPEN:
            print("Door closed")
            self.state = DoorState.CLOSED
        else:
            print("Door is already closed")

Alternatives

Flowcharts

Flowcharts focus on process steps and decisions rather than explicit states and transitions.

Use when: Choose flowcharts when the focus is on procedural logic rather than stateful behavior.

Sequence diagrams

Sequence diagrams show interactions over time between components, not internal states.

Use when: Use sequence diagrams to model message exchanges rather than state changes.

Summary

State diagrams visually represent all states and transitions of a system component.

They help prevent bugs by clarifying complex state-dependent behavior.

Use them when your system has multiple states triggered by events or conditions.