Learning roadmap
Choose a goal, then follow each stage as an ordered, explained outline.
You have not recorded evidence yet. Start with the first recommended topic, then mark the evidence you can demonstrate.
Your progress is available for this visit only because browser storage is unavailable. Keep this page open or record your evidence elsewhere.
Build a durable mental model, then transfer it into a working application.
Stage purpose: Establish the vocabulary and first working mental model.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Explain the core idea and use it in a small example.
Estimated time: 105 minutes
Prerequisites: No prerequisite topics
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Handling Database Growth — Carry the Concurrency in Online Services model into the next design step and make the trade-off explicit.
Prerequisites: Concurrency in Online Services
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Distributed Transactions — Carry the Handling Database Growth model into the next design step and make the trade-off explicit.
Prerequisites: Handling Database Growth
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Live Sports Streaming at Scale — Carry the Distributed Transactions model into the next design step and make the trade-off explicit.
Stage purpose: Connect the concepts into a repeatable problem-solving model.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Apply the model to a representative exercise without copying a recipe.
Estimated time: 105 minutes
Prerequisites: Distributed Transactions
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Video-on-Demand Architecture — Carry the Live Sports Streaming at Scale model into the next design step and make the trade-off explicit.
Prerequisites: Live Sports Streaming at Scale
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Feeds, Notifications & CMS — Carry the Video-on-Demand Architecture model into the next design step and make the trade-off explicit.
Prerequisites: Video-on-Demand Architecture
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Distributed Content Search — Carry the Feeds, Notifications & CMS model into the next design step and make the trade-off explicit.
Stage purpose: Transfer the concepts into a realistic implementation task.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Produce a small artifact that proves the decision works.
Estimated time: 105 minutes
Prerequisites: Feeds, Notifications & CMS
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Distributed Payments — Carry the Distributed Content Search model into the next design step and make the trade-off explicit.
Prerequisites: Distributed Content Search
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Weaving Services Together & Interviews — Carry the Distributed Payments model into the next design step and make the trade-off explicit.
Prerequisites: Distributed Payments
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Complete this path by applying these outcomes in your own project.
Prioritise high-frequency material, retrieve it quickly, and practise explaining it clearly.
Stage purpose: Secure the concepts that recur in most interviews.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Give a concise, accurate explanation with one concrete example.
Estimated time: 45 minutes
Prerequisites: No prerequisite topics
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Handling Database Growth — Use Concurrency in Online Services as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Concurrency in Online Services
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Distributed Transactions — Use Handling Database Growth as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Handling Database Growth
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Live Sports Streaming at Scale — Use Distributed Transactions as the setup for the next system-design follow-up and defend the connection aloud.
Stage purpose: Rehearse implementation choices that invite common follow-up questions.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Walk through a realistic API decision and defend the trade-offs.
Estimated time: 45 minutes
Prerequisites: Distributed Transactions
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Video-on-Demand Architecture — Use Live Sports Streaming at Scale as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Live Sports Streaming at Scale
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Feeds, Notifications & CMS — Use Video-on-Demand Architecture as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Video-on-Demand Architecture
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Distributed Content Search — Use Feeds, Notifications & CMS as the setup for the next system-design follow-up and defend the connection aloud.
Stage purpose: Prepare the details that distinguish a deeper answer.
Required background: Complete the linked prerequisites below or bring equivalent experience.
Expected outcome: Connect the concept to reliability, complexity, or production behavior.
Estimated time: 45 minutes
Prerequisites: Feeds, Notifications & CMS
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Distributed Payments — Use Distributed Content Search as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Distributed Content Search
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Weaving Services Together & Interviews — Use Distributed Payments as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Distributed Payments
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Complete this path by applying these outcomes in your own project.