4 ms·
Interesting, I would have though a solution like https://temporal.io/ https://temporal.io/ would be more appropriate for these use cases. a job queue might jus
by orefalo 3y ago
Interesting, I would have though a solution like https://temporal.io/ https://temporal.io/ would be more appropriate for these use cases.
a job queue might just be the tip of the use cases iceberg... isn't it?
in the end it's a pub/sub - I use nats.io workers for this.
arf, just read a few comments on this same line down bellow.
- meowtimemania 3y agoThe main benefit of something like River is simplicity. With River your application might consist of two components, a database, and a code server. Such an architecture is really easy to test, develop, debug and deploy. Adding temporal.io means introducing a third component. More components usually means more complexity. More complexity means more difficult to test, develop, debug and deploy. As with everything, it's all about tradeoffs.