Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What do people use as an alternative to SQS? I've had Kafka mentioned a few times but that's way heavier/more complicated than I need. Just a simple queue is perfect, and SQS' API is gloriously simple.


RabbitMQ is a more natural alternative to SQS than Kafka I’d say. Redis can also be leveraged as a message broker depending on your needs.


Rabbit is definitely interesting. How is the maintenance/management on RabittMQ? Is it comparable to say a Postgres instance, or is it more or less?


Going simpler as possible:

Redis has a simple (but extremely powerful) Pub/Sub implementation[1] that should get you going for a long time.

Postgres also have a simple notify API[2] you can mix it with your own tables and just "notify" that some changes were made (when people say you can do anything with postgres nowadays they are not joking).

You probably can also roll your own implementation in any ACID database. Just keep adding records to an event table and consume them in scheduled batches. Should be more than enough for non real-time applications.

[1]: https://redis.io/docs/manual/pubsub/ [2]: https://www.postgresql.org/docs/current/sql-notify.html


Redis also has a Stream data type since version 5, which is designed exactly for this. No need to build something on top of lists anymore.


>Redis has a simple (but extremely powerful) Pub/Sub

Interesting - I had just assumed everyone is doing MQTT or cloud pub/sub


If SQS meets your needs then you don't need an alternative, but there are Azure Storage Queues and GCP PubSub are the closest.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: