Managing Long Running Tasks easy
When building an Async API, what does the `/status/{taskId}` endpoint usually return?
- A Current state (e.g., 'pending', 'processing', 'completed', 'failed') and potentially a percentage complete.
- B The final result immediately.
- C A 404 error.
- D The user's password.
Answer: A. Current state (e.g., 'pending', 'processing', 'completed', 'failed') and potentially a percentage complete.
This allows the frontend to show a spinner or progress bar.
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?