Message Queue Solutions — New User Reviews 2017

What are enterprise tech professionals discussing in their latest Message Queue reviews of 2017?

In this post, we take an insider’s look at the most recent Message Queue reviews written by our users for the following solutions:

As they discuss the solutions’ most valuable features and areas for improvement, real users from IT Central Station share their insight and expertise with the enterprise tech community.


Valuable Features

“So far, it’s helped us with our Maximo integration between the users and the database administrators. I know we kind of lagged behind on some updates, which caused us problems. We recently upgraded, which had made things a lot easier, got rid of some of the issues we had with the older versions.”

— William Berry

“It’s certainly a product that you can rely on. It delivers the stability and security within our applications that we desire as an organization.”

— Ramond Ball

For MQ, the most valuable feature is our ability to connect our distributed systems back to the mainframe, and pull our legacy data out of the mainframe and bring it down into a modern Java front end.”

— Thomas Golden

Room for Improvement

“The response time could be improved because that’s our main concern. Once our system is down, then it impacts our business since we have another partner who is dependent on us.

There is a need for more integration with cloud. That’s what we’re looking for because that’s what the company is moving towards.”

— Vikas Salvi

“One of the bottlenecks for us is owing to the industry that we’re in, we sometimes get the large payloads and the MQ queues that we can increase. But, the maximum payload size allowed is only 100 Mbps. So, I wish to see if it bumps up because sometimes we hit that ceiling and the message won’t process. We have to find another way to mitigate one or two instances like that.”

— SeniorMic699


Valuable Features

“The most valuable feature of RabbitMQ is the ability to set up workflows simply with configuration. We had some very complex problems (logging, auditing, sequential and parallel operations) that have been easily solved by inserting a queue in the middle of an existing workflow.”

— Robert Herrick

“Some valuable features of this product are”:

  • Message queuing
  • Good support
  • Provided scalability and a distributed environment
  • Easy usability with Node JS
  • Could easily withstand and pass stress/load testing with more than 10K API calls
  • Helped achieve a distributed environment and implement a 3-tier structure
  • Helped to develop a highly scalable system by decoupling front end and back end

— Jay Sardhara

Room for Improvement
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.”

— SeniorSoabf3

“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 was self-inflicted but occasionally the distributed database would end up corrupted.”

— VpOfSoftb75e

Apache Kafka

Valuable Features

“The most valuable features are topic-based eventing, scalability, and retention periods.

My organization is transforming by using the new SOA/eventing-based architecture. The application depends on the employee’s’ information events.

Kafka is very helpful in implementing this. It increases the performance and gives the details to multiple external/internal teams using Kafka topics in an asynchronous manner.”

— Technica9976

“We use the product for high-scale distributed messaging. The processing capability of the product is enormous. Being a distributed platform, multiple consumers can sync with it and fetch messages.”

— kafkakid

Room for Improvement

“Currently, as it is in the big/fast data integration world, you need to piece together many different open-source technologies.

For example, to create a reliable, fault-tolerant streaming processing system that ingests data, you need:

  • A producer service
  • An event/message buffer such as Kafka or a message queue
  • A stream processing consumer such as Spark, Flink, Storm, etc.
  • something to help facilitate the ingestion into target data sources, such as Flume or some customized concoction.
  • This is simply to ingest the data and does not necessarily account for the analytical pieces, which may consist of Spark ML, SystemML, ElasticSearch, Mahout, etc.
    What I’m getting at is basically the need for a Spring framework of big data.”

— Kevin Quon

Apache ActiveMQ

Valuable Features

“One of the most important features of ActiveMQ is the ability to set up a network of brokers, and the ability to forward the message to another broker in the network, where there is a demand for messages from a consumer.

These brokers could span over WANs and geographies. The messages will get forwarded to the broker where the demand is, which is what makes this a distributed messaging system.”

— Principab325

Most valuable to us are fast asynchronous message queuing with message-level acknowledging and message persistence.”

— Freelanc06f0

Room for Improvement

“There is a need for more protocols and maybe they should provide documentation on the internet as well…About the documentation, it is more about the ActiveMQ advanced concepts such as using the KahaDB etc. For the protocols, maybe a translator is needed for example integration of AMQP to MQTT or XMPP to CoAP.”

— Alexi Coard

Apache ActiveMQ needs some improvement playing with multi-platform message clients. It already plays really well with Java clients since it’s a JMS implementation, but it needs some improvement supporting clients written in other languages (like C#).”

— SrSysAdmin818

Read more of the newest 2017 Message Queue reviews by IT Central Station users.

Face-off in Message Queue Reviews: IBM MQ vs. RabbitMQ vs. Apache Kafka

What do enterprise tech professionals look for when choosing a Message Queue solution? In this week’s Face-off between Message Queue reviews, IT Central Station users discuss features such as software reliability, stability, robustness, usability, and high-scale distributed messaging. Their reviews also address the users’ main use-cases for their Message Queue solution of choice, as well as where they suggest room for improvement.


Valuable Features

Donna Fawcett describes IBM MQ as “the cornerstone for the billing system for cable” at her communications and media company, Rogers Communications. For Fawcett, MQ is “a very valuable piece of software” that interfaces with their (well over) 8 million customers.

“It’s very reliable and very stable” writes Toufic Abi Farraj, saying that “you can do a fast recovery in case of any failure.”

The “major benefit for MQ” says Payam Ghalili, is “messaging throughout multiple platforms”, explaining that his company (Fiserv) uses it “quite extensively to do messages between the iSeries and the mainframe.”

“Obviously, the biggest thing is that we’ll never lose a message” writes largesysfc05, sharing that “we use it for a lot of real-time information between our systems for integration.”

More so, largesysfc05 adds, under no circumstances can data be lost during the real-time integration, otherwise they “lose track of inventory, our manufacturing systems, sales orders and things like that.”

Room for Improvement

When it comes to room for improvement, Donna Fawcett points to price, as well as cloud functionality, explaining that getting more of the cloud and mobile experience(s) would “go farther in terms of the customer experience.”

Toufic Abi Farraj suggests “integration with the alert system”, explaining that this would alert his organization “of any failure of any message to be transmitted from one source to another.”

“A better user interface” argues director32c1, explaining that currently, the user interface is technician dependent, which automatically requires tech support. “It would be nice if we could provide better interfaces to see the queues, the channels and how they’re used, and the queue depths.”


Valuable Features

“The most valuable feature is its robustness” writes Todd Outten, explaining that “message queues need to be extremely reliable as they are the glue between system components.”

For GraduateTA901, not only is “its real-time capability of delivering the sensor data in different topic abstractions” very good, but it’s also “quite easy to setup in our sensor network system which involves data monitor agents across geographically distributed organizations.”

“One of our favorite features is the exchange” writes MidLevel24cf, adding that “the queuing out-of-the-box is awesome”, and that the clustering features allow their system to be highly available.

Jay Sardhara lists several valuable features for RabbitMQ, which include:

  • Message queuing
  • Good support
  • Provided scalability and a distributed environment
  • Easy usability with Node.js
  • Could easily withstand and pass stress/load testing with more than 10K API calls
  • Helped achieve a distributed environment and implement a 3-tier structure
  • Helped to develop a highly scalable system by decoupling front-end and back-end

ThomasS346 explains that when choosing a Message Queue solution, “performance and security were of the highest priority” and the main reason he chose RabbitMQ messaging frameworks.

For that reason, “authentication, performance, and durable messaging” are the most valuable features to him.

Apache Kafka

“We use the product for high-scale distributed messaging” explains kafkakid, adding that because it is a distributed platform, “the processing capability of the product is enormous” and multiple consumers can sync with it and fetch messages.

JavaDeve0c6d lists the following features as most valuable:

  • Replication: “good for high availability, provides additional safety for data in case of node failure or data center outage.”
  • Partitioning: “a really useful feature for parallelizing processing.”

JavaDeve0c6d explains further that because his media company uses Apache Spark to process data from a Kafka queue, “Spark is able to assign one executor to each Kafka partition, and the more partitions we have, the more threads we can use to process data in parallel.”
What do other users point to when comparing valuable features or areas for improvement among the various Message Queues on the market?

Read our entire collection of Message Queue reviews from the user community at IT Central Station.

New Reviews: Message Queue Software Roundup

In IT Central Station’s user community, 4,338 users follow the Message Queue category. 3,708 of these users follow Avada Software Infrared360, which ranks as the #1 Message Queue solution on our site.

In this week’s review roundup, we see how Avada Software Infrared360 compares to Apache Kafka, which ranks as the #5 Message Queue solution.

Avada Software Infrared360 and Apache Kafka earned average review ratings of 8.0 and 8.5, respectively.

Continue reading below to learn how these two solutions compare in terms of improvements to user’s organizations, scalability, stability, and overall room for improvement.

message queue stats

“What Were the Improvements to your Organization?”
Avada Software Infrared360

“One way it’s helped the business is how you’re able to empower MQ users, without your administrators, to be able to do different types of processes in the environment” writes Brad Rogers, a Middleware Admin at a Financial Services Firm.  

Rogers specifies that Avada Software Infrared360 has:

  • User group privileges that “allow you to set up security roles in the system.”
  • Permissions and actions that can be delegated to other users, so that they take on and maintain different MQ tasks.
  • Admins that can “delegate some of the work to people to do what that they’re capable of doing, without risking access to parts of the system you don’t need other people in.”
Apache Kafka

One Apache Kafka user explains that his “organization is transforming by using the new SOA/eventing-based architecture. The application depends on the employees’ information events. Kafka is very helpful in implementing this. It increases the performance and gives the details to multiple external/internal teams using Kafka topics in an asynchronous manner.”

“If any of the consumers fail to consume the message”, he continues, “then that message will be there until the retention period ends.”

“How Would You Rank the Solution’s Scalability and Stability?”
Avada Software Infrared360

In terms of scalability, writes Brad Rogers, “it’s a pretty straightforward tool…thousands of customers have it hooked up to thousands of MQ managers…it’s very easy to implement and use.”

Rogers is also confident about the stability, writing that “it has always worked. It’s a little, lightweight product and it works great. It always did what I set it up to do.”

Apache Kafka

In terms of scalability, “we have not encountered any scalability issues”, writes an Enterprise Architect at a logistics company, as does a Technical Lead at a tech services company.

The Technical Lead shares that in terms of stability, “if you are using the same group ID for multiple topics, it may shut down the application. We have faced this issue before.”

“Where Do You See Room for Improvement?”
Avada Software Infrared360

“Some of the graphics in the interface could be improved” argues Brad Rogers, describing that “some interfaces are not up to what you’re used to seeing on other, more Windows-like tools.”

Rogers suggests that the interface “just needs to keep improving to where it looks more and more like other applications. Then, when new users come in, it’s not as hard for them to learn and navigate around the environment. It’s easy to navigate once you understand how they set their GUI up. It would be something similar to how Windows or Excel follow a certain platform design and you know exactly how they work.”

Apache Kafka

“A great free monitor tool would be great for Apache Kafka” writes an Enterprise Architect at a logistics company.

Another user suggests “a more user-friendly GUI.”

“This product guarantees at-least-once delivery. We have asked JIRA to provide features such as at-most-once delivery to remove duplicate message consumption” shares a Lead Engineer.

Interested in learning more about Message Queue Solutions?

Read more user reviews for Top Message Queue Solutions, including IBM MQ, RabbitMQ and Apache ActiveMQ from the IT Central Station community.