Managing Long Running Tasks medium
How does 'Long Polling' improve upon standard Polling?
- A It is faster to code.
- B It uses UDP.
- C Efficiency. Instead of returning 'Not Ready' immediately, the server HOLDS the connection open (e.g., for 20s) until new data arrives, reducing the number of empty requests.
- D It uses more bandwidth.
Answer: C. Efficiency. Instead of returning 'Not Ready' immediately, the server HOLDS the connection open (e.g., for 20s) until new data arrives, reducing the number of empty requests.
Reduces network chatter and header overhead by 90%+ for sparse events.
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?