Graphile Worker vs River
Overview
🔥 Trending in Background Jobs on StackShare
Distributed, fault tolerant, high throughput pub-sub messaging system
Detailed Comparison
It is a job queue for PostgreSQL running on Node.js. It allows you to run jobs (e.g. sending emails, performing calculations, generating PDFs, etc) "in the background" so that your HTTP response/application code is not held up. Can be used with any PostgreSQL-backed application. Pairs beautifully with PostGraphile or PostgREST. | It is a robust high-performance job processing system for Go and Postgres. It encourages the use of the same database for application data and job queues. By enqueueing jobs transactionally along with other database changes, whole classes of distributed systems problems are avoided. |
Standalone and embedded modes;
Designed to be used both from JavaScript or directly in the database;
Easy to test (recommended: runTaskListOnce util);
Low latency (typically under 3ms from task schedule to execution, uses LISTEN/NOTIFY to be informed of jobs as they're inserted);
High performance (uses SKIP LOCKED to find jobs to execute, resulting in faster fetches);
Small tasks (uses explicit task names / payloads resulting in minimal serialisation/deserialisation overhead);
Parallel by default | Transactional enqueueing simplifies everything;
Error handling and reporting;
Multiple isolated queues;
Graceful shutdown |
Statistics | |
GitHub Stars 2.1K | GitHub Stars 4.6K |
GitHub Forks 109 | GitHub Forks 126 |
Stacks 3 | Stacks 0 |
Followers 0 | Followers 2 |
Votes 0 | Votes 0 |
Integrations | |
What are some alternatives to Graphile Worker, River?
Sidekiq
Sidekiq uses threads to handle many jobs at the same time in the same process. It does not require Rails but will integrate tightly with Rails 3/4 to make background processing dead simple.
Beanstalkd
Beanstalks's interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously.
Hangfire
It is an open-source framework that helps you to create, process and manage your background jobs, i.e. operations you don't want to put in your request processing pipeline. It supports all kind of background tasks – short-running and long-running, CPU intensive and I/O intensive, one shot and recurrent.
Resque
Background jobs can be any Ruby class or module that responds to perform. Your existing classes can easily be converted to background jobs or you can create new classes specifically to do work. Or, you can do both.
delayed_job
Delayed_job (or DJ) encapsulates the common pattern of asynchronously executing longer tasks in the background. It is a direct extraction from Shopify where the job table is responsible for a multitude of core tasks.
Faktory
Redis -> Sidekiq == Faktory -> Faktory. Faktory is a server daemon which provides a simple API to produce and consume background jobs. Jobs are a small JSON hash with a few mandatory keys.
Kue
Kue is a feature rich priority job queue for node.js backed by redis. A key feature of Kue is its clean user-interface for viewing and managing queued, active, failed, and completed jobs.
Bull
The fastest, most reliable, Redis-based queue for Node. Carefully written for rock solid stability and atomicity.
Cron
Background-only application which launches and runs other applications, or opens documents, at specified dates and times.
PHP-FPM
It is an alternative PHP FastCGI implementation with some additional features useful for sites of any size, especially busier sites. It includes Adaptive process spawning, Advanced process management with graceful stop/start, Emergency restart in case of accidental opcode cache destruction etc.
