Managing Long Running Tasks easy
The architectural pattern where one service creates tasks and another processes them is called:
- A Client-Server.
- B Producer-Consumer.
- C Peer-to-Peer.
- D Master-Slave.
Answer: B. Producer-Consumer.
The Producer (Web App) produces tasks. The Consumer (Worker) consumes (processes) them.
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)?
- 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?
- When implementing retries for failed tasks, why use 'Exponential Backoff' with 'Jitter'?