Likelihood to Recommend 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 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 Processing huge loads of data Integrating well with IoT Platform on Amazon Integration with overall AWS Ecosystem Scalability Read full review 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 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 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 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 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 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 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 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 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 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