Web Application Architecture - Job/Task Queue needed?
I am currently designing a web application that will allow users to schedule tasks which will be executed against an HTTP API (on behalf of them). The tasks can be recurring and the minimal time resolution that can be used for scheduling will be one minute. Because of the nature of the tasks I think it makes sense to execute them asynchronously. However, how should the architecture of this part look like? I thought about using a task queue to create tasks by the web application and let them be executed by a worker. In this case, I have several questions: How do I handle recurring tasks? How do