riverqueue.com

What It Is

River is a background job queue for Go applications, backed by PostgreSQL. Its key selling point is “transaction-safe” job enqueueing: jobs can be inserted within the same transaction as your business database operations, and will only run after that transaction is committed. If the API transaction succeeds, the job is enqueued as well. Compared with external queues such as Redis, this reduces service dependencies and lowers the risk of inconsistency between transactions and asynchronous jobs.

Core Capabilities

The open-source edition is already fairly complete, with support for multiple isolated queues, unique jobs, priorities, periodic/cron jobs, snoozing, automatic retries, transactional job completion, testing helpers, error reporting, telemetry integration, and a self-hosted River UI. River UI lets you view queue depth, throughput, and failed jobs, and supports operational actions such as canceling, retrying, and deleting jobs, as well as pausing queues. It also fits naturally into the Go ecosystem, using generics to provide strongly typed parameters for Workers. The Pro edition adds more advanced capabilities such as workflows, batches, sequences, dead letter queues, encrypted jobs, resumable jobs, and global concurrency limits.

Languages, Integrations, and Documentation

River is primarily designed for Go + PostgreSQL. The documentation also mentions integrations with Bun, GORM, SQLite, PgBouncer, alternate schemas, OpenTelemetry, and more, and provides cross-language enqueueing guidance for Python, Ruby, SQL, and TypeScript. The documentation quality is strong, with sections covering migrations, reliable Workers, unique jobs, retry strategies, UI deployment, Pro modules, and advanced topics, along with plenty of sample code.

Pricing and Deployment

The open-source version of River can be self-hosted. River UI can also be run from source, as a binary, via a Docker image, or embedded into a Go application. River Pro is a paid subscription that includes commercial support and advanced features, but the main content does not disclose specific pricing, payment methods, or plan details.

Pros, Cons, and Who It’s For

Its strengths include tight integration with Postgres transactions, no need for an additional queue service, a good type-safe experience in Go, and friendly observability and UI tooling. Its limitations are that it has a relatively narrow focus and is best suited to Go/Postgres stacks; some production-grade advanced features require Pro; and if the UI is exposed publicly, authentication must be configured separately. It is a good fit for Go backend teams that want to reduce Redis/RabbitMQ operational overhead and care about consistency between background jobs and business data.

Access in China

The main content does not provide information about access from mainland China, payment, or compliance, so this is unknown. If access to GitHub, container images, or private modules is affected by network conditions, teams in China may want to evaluate alternatives such as Asynq, Temporal, Celery, BullMQ, and Graphile Worker.