Learning path / Editorial roadmap
Online Store Architecture: From Boundaries to Reliable Orders
Follow one purchase through a modular online store: map its boundaries, define contracts, trace checkout, schedule durable work, and recover from ambiguous outcomes. A focused five-lesson route, not a complete system-design curriculum.
5 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
2 articles available
Map the system
Define the store's promise, participants, and module contracts before choosing deployment boundaries.
5 min read
Define System Boundaries with an Online Store
Use Fieldnote, a fictional stationery shop, to turn an unclear system boundary into explicit ownership, participants, and an order-acceptance promise.
5 min read
Design Services and Contracts Without Splitting the Monolith
Assign stock, order, payment, and checkout responsibilities inside one modular backend, then specify meaningful success, pending, and failure results.
2 articles available
Follow the order
Trace local commits, the remote payment call, and durable follow-up work.
5 min read
Trace a Synchronous Checkout with a Sequence Diagram
Trace one purchase through two local commits and a remote payment call, with explicit decline and unknown-outcome branches.
5 min read
Process Orders Asynchronously Without Losing Work
Turn one accepted order into durable packing and receipt jobs, then distinguish local task uniqueness from an external email effect.
1 article available
Recover safely
Preserve operation identity and reason about unknown outcomes and business costs.
6 min read
Handle Checkout Failures with Idempotency and Explicit Trade-offs
Recover a lost payment response without inventing a decline or creating a second payment attempt, and record the costs that safe recovery still carries.