Managing Long Running Tasks hard
What is the benefit of 'Consumer Groups' in Kafka compared to standard queues?
- A Broadcast + Scale. Multiple applications (Groups) can all receive a copy of the message stream (Broadcast). Within each Group, workers share the partitions (Scale).
- B It is faster.
- C It is cheaper.
- D It supports SQL.
Answer: A. Broadcast + Scale. Multiple applications (Groups) can all receive a copy of the message stream (Broadcast). Within each Group, workers share the partitions (Scale).
Combines the benefits of Topics (Pub/Sub) and Queues (Work Distribution).
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- What is the primary purpose of a Dead Letter Queue (DLQ)?
- The architectural pattern where one service creates tasks and another processes them is called:
- In a Priority Queue system (High vs Low), what is 'Starvation' and how do you fix it?
- How do you atomically update your local database AND publish a message to a queue without losing sync if the process crashes in between?
- What does 'Fire and Forget' mean?
- Why might you 'Throttle' (limit the speed of) your background workers?