Rive, Fast and reliable background jobs in Go

jeffbee

They avoided all those pesky distributed systems problems by making a system that is not distributed. Hell of a claim.

leetrout

Typo in title... it's River not Rive

hasyimibhar

How does it compare to a full-fledged durable execution platform like DBOS[0], which follows the same philosophy? Looks like River does have workflows, but it's locked behind Pro [1]. [0] https://dbos.dev [1] https://riverqueue.com/docs/pro/workflows

whinvik

Curious how people use systems like this or DBOS etc. Do you self-host? Do you use the same DB as the application DB? Do you use this for API background jobs, batch jobs, cron jobs? As someone who uses Airflow a lot but not for background jobs, I am interested in the pros and cons of various approaches.

absoluteunit1

I was just asking on the Go subreddit for suggestions and River came up. My only hesitation is that many features are locked behind Pro. I normally only settle for completely open source tools that I can self host and try to avoid these “partially” open tools. For now, going to try to migrate my current stack to RabbitMQ. Seems like a very mature and completely open source tool. River does look cool but I’m not a fan of vendor lock in. Will always avoid when possible

dwrodri

I was asking around a while ago about better single-node solutions to "durable workflows" than Airflow before I was familiar with the terminology. Admittedly, Go + durable workflows in the cloud feels like the perfect marriage. Seeing the gated features makes me hesitant, unfortunately, but definitely considering this!