State Design pattern - Real time example [Vending Machine]

Master Practical Java Architecture & Design Patterns!

Subscribe to Ram N Java for clean coding tutorials, GoF design patterns, and real-world system implementations!

🔔 Subscribe to Ram N Java

The Real-Time Vending Machine Problem

A classic, intuitive way to understand behavioral design patterns is by examining how everyday machines operate. Consider a Vending Machine: depending on what state the machine is currently in, pressing the exact same button produces completely different outcomes:

• No Coin State: Pressing an item button does nothing, alerting the user to insert money first.
• Has Coin State: The machine accepts item selections and prepares to dispense goods.
• Dispensing State: User inputs are temporarily locked while the mechanism delivers the item.
• Sold Out State: All purchase requests are rejected, preventing coin acceptance or prompting maintenance.

If you manage these conditions using procedural flags and nested if-else or switch blocks, adding a new action or state turns the code into an unmaintainable maze of conditional logic.

How the State Pattern Models the Machine

The State Design Pattern solves this complexity by turning every operational condition into an independent class:

• State Interface: Declares actions supported across various states—such as insertCoin(), ejectCoin(), selectItem(), and dispense().
• Concrete State Classes: Classes like NoCoinState, HasCoinState, and SoldOutState define what happens when each action is invoked, preventing invalid transitions and transitioning the context to the next valid state.
• Context (Vending Machine): Maintains the active state reference, delegating all incoming user actions directly to the current state object.

Key Architectural Benefits

Structuring state-driven systems with the State pattern delivers immediate engineering benefits:

• Eliminates Massive Conditionals: Replaces fragile if-else trees with clean polymorphic method calls.
• Single Responsibility Principle: Keeps state validation, transitions, and business rules cleanly isolated in their own classes.
• Open/Closed Principle: Adding new states (like CardPaymentState or MaintenanceState) requires no modifications to existing state classes.

Related Tutorials from Ram N Java

• 👉 State Design Pattern Applied: Vending Machine Implementation
• 👉 State Design Pattern Practical Example: LED TV Implementation
• 👉 State Design Pattern: Class Diagram Explained

---

Click here to watch in Youtube : https://www.youtube.com/watch?v=Ole4PaPb3uQ

Click the below Image to Enlarge

State Design pattern - Real time example [Vending Machine]