Problems / Kubernetes and containers, medium
Each pod uses 300 MB plus 8 MB for every request it holds (about 250 ms each, waiting on other services), under a 512 MB memory limit. Normal traffic is fine; at 40 s a 2.6× surge arrives.
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.
Keep success at 99% or more through the surge.
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.
150 requests a second for 180 seconds: 100% api (reads).
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 (pods).Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| API (pods)Container platform | Load balancer forwards to it.Calls Postgres.Kubernetes places pods on nodes by their CPU and memory requests, and only replaces a lost node's pods after about 5 minutes. | 60 slots |
| PostgresSQL database | API (pods) calls it.Postgres runs one process per connection, which is why poolers like PgBouncer sit in front of busy databases. | 32 vCPU · 300 connections |