Fundamentals
What system design is, the design process, requirements and HLD vs LLD.
Learn how to design scalable, reliable and fast software systems, step by step. Clear explanations, diagrams and real-world examples, from the basics to the questions asked in senior engineering interviews.
System design is the process of deciding the architecture, components, data and communication of a software system so that it does what users need (functional requirements) and does it well: fast, reliable, secure and able to grow (non-functional requirements). It is the blueprint you create before and while building an application, from a small startup product to a platform serving millions of users.
Every good design balances a few core qualities. Each one has its own tutorial:
Software developers moving towards senior or architect roles, backend engineers building distributed systems, and anyone preparing for system design interviews.
Basic programming in any language, simple SQL or NoSQL database use, and a general idea of HTTP, APIs and the client-server model.
Most large applications are built from the same building blocks. Requests from users pass through a CDN and a load balancer to a group of stateless application servers, which use a cache for speed, a replicated database for safe storage and a message queue for slow background work.
Follow the tracks in order, or jump to the topic you need. Topics marked "coming soon" are being written and will be linked here as they are published.
What system design is, the design process, requirements and HLD vs LLD.
Monolithic, microservices, serverless, event-driven and more.
Availability, consistency, reliability, latency, throughput, scaling and load balancing.
How clients and services talk: DNS, HTTP, APIs, WebSockets and gateways.
Choosing and scaling databases: SQL vs NoSQL, indexing, replication and sharding.
CDNs, caching, cache eviction, connection pooling and rate limiting to keep systems fast.
Queues, publish-subscribe and asynchronous processing.
3 more tutorials coming soon
Coordination across many machines: sagas, leader election and consensus.
6 more tutorials coming soon
Circuit breakers, retries, bulkheads and observability.
Authentication, authorization, JWT, OAuth2 and RBAC.
1 more tutorial coming soon
Step-by-step designs of popular real-world systems.
10 tutorials coming soon
How to approach and answer system design interview questions.
1 more tutorial coming soon
Whether you are designing a real product or answering an interview question, this six-step process keeps you organised:
Design applications that keep working smoothly as users, data and traffic grow.
Senior engineers and architects are expected to make and explain design decisions.
System design rounds are a standard part of interviews for mid-level and senior positions.
Understand the cost, speed and complexity behind every architecture choice.
Plan for failures early with redundancy, monitoring and resilience patterns.
Use the right amount of infrastructure, neither too little nor too much.