Re:I Love You, Redis, but I'm Leaving You for SolidQueue
by nick__m on Wednesday January 14, 2026 @07:52AM
(#46615458)
Frequently you have to couple the transactional state of the queue db and the app db, colocating them is the simplest way to achieve that without resorting to distributed transactions or patterns that involve orchestrated compensation actions.
[ Parent
| on HN ]
Re:I Love You, Redis, but I'm Leaving You for SolidQueue
by yawboakye on Wednesday January 14, 2026 @05:55PM
(#46625104)
that’s setting yourself up for trouble, imo. intermediate states solve this problem, and economically. for mature production system see temporal[0]. their magic sauce is good intermediate states.
[0]: https://temporal.io/
Re:I Love You, Redis, but I'm Leaving You for SolidQueue
by imtringued on Thursday January 15, 2026 @06:10AM
(#46630876)
This feels like an ad because you explained absolutely nothing.
It's one thing to explain to people what a screw driver is and you just happen to sell screw drivers to people who might need them.
It's a wholly different thing to sell the screw driver first and then let people figure out why they need it.
Re:I Love You, Redis, but I'm Leaving You for SolidQueue
by yawboakye on Thursday January 15, 2026 @06:59AM
(#46631263)
i’m not associated with temporal, nor does the link above have any referrer nonsense in there. i don’t profit from referring to it here. in fact it may well be a household name in the hn community. that out of the way, it’s not wrong to point to a proper resource that can explain and demonstrate my argument better than a couple of words could. temporal is open source[0] so maybe a github link would have been more palatable?