Problems / Async and streaming, medium
2,000 events/s into a 6-partition stream with 30 s retention. 3 consumers.
Free to open. Runs in your browser, no sign-up.
No data lost to retention. Consumers must keep up with producers.
2,000 requests a second for 120 seconds: 100% event (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 Ingest API.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header. | – |
| Ingest APIApp service | Load balancer forwards to it.Calls Event stream (publishes).Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s. | 2 replicas × 200 slots · timeout 1.0 s |
| Event streamEvent stream | Ingest API publishes to it.Calls Consumer group.Kafka keeps order only within a partition, so the partition key decides what stays in sequence. | 6 partitions · retention 30 s |
| Consumer groupWorker | Event stream consumes from it.Queues deliver at least once, so a worker can see the same message twice. | 3 concurrent jobs |