pgmq VS cadence

And lots of interesting extensions use it, like

https://github.com/tembo-io/pgmq

https://github.com/zombodb/zombodb

https://github.com/supabase/pg_jsonschema

Have you considered https://github.com/tembo-io/pgmq for the queue bit?

some notes about pgmq, https://github.com/tembo-io/pgmq, that is on this list. It is built as an extension in Postgres, which makes it compatible with all languages that have a Postgres driver.

There's no 'magic' to it, it uses existing Postgres features so all the performance and consistency guarantees of Postgres are to be expected. Easily gets to 10k+ concurrent reads and writes even on smaller sized Postgres instances, which is more than most applications need.

Newer project but there's no library needed. https://github.com/tembo-io/pgmq. They have a pretty simple SQL api similar to SQS. It's an extension though, so some cloud provider will not support it.

PGMQ does not require a client library, https://github.com/tembo-io/pgmq so long as your language of choice can run SQL. All the functions live in Postgres, and you just call them with SQL statement. Very similar feel and semantics to SQS.

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