← Questions
Design CRUD APIs backed by asynchronous jobs
0
I was asked this
No reports yet. Sign in to say where you were asked it.
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 official answer yet. Draw yours on the right; publish it and it shows under Community.
Nothing published yet. Publish your canvas and it shows here for others to open and remix.
Draw your answer hereBoxes, arrows and notes, saved for you to come back to.Sign in to start drawing
