using zeebe/Camunda at work. The system gives you a way of designing and partitioning message-based workflows. It has a very thorough design.
Ask HN: What's your go-to message queue in 2025?
31–40 of 99 posts
Re: Ask HN: What's your go-to message queue in 2025?
#32I 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 (:
A classic. Not something I personally use these days, but I think just as a piece of software it is an eternally good example of something simple, powerful, well-engineered, pleasant to use, and widely-compatible, all at the same time
Re: Ask HN: What's your go-to message queue in 2025?
#33The US Federal Reserve uses IBM MQ for the FedNow interbank settlement service that went live last year.
Architecture info: https://explore.fednow.org/resources/technical-overview-guid...
Re: Ask HN: What's your go-to message queue in 2025?
#34I played with most message queues and I go with RabbitMQ in production. Mostly because it has been very reliable for years in production at a previous company, and doesn’t require babysitting. Its recent versions also has new features that make it is a descent alternative to Kafka if you don’t need to scale to the moon. And the logo is a rabbit.
Datadog too. i often wonder how come more companies dont pick cute mascots. gives a logo, makes everyone have warm fuzzies immediately, creates pun opportunities.
inb4 "oh but you wont be taken seriously" well... datadog.
Re: Ask HN: What's your go-to message queue in 2025?
#35Postgres. 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?
Re: Ask HN: What's your go-to message queue in 2025?
#36Postgres. 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?
We also use Postgres but we don't have many jobs. It's usually 10-20 squedule that creates hourly-monthly jobs and they are mostly independent.
Currently a custom made solution but we are going to update it to use skip locked and use Notify/Listen + interval to handle jobs. There is a really good video about it on YouTube called: "Queues in PostgreSQL Citus Con."
Re: Ask HN: What's your go-to message queue in 2025?
#37Postgres. 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?
You can go an awfully long way with just SELECT … FOR UPDATE … SKIP LOCKED
Re: Ask HN: What's your go-to message queue in 2025?
#38using 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.
Re: Ask HN: What's your go-to message queue in 2025?
#39The US Federal Reserve uses IBM MQ for the FedNow interbank settlement service that went live last year. Architecture info: https://explore.fednow.org/resources/technical-overview-guid...
Likely implies z/OS is common on both sides. Given the stakes and availability needs not a bad choice.
Re: Ask HN: What's your go-to message queue in 2025?
#40I've used Qless for several years;
For those unfamiliar, it's a Lua library that gets executed in Redis using one of the various language bindings (which are essentially wrappers around calling the Lua methods).
With our multi-node redis setup it seems to be quite reliable.