Documentation
ADR-007 — Event-driven order notifications
Why we chose an event bus over synchronous calls to notify downstream services.
examples/adrAPI · v1Orders API reference
The HTTP surface for creating and reading orders.
examples/apiARCHITECTURE · AWSOrders service — cloud architecture
How the orders service is deployed on AWS, and the request path through it.
examples/cloudRFC-012RFC — Idempotent order creation
A proposal to make POST /orders safe to retry under network failure.
examples/designDECKDecoupling checkout
One idea per slide — why and how we moved order notifications to events.
examples/presentationROADMAP · FY26Notifications platform roadmap
From a coupled checkout to a self-serve notifications platform over three quarters.
examples/roadmapRUNBOOK · ON-CALLRunbook — order events lagging
Diagnose and clear a backlog on the OrderPlaced consumer.
examples/runbookWRITE-UPCutting checkout latency
How a slow, coupled checkout became a fast one — situation, complication, resolution.
examples/situationDEMO · ALIGNSlide alignment demo
How vertical alignment works — auto by default, forced with a {top}/{center}/{bottom} marker.
examples/slides-align-demoDEMO · DECKSlides demo
A quick deck to test header-based slides — each
examples/slides-demoOVERVIEWOrders system overview
How the orders system fits together — context, landscape, one module, one flow.
examples/system-overview