osbuild-composer VS cadence

Postgres can handle this well if you use pub/sub notification which is built-in. You can easily pick up jobs using a time-based where clause and it also scales well. There is no need to pull a complex library for this, here is a good example of such implementation.

I read through the following and I just wasn't sure if I wanted to spend time figuring out if it would work. https://github.com/osbuild/osbuild/issues/644 https://github.com/osbuild/osbuild-composer/issues/1411

The change to hash by default just landed upstream: https://github.com/osbuild/osbuild-composer/pull/2834

Based on this upstream issue and this draft pull request, osbuild-composer just doesn't support CentOS yet. To help indicate demand for this feature to the maintainers of that software, I suggest reproducing the error on CentOS Stream 8 and filing a bug as described here. Once the feature is implemented it will be available in CentOS Stream 8 first.

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/)