Cron job bundling
E
Eric Mayefsky
I will have a bunch of different small cron jobs related to my web service that deal with unrelated parts of my system and/or need to be run at different frequencies. Currently having every cron command as a totally separate service isn't great from a housekeeping perspective (I want them all to have the same environment set up as my web service) and also seems not great from a pricing/incentives perspective. For example it seems like it would be cleaner if I had a separate command for weekly jobs and daily jobs (instead of combining them and using code logic to decide what to run), but if I do that today I would be charged twice as much.
I would be happy to pay a higher fixed fee to use the cron system, but not have payment be a function of the number of jobs that all point to the same repo+db; or to pay based on server/compute time (this is how Heroku Scheduler works, I think I am one of many Heroku expats here, maybe that's why this feels natural :-) ).
Log In
d
dev
+1 It's annoying to have to plan to have multiple deployments all using the exact same image (repo) just to run slightly different commands on different schedules. Not to mention trigger multiple rebuilds on changes. Even if this was an abstraction that used multiple services behind the scenes, it would make it easier to manage.