tembo VS BeanstalkD

Stacks[1] are basically recipes for deploying Postgres for specific use cases. This includes extensions, Postgres configs and application deployments (example: PostgREST)

For examples, you can look at https://github.com/tembo-io/tembo/tree/main/tembo-operator/s...

[1] Blog about Stacks: https://tembo.io/blog/tembo-stacks-intro/

Perhaps you mean https://github.com/CoreDB-io/coredb/tree/main/extensions/pgm...

Your link results in a 404.

There's beanstalkd, it has a few Python libraries and it works out of the box with ActiveJob via Backburner.

https://beanstalkd.github.io/

Messaging/Queueing Systems (Amazon SQS, RabbitMQ, Beanstalkd)

Not when a queue is involved. IME trying to replicate something like beanstalkd (https://beanstalkd.github.io/) in postgres is asking for trouble for anything but trivial workloads.

If you're measuring throughput in jobs/s, use a real work queue.

Before Kafka was a standard, I created a go library for beanstalkd that act like an RPC.

Then there are queue libraries like beanstalkd, RabbitMQ or built-in features like queues from Laravel. These will probably get you quicker to your goal then trying the process managing route.

The only task queue I loved was beanstalkd -- it's beautifully written and highly performant. Starting it takes seconds and it's been running for a decade:

https://beanstalkd.github.io/

It's not rust (it's C), but beanstalkd is a pretty incredible work queue that processes millions of jobs a day (10K+/s at peak) for my company. I know there are a few rust drivers available.