System Design Roadmap 2026
Design scalable systems: requirements, data, caching, queues, consistency, reliability and classic interview problems.
4 stages · 8 units · Advanced · about 120 hours · Last reviewed 19 November 2026
What is a system design?
System design is the practice of planning how the parts of a large software system fit together: clients, APIs, databases, caches, queues and services. It balances requirements such as scale, latency, consistency and cost, and it is the skill tested in senior engineering interviews and used when real products must handle growth and failure.
Step-by-step system design roadmap
- 1
Fundamentals
Intermediate · about 32 hours
Think in systems.
- Approach
The approach to system design starts before any boxes are drawn. It means clarifying functional and non-functional requirements, estimating traffic and storage with back-of-envelope arithmetic, defining the APIs clients will call, and sketching the core data model. These steps decide which architecture is reasonable.
- Building Blocks
Building blocks are the standard components that most architectures reuse. On the network side they include DNS, load balancers, reverse proxies and CDNs. On the storage side they include the engines under databases, such as B-trees and log-structured merge trees, which shape read and write performance.
- Approach
- 2
Data at Scale
Advanced · about 32 hours
Store and move data.
- Databases
Database scaling in system design is about growing storage and throughput beyond a single server. Common techniques are replication for read capacity and availability, partitioning or sharding to spread data, and indexing. Choosing a store means matching access patterns to relational, key-value, document, wide-column or graph databases.
- Caching and Messaging
Caching and messaging are two tools for speed and decoupling. A cache such as Redis keeps hot data in memory with strategies like cache-aside and write-through, and eviction policies like LRU. Queues and streams, such as Kafka or RabbitMQ, move work asynchronously between services and absorb traffic spikes.
- Databases
- 3
Reliability
Advanced · about 32 hours
Design for failure.
- Distributed Systems
Distributed systems theory explains what goes wrong when data lives on many machines. Topics include the CAP theorem, consistency models from eventual to strong, consensus algorithms such as Raft and Paxos for agreeing on a leader or value, and ways to handle transactions across services, such as two-phase commit and sagas.
- Resilience
Resilience is the ability of a system to keep working when parts fail. It is built with redundancy, health checks, timeouts, retries with backoff, circuit breakers and graceful degradation. Observability, meaning logs, metrics and traces, lets engineers see failures early and find their cause in production.
- Distributed Systems
- 4
Case Studies
Advanced · about 24 hours
Practise the interview.
- Classic Designs
Classic designs are the recurring case studies used to practise system design. Social and content examples include a news feed, chat application and video platform, while infrastructure examples include a URL shortener, rate limiter and distributed cache. Each reveals trade-offs between fan-out, storage, ordering and latency.
- Method
The system design interview method is a repeatable framework for answering open-ended design questions in limited time. It moves from clarifying requirements and estimating scale to a high-level diagram, deeper dives on key components, and a discussion of bottlenecks and trade-offs, with the candidate driving the conversation.
- Classic Designs
Frequently asked questions
Ready to practise for interviews?
Practise system design questions with an AI mock interviewer and get feedback on your answers.