← All parts

Capacity Planning

Design a Pub-Sub / Message Queue · Part 5
Problem context

Design a durable, high-throughput message system that decouples producers from consumers: producers append events; many independent consumer groups read them at their own pace, replay history, and survive each other's failures.

This is the Kafka lineage — a partitioned, append-only log, not a transient queue. In scope: publishing to a topic, consuming as part of a group while committing progress, replaying from any offset, and retaining messages for a window or compacting the log (keeping only the latest record per key, dropping older ones).

What a strong answer sounds like

State the decision, connect it to a requirement, and name the tradeoff. Keep the design focused on the workload in the prompt.

Ready for the capacity planning interview?

The AI interviewer asks about this part of Design a Pub-Sub / Message Queue. The interviewer guides you through topics one by one.