Managing Long Running Tasks medium
Why is 'Queue Depth' (ApproximateNumberOfMessagesVisible) a critical metric for auto-scaling workers?
- A It determines the price.
- B It is not useful.
- C It indicates the backlog. If Depth > 1000, add more workers. If Depth == 0, remove workers to save money.
- D It shows CPU usage.
Answer: C. It indicates the backlog. If Depth > 1000, add more workers. If Depth == 0, remove workers to save money.
The primary signal for consumer lag.
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?