IBM MQ and Amazon SQS compete in the enterprise messaging category, with IBM MQ excelling in handling complex, high-volume integrations across diverse environments and Amazon SQS shining in simplicity and integration with AWS services. IBM MQ appears superior for enterprise-grade messaging with robust features for scalability and data integrity, whereas Amazon SQS stands out for cost-effectiveness and ease of use.
Features: IBM MQ is known for transferring large volumes of data reliably, with features including queue managers, asynchronous messaging, and a comprehensive command-line interface, supporting diverse environments without message loss. Amazon SQS is integrated deeply with AWS, offering FIFO and dead-letter queues, along with robust event-driven invocation, making it cost-effective for scalable messaging within AWS.
Room for Improvement: IBM MQ may need better integration with newer technologies like Kafka, enhanced monitoring, high availability, and a more user-friendly GUI, with pricing posing a challenge. Amazon SQS could improve message size limitations, expand protocol support, and manage costs better, enhancing its integration to compete with platforms like Kafka.
Ease of Deployment and Customer Service: IBM MQ offers flexible deployment across on-premises, hybrid, and private clouds, though support quality can vary. Amazon SQS benefits from AWS infrastructure's quick deployment and scaling, being recognized for ease of use but with concerns about cost management as usage scales.
Pricing and ROI: IBM MQ is considered expensive, with licensing as a barrier for smaller companies, yet its long-term enterprise value is noted. Amazon SQS utilizes a competitive, pay-as-you-use model, appealing to cost-conscious users but requiring careful cost management as usage grows, both being reliable solutions with different cost strategies.
Using Amazon SQS has led to increased productivity and reduced man-hour costs.
It's a product which integrates the external systems with internal systems or among the systems themselves, making it an essential technology component required to integrate multiple systems.
They meet their tasks effectively.
We cannot hold on to the project for a long time just to wait for IBM to fix the issues.
The response time for IBM MQ support could be better because when we are using IBM MQ and something goes wrong, support is required as the resource availability of the IBM product is very limited.
With containerized flavors of these products, we are having a tough time dealing with PMRs because the versions are new to IBM.
Amazon SQS is highly scalable, automatically managing itself based on the load.
I can easily scale up or down with Amazon SQS without any issues.
IBM MQ handles many thousands of messages in a second, indicating good scalability.
In our environment, we do not have horizontal scaling for IBM MQ, but as demand increases, we would just vertically scale it.
We've got 12 VMs running, and it's very easy to scale.
With Amazon SQS, such maintenance is not needed, making it more reliable and secure.
The stability of Amazon SQS is very good, as I find it to be very stable.
We have never had any downtime or crashes since it's been running.
The transaction is always guaranteed with IBM MQ, which is the main reason I have been working with it for fifteen years while dealing with financial transactions or messages.
Otherwise, they're completely stable.
It would be beneficial if there was a provision to configure and retain messages for longer than a week.
Having a graphical user interface would improve usability.
The pricing model for IBM MQ could be more flexible for clients.
They don't meet our standards due to the timing to get a person with knowledge.
On a scale of one to ten, where one is very cheap, I would rate the pricing as one.
It's not cheap.
It's possible to get some training, but the cost of this learning is expensive.
The price of IBM MQ is definitely on the higher side.
If there's a failure in the system after consuming a message, SQS's settings ensure the message is not deleted until confirmation.
If we compare with other solutions such as RabbitMQ for messaging, Amazon SQS is easier to use and easier to create the queue.
These are financial transactions, so we do not want to lose the message at any cost.
There is a saying that for the last 30 years IBM MQ has never been hacked.
It's time-tested, very stable, highly resilient, and has all the features to troubleshoot even if something goes wrong.
| Product | Mindshare (%) |
|---|---|
| IBM MQ | 21.0% |
| Amazon SQS | 6.5% |
| Other | 72.5% |
| Company Size | Count |
|---|---|
| Small Business | 13 |
| Midsize Enterprise | 4 |
| Large Enterprise | 14 |
| Company Size | Count |
|---|---|
| Small Business | 20 |
| Midsize Enterprise | 18 |
| Large Enterprise | 147 |
Amazon SQS provides scalable, reliable communication for asynchronous messaging. Supporting both standard and FIFO queues, it efficiently handles millions of messages while connecting with AWS services like Lambda and EC2.
Amazon SQS is designed for robust asynchronous messaging, facilitating event-driven architectures across applications. Its features ensure reliable microservice communication, managing retries and dead-letter queues to maintain stability. Ease of integration with services like API Gateway, Lambda, and EC2 allows users to seamlessly process large message volumes. Message durability and precise FIFO execution ensure accurate delivery. Despite its capabilities, there's room for enhancement in telemetry, cost estimation, and integration breadth. Improvements like better message handling, increased retention, and faster processing could enhance Amazon SQS's performance.
What features make Amazon SQS reliable?In industries like e-commerce, finance, and tech, Amazon SQS is vital for enabling scalable messaging and processing large volumes of transactions. Companies utilize it to build efficient event-driven architectures, ensuring their systems operate smoothly and accommodate growth demands. Its integration with AWS tools supports varied application needs, enhancing operational efficiency.
IBM MQ provides reliable message delivery, supporting integration across systems with features like security and data integrity. It's widely used in financial and healthcare sectors, offering high scalability and availability while maintaining message consistency during downtime.
IBM MQ is known for its reliable and guaranteed message delivery, high scalability, and seamless integration with diverse systems. Users find its data integrity and robust security particularly beneficial, making it ideal for critical environments. It efficiently handles large message volumes, ensuring no data loss even during outages. Ease of use and initial setup, along with stability, are frequently noted advantages. However, users express a desire for better interfaces and enhanced cloud integration. Administration and security features are sometimes considered complex, necessitating streamlined processes and modern graphical interfaces. Expanded monitoring, competitive pricing, improved connectivity with platforms like Kafka and RabbitMQ, and seamless integration opportunities are commonly suggested areas for improvement.
What Are the Key Features of IBM MQ?IBM MQ is extensively implemented in critical industries such as finance and airlines, where reliable data exchange is essential. It supports message delivery in diverse platforms, facilitating crucial business transactions and scalable web services. Organizations in these sectors leverage its stability, high performance, and integration with both distributed and mainframe environments for consistent and reliable communication, helping to reduce the risk of data loss.
We monitor all Message Queue (MQ) Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
