Managing Long Running Tasks medium
Queues like SQS are 'Pull-based' (Workers poll for messages). What is a disadvantage of this vs 'Push-based' (e.g., RabbitMQ, WebSockets)?
- A Pulling introduces latency (wait time between polls) and wastes empty cycles when the queue is dry.
- B Push is slower.
- C Pulling is too fast.
- D Push handles backpressure better.
Answer: A. Pulling introduces latency (wait time between polls) and wastes empty cycles when the queue is dry.
However, Pull is easier to scale and control (Workers control their own load).
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?