Absorb flash-sale order bursts without losing messages
Task 2.1: Design scalable and loosely coupled architectures
QuestionWatch the method
Predict first. Then watch short phrases—not full sentences—drive the decision.
Scenario
Brightline Supply runs its order API on ECS, and each request writes the order straight into an RDS for PostgreSQL instance that downstream fulfilment and finance both read.
During last month's flash sale arrivals jumped from 40 to 900 orders a second; the database saturated, API latency climbed, and about 3,000 checkout requests timed out and were never recorded.
The platform lead wants arrival spikes held durably until the database can take them, and any order that keeps failing parked somewhere the on-call engineer can inspect rather than retried forever.
Fulfilment and finance already query the relational order tables, so RDS must stay the system of record.
Question
Which architecture should the platform lead adopt?
Activity timeline · 1 events
- 01coach · Make a prediction, record your confidence, then watch the reasoning method.