SQS
Ask HN: What's your go-to message queue in 2025?
21–30 of 99 posts
Re: Ask HN: What's your go-to message queue in 2025?
#22For large applications in a service-oriented architecture, I leverage Kafka 100% of the time. With Confluent Cloud and Amazon MSK, infra is relatively trivial to maintain. There's really no reason to use anything else for this. For smaller projects of "job queues," I tend to use Amazon SQS or RabbitMQ. But just for clarity, Kafka is not really a message queue -- it's a persistent structured log that can be used as a…
> This means you can really only have one client per topic, because once the message is consumed, it's no longer available to anyone else.
It depends on your use case (or maybe what you mean by "client"). If I just have a bunch of messages that need to be processed by "some" client, then having the message disappear once a client has processed it is exactly what you want.
Re: Ask HN: What's your go-to message queue in 2025?
#23NATS.io because I'm using Go, and I can just embed it for one server [0], one binary to deploy with Systemd, but able to split it out when scaling the MVP.
Re: Ask HN: What's your go-to message queue in 2025?
#24No one ever seems to use it, but for AMPQ I like Beanstalkd. It’s fast, stable and has not failed me under high RPS.
This is my go-to solution as well. It is great, but utilizes just one CPU core. But if this the problem, then your business is already booming.
Re: Ask HN: What's your go-to message queue in 2025?
#25For large applications in a service-oriented architecture, I leverage Kafka 100% of the time. With Confluent Cloud and Amazon MSK, infra is relatively trivial to maintain. There's really no reason to use anything else for this. For smaller projects of "job queues," I tend to use Amazon SQS or RabbitMQ. But just for clarity, Kafka is not really a message queue -- it's a persistent structured log that can be used as a…
We build applications very differently. SQS queues with 1000s of clients have been a go to for me for over a decade. And the opposite as well — 1000s of queues (one per client device, they’re free). Zero maintenance, zero cost when unused. Absurd scalability.
Re: Ask HN: What's your go-to message queue in 2025?
#26I 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 (:
Re: Ask HN: What's your go-to message queue in 2025?
#27[dead]
Re: Ask HN: What's your go-to message queue in 2025?
#28Postgres. Doing ~ 70k messages/second average. Nothing huge but don’t need anything dedicated yet.
Re: Ask HN: What's your go-to message queue in 2025?
#29For my extremely specialized case, I use a SQLite database as a message queue. It absolutely wouldn't scale, but it doesn't need to. It works extremely well for what I need it to do.
Re: Ask HN: What's your go-to message queue in 2025?
#30Postgres. 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?