Problems / Async and streaming, medium
The API writes the order to the database, then publishes an event. At 10 s the queue is unavailable for 5 seconds: orders are saved but their events vanish.
Unlock it once for 15 credits; everything inside it is free (runs, changes, Submit, results, hints). Sign in with Google to start; new accounts get free credits.
No lost events, success ≥ 99%.
Like a coding problem, a solution has to pass every case, not just the one it was built for. Submit in the lab runs all 5; 2 of them are hidden until then.
600 requests a second for 30 seconds: 100% submit (writes).
What each component does in this design, and what calls it. The simulator mimics each one from these settings.
| Component | Its job here | Settings |
|---|---|---|
| Load balancerLoad balancer | Traffic enters here.Calls API.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| APIApp service | Load balancer forwards to it.Calls Orders DB, Job queue (SQS) (publishes).Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s. | 3 replicas × 200 slots · timeout 1.0 s |
| Orders DBSQL database | API calls it.Postgres runs one process per connection, which is why poolers like PgBouncer sit in front of busy databases. | 8 vCPU · 60 connections |
| Job queue (SQS)Message queue | API publishes to it.Calls Workers.If a consumer does not finish within the visibility timeout, the message is delivered again. | – |
| WorkersWorker | Job queue (SQS) consumes from it.Calls Results DB.Queues deliver at least once, so a worker can see the same message twice. | 16 concurrent jobs |
| Results DBSQL database | Workers calls it.Postgres runs one process per connection, which is why poolers like PgBouncer sit in front of busy databases. | 8 vCPU · 60 connections |