delayq VS cadence

I built this for the same problem: https://github.com/spy16/delayq/tree/main/redis

I built https://github.com/spy16/delayq

most useful: https://github.com/spy16/delayq (used in production as the backbone for a distributed crontab system with 50 million active schedules)

I built https://github.com/spy16/delayq which may or may not be helpful. Mentioning anyway. (It's uses redis, so in terms of durability whatever redise can guarantee applies.)

Uber | Software Engineers | Hybrid (Denmark) | https://www.uber.com/dk/en/careers/locations/aarhus/

Work with an amazing team responsible for the infrastructure software that makes Uber’s data centers around the world reliable and scalable. If you want to solve the toughest engineering challenges alongside some of the smartest people in the industry, Uber Aarhus is the right place for you.

The team in Aarhus build and operate the stateless and stateful compute platforms used by nearly every other engineer in the company (Up - https://www.uber.com/en-GB/blog/up-portable-microservices-re... and Odin - https://www.uber.com/en-GB/blog/how-uber-optimized-cassandra...) as well as other related infrastructure projects such as Cadence - https://github.com/uber/cadence.

May be this..https://cadenceworkflow.io/

a managed esb orchestration for example is exactly same as step functions and workflow engines like cadence - https://github.com/uber/cadence

Having done a reasonable amount of messaging code in my time, I would say the final form of this sort of thing might look more like Cadence[0] than anything like this.

[0] https://github.com/uber/cadence

Emit events from your primary DB (postgres, etc.) to something like kafka or rabbitmq and then catch that in your search engine. There's also some end-to-end solutions like temporal (temporal.io) or cadence (https://cadenceworkflow.io/)