Which message broker to choose?

Question

RabbitMQ

Good afternoon!
I have been playing with RabbitMQ for quite a long time, I even wrote a wrapper over amqplib (node.js), but more and more often it seems cumbersome and incomprehensible to me (even after half a year of active use).
Now I am developing a service entirely tied to message brokers. The write-read speed is not particularly important, but I would like not to be much inferior to RabbitMQ.
Hence the question itself, which alternative to look at in the near future? I'd love to hear the pros and cons of all options.
Of the requirements:
* Availability of clients for GO, Python and JS.
* acceptable speed (at the level of RabbitMQ)
* the ability to configure the server to store queues on disk (including in sync mode), so that nothing is lost when the server is restarted

Answer 1

If persistence is not important (it's okay to lose messages sometimes) - you can look at the PUB / SUB mechanism in Redis . Very fast, lightweight and as simple as three rubles. Clients for Redis , of course, are available for all at least some popular languages.

Answer 2

If you want another broker, then there are many. For every taste and color. Although I myself use rabbitmq, I recommend paying attention to kafka.apache.org
If you want without a dedicated server, look towards akka. It works faster than through a broker, it can store the state and a bunch of other things.

Answer 3

so there are only two of them - the second ZeroMQ
Gearman, alas, is too simple
, there are enough articles on the hub, plus, for example,
docs.celeryproject.org/en/latest/getting-started/i...