rabbitmq-server

The linked github page gives me 404. But here are the release notes: https://github.com/rabbitmq/rabbitmq-server/blob/main/releas...

Here is what I dislike about RabbitMQ: by default it opens several ports on external interfaces and doesn't provide an easy way to bind them to localhost only. To be specific, those are epmd port 4369, and RabbitMQ's ports 5672, 15672, and 25672. With help of Google I managed to move three of those ports to localhost, however the cluster communications port 25672 cannot be bound to localhost only. I found an issue on Github and developers' point is that it doesn't make sense to build a cluster from a single node, so you must have this port exposed to whole Internet so that any random stranger can connect to your RabbitMQ instance [1]. So it seems that RabbitMQ wants to advertise how scalable it is by enabling clustering by default and accepting connections from anyone even though it is not secure. It is targeted at large corporations wit

Unfortunately, Rabbit's implementation of MQTT has some pretty serious deficiencies which you may find ends up being a deal-braker (e.g. https://github.com/rabbitmq/rabbitmq-server/issues/2556).

After a brief glimpse at the documentation, I am missing a feature comparable to Kafka's partitioning. Well, the protocol [1] briefly mentions it, but it does not seem to be exposed. Getting insights into the roadmap for this would certainly be interesting... [1]: https://github.com/rabbitmq/rabbitmq-server/blob/v3.9.x/deps...

As much as I like Redis and Antirez, I have to completely agree with this article. I would just point out that Pivotal (current Redis sponsor) runs RabbitMQ; no doubt that they have in-house knowledge about message brokers. No idea if they are willing to put time into Disque. First version of RabbitMQ was released in 2008 and there have been more that 50 releases so far[2]. No doubt that maintaining a product like this is a lot of effort. [1] https://www.rabbitmq.com/ [2] https://github.com/rabbitmq/rabbitmq-server/releases

Nope. I'm barely literate in Erlang, but it looks like they haven't fixed it, unless they've wrapped the backing queue somewhere: https://github.com/rabbitmq/rabbitmq-server/blob/master/src/...

Horrible link title: "They said high level languages relieved us from thinking about memory issues" High level languages do relieve us from thinking about memory. The linker allows you to forget about program layout in memory and executable. C and other "system" languages free you from managing byte alignment for your structures, byte order and more, and very high level languages even manage your memory use with automatic garbage collection. Locality is a concern in all these languages, and there's no abstraction for that (yet). The simple solution to the issue presented in the article itself is any of the following: 1. Remove the call to len(). Handle the empty case from the drop/get/peek call, which would appear to be the idiomatic style for Erlang. 2. Track the size of the queue as is suggested in the docs, to improve the efficiency of

I just picked a random file in RabbitMQ to see how erlang looks like - https://github.com/rabbitmq/rabbitmq-server/blob/master/src/... Then I thought of looking into something I might understand: https://github.com/apache/couchdb/blob/master/src/couchdb/co... The syntax is indeed scary. Unless erlang provides features that are overwhelmingly compelling that I just cannot live without, I cannot imagine coding in it. Go seems more approachable.

As it's all open source, I guess you can look at the code and judge whether it's a mess or not. https://github.com/libguestfs/libguestfs https://github.com/rabbitmq/rabbitmq-server