Problems / Scaling, easy
The API renders pages on the server: 6 ms of CPU per request on 2 vCPUs per replica, at 1,500 req/s.
Unlock it once for 10 credits; everything inside it is free (runs, changes, Submit, results, hints). Sign in with Google to start; new accounts get free credits.
Success ≥ 99%, p99 ≤ 500 ms. Don’t let the API crash.
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 3; 1 of them are hidden until then.
1,500 requests a second for 30 seconds: 90% reads, 10% 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 Redis cache (checked first), Postgres.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 |
| Redis cacheCache | API checks it first for reads.An in-memory cache like Redis usually answers in well under a millisecond inside one region. | 95% hit rate |
| PostgresSQL database | API reads it when Redis cache misses. API calls it for writes.Postgres runs one process per connection, which is why poolers like PgBouncer sit in front of busy databases. | 8 vCPU · 60 connections |