What is River?
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.
River is a tool in the Background Jobs category of a tech stack.
Key Features
Transactional enqueueing simplifies everythingError handling and reportingMultiple isolated queuesGraceful shutdown
River Pros & Cons
Pros of River
No pros listed yet.
Cons of River
No cons listed yet.
River Alternatives & Comparisons
What are some alternatives to 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.
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.
