Design CRUD APIs backed by asynchronous jobs
Design a service that exposes create, read, update and delete APIs for a resource, where some operations start long-running work that cannot finish inside the request. Cover the API shape (how a client starts the work, checks its status and gets the result), where job state is kept, how workers pick up and retry jobs, and what the client sees when a job fails.
No answer yet. Write the first one; the best answer gets endorsed.
