Managing Long Running Tasks easy
Why is it important to return a unique 'Job ID' when accepting a long-running task?
- A It looks professional.
- B Used for billing.
- C It serves as a handle/ticket for the client to check status or cancel the task later.
- D To encrypt the task.
Answer: C. It serves as a handle/ticket for the client to check status or cancel the task later.
Without a Job ID, the client loses track of the request.
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?