asynchronous processing
Accepting a request now and doing the work later, separately, instead of making the caller wait for it to finish.
In more detail
An asynchronous API answers with 202 Accepted and a way to follow progress: a job to poll, a webhook or a stream. The job needs visible success and failure states so the caller never has to guess.
Related terms
- 202 Accepted — The HTTP status meaning the request was accepted for processing but the work has not finished yet.
- 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.
- message queue — A store that holds messages from producers until consumers are ready to process them, decoupling the rate of arrival from the rate of work.
- webhook — An HTTP request a provider sends to an address you registered, to tell you an event happened, instead of you polling for it.
Taught in
- Event-Driven Architecture And Queues — Modern API Architecture: REST, GraphQL & gRPC
- Observability: Logs, Metrics, Traces — Modern API Architecture: REST, GraphQL & gRPC