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: 140 minutes
Prerequisites: No prerequisite topics
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Web Architecture, From Client to Server and Back — Carry the Tiers of Software Architecture model into the next design step and make the trade-off explicit.
Prerequisites: Tiers of Software Architecture
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Scalability, from First Principles — Carry the Web Architecture, From Client to Server and Back model into the next design step and make the trade-off explicit.
Prerequisites: Web Architecture, From Client to Server and Back
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: High Availability — Carry the Scalability, from First Principles model into the next design step and make the trade-off explicit.
Prerequisites: Scalability, from First Principles
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Load Balancing — Carry the High Availability 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: 140 minutes
Prerequisites: High Availability
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Monoliths & Microservices — Carry the Load Balancing model into the next design step and make the trade-off explicit.
Prerequisites: Load Balancing
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Micro Frontends — Carry the Monoliths & Microservices model into the next design step and make the trade-off explicit.
Prerequisites: Monoliths & Microservices
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Databases — Carry the Micro Frontends model into the next design step and make the trade-off explicit.
Prerequisites: Micro Frontends
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Caching — Carry the Databases 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: 175 minutes
Prerequisites: Databases
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Message Queues — Carry the Caching model into the next design step and make the trade-off explicit.
Prerequisites: Caching
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Stream Processing — Carry the Message Queues model into the next design step and make the trade-off explicit.
Prerequisites: Message Queues
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Architecture Grab-Bag & Picking Tech — Carry the Stream Processing model into the next design step and make the trade-off explicit.
Prerequisites: Stream Processing
Evidence: Practise the outcome in code and record what you learned.
Current status: Not started
Recommended next: Case Studies & Mobile Apps — Carry the Architecture Grab-Bag & Picking Tech model into the next design step and make the trade-off explicit.
Prerequisites: Architecture Grab-Bag & Picking Tech
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: 60 minutes
Prerequisites: No prerequisite topics
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Web Architecture, From Client to Server and Back — Use Tiers of Software Architecture as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Tiers of Software Architecture
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Scalability, from First Principles — Use Web Architecture, From Client to Server and Back as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Web Architecture, From Client to Server and Back
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: High Availability — Use Scalability, from First Principles as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Scalability, from First Principles
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Load Balancing — Use High Availability 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: 60 minutes
Prerequisites: High Availability
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Monoliths & Microservices — Use Load Balancing as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Load Balancing
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Micro Frontends — Use Monoliths & Microservices as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Monoliths & Microservices
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Databases — Use Micro Frontends as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Micro Frontends
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Caching — Use Databases 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: 75 minutes
Prerequisites: Databases
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Message Queues — Use Caching as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Caching
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Stream Processing — Use Message Queues as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Message Queues
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Architecture Grab-Bag & Picking Tech — Use Stream Processing as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Stream Processing
Evidence: Answer aloud, give a concrete example, and identify the relevant trade-off.
Current status: Weak
Recommended next: Case Studies & Mobile Apps — Use Architecture Grab-Bag & Picking Tech as the setup for the next system-design follow-up and defend the connection aloud.
Prerequisites: Architecture Grab-Bag & Picking Tech
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.