Amazon Kinesis vs. IBM Event Streams

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Amazon Kinesis
Score 8.0 out of 10
N/A
Amazon Kinesis is a streaming analytics suite for data intake from video or other disparate sources and applying analytics for machine learning (ML) and business intelligence.
$0.01
per GB data ingested / consumed
IBM Event Streams
Score 8.5 out of 10
N/A
IBM Event Streams is a high-throughput, fault-tolerant, event streaming solution. Powered by Apache Kafka, it provides access to enterprise data through event streams, enabling businesses to unlock insights from historical data, and identify and take action on situations in real time and at scale.N/A
Pricing
Amazon KinesisIBM Event Streams
Editions & Modules
Amazon Kinesis Video Streams
$0.00850
per GB data ingested / consumed
Amazon Kinesis Data Streams
$0.04
per hour per stream
Amazon Kinesis Data Analytics
$0.11
per hour
Amazon Kinesis Data Firehose
tiered pricing starting at $0.029
per month first 500 TB ingested
No answers on this topic
Offerings
Pricing Offerings
Amazon KinesisIBM Event Streams
Free Trial
NoYes
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeOptional
Additional Details——
More Pricing Information
Features
Amazon KinesisIBM Event Streams
Streaming Analytics
Comparison of Streaming Analytics features of Product A and Product B
Amazon Kinesis
8.3
2 Ratings
3% above category average
IBM Event Streams
-
Ratings
Real-Time Data Analysis10.01 Ratings00 Ratings
Data Ingestion from Multiple Data Sources9.02 Ratings00 Ratings
Low Latency9.02 Ratings00 Ratings
Integrated Development Tools9.02 Ratings00 Ratings
Data wrangling and preparation10.01 Ratings00 Ratings
Linear Scale-Out6.12 Ratings00 Ratings
Data Enrichment5.01 Ratings00 Ratings
Best Alternatives
Amazon KinesisIBM Event Streams
Small Businesses
IBM Streams
IBM Streams
Score 9.0 out of 10

No answers on this topic

Medium-sized Companies
Confluent
Confluent
Score 7.4 out of 10
Apache Kafka
Apache Kafka
Score 8.4 out of 10
Enterprises
Spotfire Streaming
Spotfire Streaming
Score 8.0 out of 10
Apache Kafka
Apache Kafka
Score 8.4 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Amazon KinesisIBM Event Streams
Likelihood to Recommend
9.0
(3 ratings)
7.9
(15 ratings)
Usability
-
(0 ratings)
8.2
(1 ratings)
Support Rating
7.1
(2 ratings)
9.1
(1 ratings)
Ease of integration
-
(0 ratings)
7.8
(10 ratings)
User Testimonials
Amazon KinesisIBM Event Streams
Likelihood to Recommend
Amazon AWS
Amazon Kinesis is a great replacement for Kafka and it works better whenever the components of the solution are AWS based. Best if extended fan-out is not required, but still price-performance ratio is very good for simplifying maintenance.
I would go with a different option if the systems to be connected are legacy, for instance in the case of traditional messaging clients.
Read full review
IBM
We used it in two cases, and it went pretty good with both. We used it for analytics and logging alongside event-based communication between different tech-stacks. One thing that users need to keep in mind is that it has a limited knowledgebase and will need a good understanding of Kafka to use it efficiently. So choose it carefully and when its needed
Read full review
Pros
Amazon AWS
  • Processing huge loads of data
  • Integrating well with IoT Platform on Amazon
  • Integration with overall AWS Ecosystem
  • Scalability
Read full review
IBM
  • It is adaptive and helps us create more engaging experiences on our platforms.
  • The Key metrics dashboard is rich with insights.
Read full review
Cons
Amazon AWS
  • Not a queue system, so little visibility into "backlog" if there is any
  • Confusing terminology to make sure events aren't missed
  • Sometimes didn't seem to trigger Lambda functions, or dropped events when a lot came in
Read full review
IBM
  • Provide Capabilities to connect the Event Streams via REST Proxy.
  • Schema Registry to handle Avro Formats.
  • Provide Kafka Connect Sink & Source Connectors.
Read full review
Usability
Amazon AWS
No answers on this topic
IBM
The product was very user friendly and extremely easy to get started with. The documentation is excellent and the free tier makes it very easy to get started with without having to make deep or long term financial commitments.
Read full review
Support Rating
Amazon AWS
The documentation was confusing and lacked examples. The streams suddenly stopped working with no explanation and there was no information in the logs. All these were more difficult when dealing with enhanced fan-out. In fact, we were about to abort the usage of Kinesis due to a misunderstanding with enhanced fan-out.
Read full review
IBM
I met with the support team and they have deep technical and development understanding of the needs and the problems which IBM Event Streams addresses. If you are looking for a product backed by a highly technical support team then IBM Event Streams is probably the best choice. I was specifically impressed by the level of technical understanding my support team demonstrated.
Read full review
Alternatives Considered
Amazon AWS
The main benefit was around set up - incredibly easy to just start using Kinesis. Kinesis is a real-time data processing platform, while Kafka is more of a message queue system. If you only need a message queue from a limited source, Kafka may do the job. More complex use cases, with low latency, higher volume of data, real time decisions and integration with multiple sources and destination at a decent price, Kinesis is better.
Read full review
IBM
In Event Streams, applications send data by creating a message and sending it to a topic. To receive messages, applications subscribe to a topic. High availability and reliability. Event Streams offers a highly available and reliable Apache Kafka service running on IBM Cloud. Event Streams. Event Streams stores three replicas of your data to ensure the highest level of resilience across three availability zones.
Read full review
Return on Investment
Amazon AWS
  • Caused us to need to re-engineer some basic re-try logic
  • Caused us to drop some content without knowing it
  • Made monitoring much more difficult
  • We eventually switched back to SQS because Kinesis is not the same as a Queue system
Read full review
IBM
  • In using downstreams, the minimal features and the rate of releases were slow, makes us feel that there's no upgrades and other than that there's poor marketing of the product.
  • The adoption around the service is low, requires focused marketing.
  • Lack of visibility into topic depth , Monitoring capabilities
Read full review
ScreenShots