Learning path / Editorial roadmap
System design in practice
A proposed route from tracing one request to reasoning about boundaries, failures, and change. Start with a system you can explain.
2 articles available · 3 proposed modules
Read at your own pace. This is a growing editorial plan, not a complete course or a progress tracker. Proposed topics have no lesson pages yet.
Explore the path
1 article available
Understand the system
Identify responsibilities and follow the work before choosing a pattern.
4 min read
Trace a request before choosing a service boundary
A small report service makes responsibilities, waiting, and failure visible before you split the code.
Proposed topics (3)
- From requirements to quality constraints Planned
- Trace a request across a system boundary Planned
- Read a component map alongside a sequence Planned
0 articles available
Make a design decision
Connect each design choice to a constraint and a cost.
No articles are published here yet. The themes below describe the editorial plan; they are not available lessons.
Proposed topics (4)
- Choose a boundary before choosing a service Planned
- Strategy versus a conditional branch Planned
- Queues, retries, and duplicate work Planned
- Cache invalidation as a data ownership question Planned
1 article available
Review a change
Use the same map to explain a proposal and check its consequences.
4 min read
Review an AI-generated change with a system map
Turn a generated patch into a change you can explain: one promise, one boundary, and a few observable checks.
Proposed topics (3)
- Review an AI-generated change against a system map Planned
- Record a decision and its trade-offs Planned
- Model failure and recovery paths Planned