-
-
Notifications
You must be signed in to change notification settings - Fork 35
Description
It's common nowadays for web services to do some processing in the background, e.g. video converting, talking to external services, etc. We need some mechanism that would allow us to spin such tasks in a way that would be picked up by some external workers (with an option to run workers inside the same binary for easier development and some simpler deployment cases). We should support some industry-standard way to create a queue of such tasks, e.g. RabbitMQ.
When we have background tasks, a scheduler that would allow running background tasks at given dates and times will probably be useful, too.
When we have all of that, the tasks should be displayed in the admin panel along with their statuses (queued, running, succeeded, failed) and some tools to control them (pause/cancel, etc.).