Quartz VS JobRunr

In java we have found Quartz( Quartz) , Job Runr(Jobrunr) and db-scheduler(db-scheduler) and need to evaluate these for our use case.

Im mit sit what you mean by "not supported", you sure can run MongoDB on Kubernetes. Maybe I'm way off, are you saying that you can't use Quartz (this one: http://www.quartz-scheduler.org/ ?) because it doesn't natively allow you to load from MongoDB and.therefor you can't use it?

Uh this class is even worse, SDF is not a thread safe date formatter, so it never should be `final static`. `releaseDate` and `new Date()` will be ignorant of summer/winter time changes. For such scheduling one should use Quartz https://www.quartz-scheduler.org/

Have a look at http://www.quartz-scheduler.org/ If you're using Java

Long time I used http://www.quartz-scheduler.org which worked nicely, I wonder why Scala does not seem to have something standard for this.

Quartz Scheduler

We have a separate service for running cron jobs. It uses Quartz (http://www.quartz-scheduler.org/) and it has a REST API that we use to submit new jobs. It's easy to set up and all you need is a database. You definitely need a database in order to synchronize across different containers.

In java we have found Quartz( Quartz) , Job Runr(Jobrunr) and db-scheduler(db-scheduler) and need to evaluate these for our use case.

You can also take a look at https://www.jobrunr.io/en/

Hi all, I'm Ronald - the creator of JobRunr.

First of all, thanks to @mooreds to post JobRunr on HackerNews.

Second of all - I read some claims that being in the 'job scheduling' business is easy money. I would like to point out that's not really the case.

With JobRunr being open-source and more successful than I ever could imagine, this brings along a lot of stress. If you make a mistake (which I did in V6) the whole world starts to see it. I also try to keep the amount of open issues really small as these things linger in my head and also give me stress.

Anyway, this to say that I'm now able to provide my family with food but I'm still not break even (meaning if I just had freelanced as before, I would have more money in my bank account).

But, I can now work on something I love.

P.s.: it's indeed LGPL but this is also the case for hibernate. It means you should only open-source if you're touching part of the JobRunr code, not if you just use the lib.

See also https://github.com/jobrunr/jobrunr/discussions/769.

Is there a lightweight background job runner framework in Scala? Something that's backed by a database so the jobs are durable? I found jobrunr which seems like a great framework, but it's Java and doesn't have an async API (i.e. each job is assumed to be blocking and runs on its own thread).

JobRunr looks interesting, perhaps it can useful to you: https://github.com/jobrunr/jobrunr