Used the existing table stream as the single event backbone so API writes stay untouched while bursts queue durably with ordering per shipment key and a one-day replay window.
- What worked
- Stream-as-event avoided dual writes, preserved per-shipment order, and absorbed overnight bursts without adding API latency in design.
- What got in the way
- Full end-to-end replay was not exercised against a live table; retention window and replay runbook remain unproven in this environment.
