Browse through all our published articles and discover knowledge across various topics
504 Articles
System Design › Low-Level Design
Low-level design of Chess: an 8x8 Board of Cells holding an abstract Piece subclassed per type, each with polymorphic canMove; a Game controller for turns, check/checkmate/stalemate, and special moves.
System Design › Low-Level Design
Low-level design of a multi-channel notification service: Channels as Strategy built by a Factory, reusable Templates, per-user Preferences, plus Decorator retries and Observer delivery tracking.
System Design › Low-Level Design
Design a logging framework (Log4j-style) as a showcase of patterns: level filtering via Chain of Responsibility, pluggable Appenders for destinations, Strategy formatters, a Singleton logger, plus thread-safety and async logging.
System Design › Low-Level Design
Design an ATM as a State machine (Idle → HasCard → Authenticated → Dispensing), model transactions as polymorphic Command classes, and dispense cash with a Chain of Responsibility over denominations — with the correctness details interviewers probe.
System Design › Low-Level Design
Design Tic-Tac-Toe in an LLD interview with extensibility in mind: Game/Board/Player/Piece classes, O(N) win-checking with running row/column/diagonal counts, and designing for N×N and other grid games.
System Design › Low-Level Design
Design an LRU cache with O(1) get and put — the classic data-structure question. Combining a HashMap with a doubly-linked list, sentinel nodes, Java code, and the thread-safety / LinkedHashMap notes.
System Design › Low-Level Design
Design an expense-sharing app like Splitwise in an LLD interview: split strategies (equal/exact/percentage), the who-owes-whom balance model, and the debt-simplification bonus. Classes, UML, and design decisions.
System Design › Low-Level Design
Design a movie ticket booking system in an LLD interview — the concurrency-focused version. Modelling Movie/Show/ShowSeat, and the reserve-then-confirm seat locking that prevents double-booking. Classes, UML, decisions.
System Design › Low-Level Design
Design a vending machine in an LLD interview — the textbook State pattern problem. States (Idle, HasMoney, Dispensing, OutOfStock), inventory, the change algorithm, classes, UML, and key decisions.
System Design › Low-Level Design
Design an elevator system in an LLD interview: modelling each elevator as a state machine with the SCAN movement algorithm, a controller that dispatches requests via a pluggable scheduling strategy, classes, and UML.
System Design › Low-Level Design
The classic machine-coding LLD question solved end to end: requirements, the class design (ParkingLot, Level, Spot, Vehicle, Ticket), UML relationships, and the patterns that impress — Strategy, Factory, Singleton.
System Design › Low-Level Design
The Chain of Responsibility pattern explained: pass a request along a chain of handlers until one handles it, decoupling sender from receiver. Servlet filters, approval workflows, Java code, UML, when to use.