To exchange data between our standalone frontend application and the backend API, we currently have a REST API, with standard endpoint to list/create/update/destroy ressources with a consistent naming and appropriate routes e.g for users:
GET /api/v1/users: list all users GET /api/v1/users/{id}: return a specific user POST /api/v1/users: create a user PATCH /api/v1/users/{id}: update a user DELETE /api/v1/users/{id}: destroy a user However, our platform being a data processing tool, users can choose to start a task applying a certain operation to their data. The frontend will send a request to the backend in order to trigger the background job.
How should this fit in a REST API ? A background task is not a ressource as users or companies can be. I have trouble finding a way to design a good API around launching background tasks or triggering events/messages that are not considered ressources.
How would you approach this ?
The post Incorporate a background job enqueue endpoint in a REST API appeared first on 100% Private Proxies - Fast, Anonymous, Quality, Unlimited USA Private Proxy!.