Try our new research platform with insights from 80,000+ expert users

Amazon SQS vs IBM Event Streams comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 27, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon SQS
Ranking in Message Queue (MQ) Software
4th
Average Rating
8.6
Reviews Sentiment
7.4
Number of Reviews
30
Ranking in other categories
No ranking in other categories
IBM Event Streams
Ranking in Message Queue (MQ) Software
10th
Average Rating
8.4
Reviews Sentiment
7.8
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2025, in the Message Queue (MQ) Software category, the mindshare of Amazon SQS is 8.0%, down from 11.1% compared to the previous year. The mindshare of IBM Event Streams is 1.0%, up from 0.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software
 

Featured Reviews

Hari Prakash Pokala - PeerSpot reviewer
Valuable AWS services enhance data analysis yet could benefit from flexible data streams
I am using multiple services such as AWS Lambda, S3, EC2, ECS, and the SNS SQS services, along with QuickSight reports and some of the VPC concepts.  We have an email notification system integrated with Spring Branch. Once a batch job completes, SNS and SQS trigger events, sending notification…
Ismail El-Dahshan - PeerSpot reviewer
Easy to set up with good support and good routing scenarios
The triggering and the events that they have triggered as well as the route of the message according to the events are very useful. The triggering scenarios and routing scenarios are all good. It's a very useful solution for financial institutions. The initial setup is pretty straightforward. The stability has been good. I've found the product to be scalable. Technical support is responsive.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It is stable and scalable."
"The scale it manages is quite impressive."
"The libraries that connect and manage the queues are rich in features."
"It works consistently and is economical under a standard non-FIFO model."
"SQS is very stable, and it has lots of features."
"One of the useful features is the ability to schedule a call after a certain number of messages accumulate in the container. For example, if there are ten messages in the container, you can perform a specific action."
"The dead-letter queue is very helpful in maintaining the messages that come into the queue."
"I like how we can subscribe to multiple topics in Amazon SQS. It's also much simpler and quicker to set up than other solutions. It also supports patterns like Kafka and RapidMQ's fan-out pattern but with easier implementation."
"I'm an administrator, and what I like most is the interface, the security, and the storage."
"The system efficiently processes and calculates the data flow within the cluster using DLP functionality."
"The stability has been good."
 

Cons

"The tool needs improvement in user-friendliness and discoverability."
"Support could be improved."
"Sending or receiving messages takes some time, and it could be quicker."
"There are some issues with SQS's transaction queue regarding knowing if something has been received."
"It would be easier to have a dashboard that allows us to see everything and manage everything since we have so many queues."
"Amazon SQS is costly. I think there could be improvements in how it facilitates comparisons between different AWS products. A calculator would be helpful. The calculator for Kafka is based on factors like throughput or storage used in the last month. In contrast, the calculator for Amazon SQS is based on the number of transactions processed. These different approaches make it challenging to compare them directly. I suggest AWS provide a straightforward calculator where I can input one aspect, and it calculates costs for multiple solutions."
"Improvement is needed in terms of troubleshooting and logs."
"There is room for improvement in handling large-scale data."
"The product's interface needs improvement."
"In the next release, I would like to see the GUI allow you to configure the security section."
"It would be helpful if they could help us explain why they, as in, the customers, should use the product and the overall benefits."
 

Pricing and Cost Advice

"The pricing of Amazon SQS is reasonable. The first million requests are free every month, and after, it's cost 40 cents for every million requests. There are not any additional fees."
"Compared to the other options and based on what I have heard, Amazon SQS is relatively more expensive, but it is not insanely expensive."
"Amazon SQS is moderately priced."
"SQS's pricing is very good - I would rate it nine out of ten."
"The pricing model is pay-as-you-use. It depends on your usage and configuration."
"I rate the tool's pricing a nine out of ten."
"Amazon SQS is more affordable compared to other solutions."
"Amazon SQS offers a generous free tier, beyond which it remains very cost-effective. The cost per million messages is less than a dollar, making it an economical choice."
"The platform is averagely priced."
"The pricing needs to be improved."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
858,469 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
20%
Financial Services Firm
16%
Manufacturing Company
10%
Comms Service Provider
8%
Financial Services Firm
26%
Computer Software Company
13%
Retailer
10%
Real Estate/Law Firm
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What needs improvement with Amazon SQS?
The retention period for messages could be improved. Currently, messages are retained for four or seven days. It would be beneficial if there was a provision to configure and retain messages for lo...
What is your primary use case for Amazon SQS?
I primarily use Amazon SQS ( /products/amazon-sqs-reviews ) for asynchronous messaging. It is part of our distributed system design, where we use it for asynchronous communication by posting a mess...
What do you like most about IBM Event Streams?
The system efficiently processes and calculates the data flow within the cluster using DLP functionality.
What is your experience regarding pricing and costs for IBM Event Streams?
The platform is averagely priced. I rate the pricing a six out of ten.
What needs improvement with IBM Event Streams?
The product's interface needs improvement. Additionally, there could be a management console to create and manage clusters.
 

Overview

 

Sample Customers

EMS, NASA, BMW, Capital One
American Airlines, UBank, Bitly, Eurobits, Active International, Bison, Contextor, Constance Hotels, Resorts & Golf, Creval, Deloitte, ExxonMobil, FaceMe, FacePhi, Fitzsoft, Fuga Technologies, Guardio, Honeywell, Japanese airline, Jenzabar, KONE
Find out what your peers are saying about Amazon SQS vs. IBM Event Streams and other solutions. Updated: June 2025.
858,469 professionals have used our research since 2012.