River vs RQ (Redis Queue)

River is a background job queue for Go applications, using PostgreSQL or SQLite to store jobs. Its transactional enqueueing keeps a job from running until the database transaction that inserted it has completed. The core set includes isolated queues, unique jobs, prioritization, recurring cron jobs, snoozing, transactional completion, and test helpers. A web interface, pause and resume controls, automatic retries, error reporting, and telemetry integrations support operations. River UI is optional and self-hosted, with no external service dependencies. PostgreSQL is the primary database target; SQLite support is experimental. River Pro adds workflows that split complex work into individually retryable tasks, plus batching, concurrency limits, and ordered job sequences. The free Open Source plan includes the web UI but excludes workflows, concurrency limits, and support. Pro costs $125 a month and includes email support for up to 20 developers. Enterprise pricing is custom and includes email and Slack support, unlimited developers, and access to a SOC 2 report.

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.