JobRunr vs RQ (Redis Queue)

JobRunr is a distributed Java library for processing background jobs and scheduling asynchronous work on the JVM. It supports fire-and-forget, delayed, and recurring tasks, and describes jobs as persistent through cluster restarts or failures. The free OSS plan includes enqueueing and scheduling, automatic retries, carbon-aware scheduling, and a simple dashboard; it allows up to 100 recurring jobs depending on the database. Official integrations are available for Spring Boot, Micronaut, and Quarkus, and the library works with Java 8 and later as a jar distributed through Maven Central. Before production use, the guide recommends replacing in-memory storage with a persistent SQL or NoSQL provider. Business adds priority queues, workflows, realtime scheduling, and a transaction plugin; its license covers one production cluster, while development, test, and staging are free and unlimited. Business costs €850 per PRD cluster / month. Enterprise pricing is custom and includes unlimited recurring jobs and clusters, a multicluster dashboard, and Kubernetes autoscaling metrics.

RQ (Redis Queue) is a Python library for placing jobs in queues and running them asynchronously in background worker processes. It is self-hosted, open source under the BSD license, and free. It requires Redis 5 or later, or Valkey 7.2 or later. RQ supports scheduled and repeating jobs, retries, bulk enqueueing, job groups, dependencies, unique jobs, and concurrency rate limits. Unique jobs cannot be combined with dependencies. Failed jobs are recorded with exception information, and custom exception handlers are supported. For monitoring, there is an `rq info` console command; RQ Dashboard is a separate web-based frontend. Documentation covers Django, including django-rq, as well as usage with Heroku, Sentry, Supervisor, and systemd. RQ serializes jobs with pickle by default, which the project warns is safe only with trusted Redis instances; JSON is an alternative. Workers need a system that supports `fork()`, so Windows requires Windows Subsystem for Linux and a bash shell. Workers must also be able to import job functions, and producers and workers must share source code.