job resource
A resource that represents long-running work, answered with 202 Accepted and a Location the client can poll for progress and the result.
In more detail
A job has an identifier and a state such as queued, running, complete or failed, and ends with a result or a problem document. Polling the job is a safe read; repeating the original command could start the work again. A client timeout does not stop the job on the server.
Related terms
- 202 Accepted — The HTTP status meaning the request was accepted for processing but the work has not finished yet.
- polling — Having the client ask repeatedly, on its own schedule, whether something has changed or finished.
- Location header — The response header that gives an address: where a newly created resource lives, where a job can be watched, or where a redirect points.
- asynchronous processing — Accepting a request now and doing the work later, separately, instead of making the caller wait for it to finish.
Taught in
- Actions That Do Not Fit CRUD — Modern API Architecture: REST, GraphQL & gRPC
- Large Payloads And Streaming — Modern API Architecture: REST, GraphQL & gRPC
- Event-Driven Architecture And Queues — Modern API Architecture: REST, GraphQL & gRPC