Problems / Real world, easy
A campaign sends 700 push notifications a second through a push provider whose plan allows 30,000 a minute.
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%.
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.
700 requests a second for 30 seconds: 100% 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 Notification service.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| Notification serviceApp service | Load balancer forwards to it.Calls Push provider (APNs/FCM).Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s. | 3 replicas × 200 slots · timeout 4.0 s |
| Push provider (APNs/FCM)Notification service | Notification service calls it.Email, SMS and push providers all throttle senders and can delay delivery. | 200 slots · 30,000 calls/min |