Overview
How to use this roadmap
Who it is for: students, freshers, developers from non-CS backgrounds, low-code developers (Appian, Pega, OutSystems) moving into backend or architecture roles, and anyone preparing for their first system design interview.
What "system design" means: deciding which pieces (servers, databases, caches, queues) an application needs, how they talk to each other, and how the whole thing keeps working when 10 users become 10 million.
Study method that works:
- Read or watch one concept.
- Explain it out loud in plain words, as if to a friend. If you cannot, re-read.
- Draw it on paper: boxes and arrows.
- Do the small hands-on exercise listed in each phase.
- Every Sunday, revise the week's terms using the glossary at the end.
Each phase below has: concepts (with simple explanations), why it matters for apps, a hands-on exercise, and a checkpoint — questions you should be able to answer before moving on.
Your path
Tip: use ← → arrow keys to move between steps.