Maybe start by explaining what you want to use it for?
Ask HN: What's your go-to message queue in 2025?
41–50 of 99 posts
Re: Ask HN: What's your go-to message queue in 2025?
#42I prefer pulsar. Elegant modular design and fully open source ecosystem.
Performance is at least as good as Kafka.
For simpler workload, beanstalkd could be a good fit, either.
Re: Ask HN: What's your go-to message queue in 2025?
#43SQS is great if you're already on AWS - it works and gets out of your way.
Kafka is a great tool with lots of very useful properties (not just queues, it can be your primary datastore), but it's not operationally simple. If you're going to use it you should fully commit to building your whole system on it and accept that you will need to invest in ops at least a little. It's not a good fit for a "side" feature on the edge of your system.
Re: Ask HN: What's your go-to message queue in 2025?
#44Another option to consider: Cloudflare Workers. They have a simple queue but you'll need to patch it with a Worker anyway. This means you can programatically manage the queue through the worker and also it makes it easy to send/receive HTTP requests.
Re: Ask HN: What's your go-to message queue in 2025?
#45I am using Beanstalkd, it is small and fast and you just apt-get it on Debian. However, I have noticed that oftentimes devs are using queues where Workflow Engines would be a better fit. If your message processing time is in tens of seconds – talk to your local Workflow Engine professional (:
In that case, any suggestions if the answer was looking for workflow engines? Ideally something that will work for no-person-in-the-middle workloads in the tens of seconds range as well as person-making-a-decision workflows that can live for anywhere between minutes and months?
Re: Ask HN: What's your go-to message queue in 2025?
#46using zeebe/Camunda at work. The system gives you a way of designing and partitioning message-based workflows. It has a very thorough design.
We had a lot of reliability isdues with zeebe/camunda (granted we started using it at version 0.10), and now they also rugulled the free version. So I would never go near that company again.
reliability is much better now, as far as i can tell.
Re: Ask HN: What's your go-to message queue in 2025?
#47Postgres. Doing ~ 70k messages/second average. Nothing huge but don’t need anything dedicated yet.
Curious what kind of hardware you're using for that 70K/s?
Re: Ask HN: What's your go-to message queue in 2025?
#48What do people think of Supabase?
Re: Ask HN: What's your go-to message queue in 2025?
#49Postgres. Doing ~ 70k messages/second average. Nothing huge but don’t need anything dedicated yet.
I'm curious on how people use Postgres as a message queue. Do you rely on libraries or do you run a custom implementation?
Just select for update skipped locked. Table is partitioned to keep unprocessed small.
Re: Ask HN: What's your go-to message queue in 2025?
#50Postgres. Doing ~ 70k messages/second average. Nothing huge but don’t need anything dedicated yet.
Curious what kind of hardware you're using for that 70K/s?
It’s an r8g instance in aws. Can’t remember the size but I think it’s over provisioned because it’s at like 20% utilisation and only spikes to 50.