Choose a specific buying criteria from the list and see what real users have to say about it.

RabbitMQ Room for Improvement

Anonymous avatar x60
Software Engineer at a marketing services firm with 51-200 employees
* The product has to improve the crisis management, especially in memory issues. * Its clustering feature also needs improvement. * I would simplify the configuration. I would add default configuration that prevents the queue system from filling out the server storage. * I would also decouple the queue from the RabbitMQ Management, so that the queues won't get stuck. * Clustering and clustering crisis management: When the cluster falls, there needs to be a simple way to recover it. It currently suffers from a recover problem. view full review »
Anonymous avatar x60
Software Engineer at a tech vendor with 1,001-5,000 employees
After creating a RabbitMQ service, they provide you with a sort of web management dashboard. The dashboard allows you see things on your queues, purge/delete queues, etc. The dashboard is pseudo-real time, refreshing every N secs/mins, specified with a drop down. I’d like this dashboard to use web sockets, so it would actually be in real time. It would slightly increase debugging, etc. view full review »
A12a5617 98a9 495c b848 deeba2953183 avatar
Senior Developer/Architect at a tech services company with 51-200 employees
RabbitMQ is clearly better supported on Linux than it is on Windows. There are idiosyncrasies in the Windows version that are not there on Linux. The documentation for the Windows version is also less plentiful and less accurate. The online community clearly provides better Linux support, but this naturally follows from the smaller Windows installed base. There are also some potential concerns about how we maintain high-availability whilst also scaling out. view full review »
7b661919 089e 4f2d b1f3 1ac7dd1624ce avatar
Technical Manager at a government with 501-1,000 employees
The debugging capabilities and testing flexibilities need to be improved. view full review »
C19ab58b d8f3 49ae b4a2 e26601903617 avatar
Head of Data & Infrastructure at a tech services company with 51-200 employees
* The product should have much better scaling and scalability capabilities. Currently, they're really falling behind some of the competitors such as Kafka and NSQ. * The installation of the HA version and clustering mechanism should be made much easier. * The fact that a single queue can't be distributed across multiple instances/nodes is a major disadvantage. view full review »
Anonymous avatar x60
VP of Software at a manufacturing company with 11-50 employees
The biggest area we struggled with was operations troubleshooting. We were running a pretty big cluster and ended up with some random cluster failures that were difficult to troubleshoot. A good portion of these were self inflicted but occasionally the distributed database would end up corrupted. view full review »
68793ce1 7ec5 46ad b508 9452ba61f7f0 avatar
Head of Cloud Platform Development at a tech vendor with 501-1,000 employees
The web management tool. view full review »
Anonymous avatar x60
President, Applications and Security Architect at a tech services company with 51-200 employees
The documentation needs to be improved. There's a learning curve on setting it up and there are issues arising from slower networks that they lack documentation on. view full review »
4cb2a777 25cc 448e a837 019f3ca9baad avatar
Senior Software Engineer at a hospitality company with 1,001-5,000 employees
The High Availability feature is not really reliable. It also took a really long time to restart the box when there were a lot of messages in the queue. As mentioned on its document page ( https://www.rabbitmq.com/partitions.html ), it cannot tolerate network partition well. I suffered a network parturition with 3 nodes cluster and lost all data. So with our cloud provider, we can’t rely on pause_minority and seems like auto_heal is a better fit for us. Apart from that, RabbitMQ doesn’t seem to be stable when it has high RAM usage. Especially when you have millions of queue items in a queue and a node crashes, adding a new node to such cluster will be a pain as the replication takes forever. view full review »
Anonymous avatar x60
Director - Information Technology at a transportation company with 51-200 employees
* RabbitMQ is great, but it depends on the Erlang VM. * I understand that Erlang is the reason why RabbitMQ is what it is. However, having to install and maintain yet another VM product has been annoying. * The configuration for RabbitMQ borders on the esoteric. Once we got all of the moving parts working, it’s been a dream. However, it was an effort just to get it going. view full review »
Anonymous avatar x60
Software architect & back-end engineer at a tech services company
* Have more features such as being able to replay a sequence of what was received. * Handle more messages per second. * Consume fewer resources: NATS can handle millions of requests within a few minutes. RabbitMQ handles hundreds of requests with the same resources (RAM). Finding a way to be more efficient in this aspect would open them up to other markets, like IoT or embedded systems. view full review »
Anonymous avatar x60
Solutions Architect at a tech services company with 1,001-5,000 employees
I want it to reorder messages in a queue, if possible. If you could reorder messages in a queue directly, then you would not need a sequencer to reorder messages outside of RabbitMQ. view full review »
Aa76054f fdcd 4e62 b6ac c57b566e75d2 avatar
DevOps Deployment Engineer at a media company with 501-1,000 employees
The GUI management could use updating. The front-end has a look and feel that's outdated. view full review »
Anonymous avatar x60
Senior Software Specialist at a security firm with 1,001-5,000 employees
* You cannot edit shovels other than by recreating them. * Routing of data could be more enhanced with a nice GUI. ("IF header.contains(this.thing) THEN data.goesTo(cluster_02)"). * In its current form, you have to recreate a shovel with the same parameters except for the one you want to change. You end up doing more or less a delete/create. * There is no HTML form where you can click on a shovel and adjust the wrong parameter. * If I click on a shovel, I get on a page that lists the shovel, but it is not editable. You have to create a shovel and then delete the old one with all the same parameters, except for the one you want to change. * Temporarily stopping shovels is also not possible in the web interface. I do not know if the CLI version can do it, but if somebody wants to temporarily stop the incoming flow, he or she has to delete the shovel and then recreate it afterwards. This is annoying, to say the least. * RabbitMQ has to be started before one can define exchanges, queues, and even users with rabbitmqctl. See https://www.rabbitmq.com/man/r... ( https://www.rabbitmq.com/man/rabbitmqctl.1.man.html ) * This is no problem if one lives in the monolithic server environment. However, if one wanted to make a RabbitMQ Docker-container with a pre-defined set of exchanges, queues, users, and shovels, you have to literally jump start the server. You would have to configure it in the Docker build phase. You would do it like this in the Dockerfile: RUN service start rabbitmq-server && wait 30 && rabbitmqctl add_user mike mikespassword. view full review »
Anonymous avatar x60
Development Lead - Java/Hybris at a Consumer Goods with 10,001+ employees
The solution needs improvement on performance. view full review »
Anonymous avatar x60
Full Stack Developer Intern at a tech vendor with 1,001-5,000 employees
I would love to see better documentation/demo for few technologies. There is need for better stability in the Windows environment. view full review »
Anonymous avatar x60
Mid Level Software Engineer at a tech services company with 501-1,000 employees
Support for Windows systems needs to improve. This could move Microsoft shops away from it. We provisioned Linux servers specifically for our RabbitMQ servers. RabbitMQ clusters run on two kinds of protocols: AMQP and HTTP. The one we were using was AMQP (this requires all your cluster nodes to be in the same network partition). With our Windows servers, every time we used to run Puppet, RabbitMQ used to think it got partitioned. This problem never occurred in our Linux cluster. All this is subjective. Maybe we were doing something wrong. There are a few other things which they have listed here: https://www.rabbitmq.com/windows-quirks.html Overall, I don't think it's RabbitMQ's fault because Windows can be a problematic OS at times. So, I would recommend using Linux servers instead of Windows servers for a RabbitMQ cluster. view full review »
Anonymous avatar x60
Senior Application Developer at a software R&D company with 51-200 employees
I would like to see improvements in fluent configuration. I'd also like to see more support for code-first environment configuration. We do a lot of this stuff as part of our deployment process via command line scripts, but I'd rather have a specific API to target rabbitmq.config and rabbitmq-env.config so that configuration could scale with my environments more easily. If more of that was baked into the RabbitMQ management HTTP API, it would help. view full review »
22819373 0b2e 471f b605 f060bb9b2858 avatar
Founder Partner and CTO at Rogue Startup
I would like to see better documentation on how to set up complex webs of RabbitMQ servers — master/slave, multi-master, etc. view full review »
Anonymous avatar x60
Graduate Teaching Assistant at a university with 1,001-5,000 employees
The solution can be improved in terms of how to handle the rolled off data from the queue. Currently, if the consumer does not consume a queue, the data in the queue will eventually overflow and be discarded. view full review »
F5dd3a31 0280 415b 8209 4f88c3cae006 avatar
Software Engineer at a software R&D company with 1,001-5,000 employees
The product works pretty well, but one small thing could be an improvement to the monitoring site. It could be a little bit more modern, instead of postback refreshing, etc. view full review »
Anonymous avatar x60
Research Assistant at a university with 1,001-5,000 employees
Improve the ability to handle the large message load. People usually use RabbitMQ as the lightweight messenger, if they have a large message load people are inclined to use Kafka. But at the beginning stage of most projects, the data is small, people do not need to use a Kafka type of messenger, they are more likely to use RabbitMQ. If RabbitMQ can handle the large message load and support ordered delivery, with the project growing, data bigger, people can still use RabbitMQ and wouldn't need to find another tool to use like Kafka which is much more convenient. view full review »
8551ee2e c611 49bf a52b 04b14d2d0f1d avatar
Principal Software Engineer at a tech company with 501-1,000 employees
RabbitMQ needs 2 additional features: * It is lacking a good dashboard on the web interface; maybe they can develop a dashboard for monitoring. * There is no alert mechanism. For example, sometimes consumers may be killed or the input messages in queues are greater than the consumed messages. Thus, I would like them to define a rule for alert; maybe they can develop an alert mechanism. view full review »

Sign Up with Email