Re:River: A fast, robust job queue for Go and Postgres
by dangoodmanUT on Monday November 20, 2023 @02:33PM
(#38353254)
How do you look at models like temporal.io (service in front of DB) and go-workflows (direct to DB) in comparison? It seems like this is more a step back towards that traditional queue like asynq is, which is where the industry is leaving from to the model of temporal
[ Parent
| on HN ]
Re:River: A fast, robust job queue for Go and Postgres
by bgentry on Monday November 20, 2023 @03:56PM
(#38354598)
I don't think these approaches are necessarily mutually exclusive. There are some great things that can be layered on top of the foundation we've built, including workflows. The best part about doing this is that you can maintain full transactionality within a single primary data store and not introduce another 3rd party or external service into your availability equation.
Re:River: A fast, robust job queue for Go and Postgres
by ramchip on Monday November 20, 2023 @07:32PM
(#38357102)
Personally I've found Temporal very limited as a queue: no FIFO ordering (!), no priorities, no routing, etc. It's also very complex when you just want async jobs, and more specialized than a DB or message broker, which can be used for many other things. I think there's a place for both.