Gearman vs JobRunr

Gearman is a free, self-hosted application framework for distributing work across machines or processes. A client submits jobs, a job server routes them, and a worker performs them, allowing parallel processing and load balancing. Jobs can run asynchronously in the background or receive priorities. Clients and workers may use different language interfaces when they understand the workload; listed interfaces include C, C#/.NET, Go, Java, Node.js, PHP, Perl, Python, Ruby, Rust, and Lisp. Messages can reach 4 GB, with chunking for larger messages. Clients and workers can connect to multiple job servers and fail over when one dies. The C job server supports persistent queues. MySQL and PostgreSQL functions expose client calls to queries, triggers, and stored procedures, while the pure Perl API supports SSL. Gearman runs on Linux and Windows, offers API access, and is licensed under BSD. GearmanSharp is incomplete.

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.