Managing Long Running Tasks medium
Most distributed queues guarantee 'At-Least-Once' delivery. What side effect must developers handle?
- A Messages might be lost.
- B Messages arrive slowly.
- C Messages are encrypted.
- D Messages might be delivered twice (Duplicates). Operations must be Idempotent.
Answer: D. Messages might be delivered twice (Duplicates). Operations must be Idempotent.
Exactly-once is theoretically impossible or extremely expensive (FLP theorem constraints).
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?