Long Running Process
On Scalingo, HTTP requests to your application need to be processed in less than 30 seconds. More generally, this is a best practice for a HTTP request to be as short as possible. You may wonder what you need to do in case your application has a long process to execute in reaction to a user interaction. This page aims at explaining how you could achieve this in your application.
The HTTP Status 202
Whenever your application needs to execute a long running process (more than a few seconds), it should
- Create a resource in your application database with a status such as
- Publish a message on a message queue.
- Return a HTTP status code
202 Acceptedto the client. This status code means that the request has been accepted and will be processed asynchronously.
Asynchronously, a worker should handle the processing of the resource created in the database and update its status, from
processed. The client could poll the status of this resource at regular interval to determine when the process is over.
There is various message queue system depending on the programming language and the framework your application uses:
- Ruby: Delayed Job, Sidekiq or Resque.
- PHP: Symfony Messenger or Laravel Tasks Scheduler
- Node.js: Bull.
- Python: Celery.