Vapor permanent load and results

Hi, I wonder if it is a good choice to use Vapor if an application permanently run jobs ?

Perhaps it would be interesting to test something with L. Vapor, for example a set of tasks that would run continuously, calls to URLs or some kind of calculation that would be called every minute.

Obviously there is a cost issue behind all this. But above all I would like to know how far it is possible to go.

The underlying question is of course whether using Laravel Vapor for an application that performs a lot of tasks in the background all the time is a good idea, especially when the number of users increases over time.

I realise that my question may be a little naive, and I have gone through the various documents, but feedback will always make the difference.

So if you have any ....