Amazon Kinesis vs. Sybase Event Stream Processor (discontinued)

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.

Incentivized

These complex event processing platforms have the ability to process to multiple streams of data with low latency and ability to scale up well. It provides the ability to analyze streaming data real time and establish/investigate patterns with this streaming data and also deals with high-speed data very well.

Incentivized

• Processing huge loads of data
• Integrating well with IoT Platform on Amazon
• Integration with overall AWS Ecosystem
• Scalability

Incentivized

• Ability to capture data and investigate data for pattern fairly quickly
• Integrates well with Sybase database
• Ability to do data modeling

Incentivized

• 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

Incentivized

• Configuring data streams could be made more intuitive to users
• Sometimes debugger tools are very slow

Incentivized

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.

Incentivized

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.

Incentivized

IBM WebSphere business elements which was more complex to set up and also more expensive especially in a large SAP environment, We were also looking to get ramped up with the product with minimal learning curve especially with good documentation available to get started with the product as well as the ability to deploy and maintain with relative ease on an ongoing basis.

Incentivized

• 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

Incentivized

• A positive impact on real-time analysis and patterns from streaming data
• Good speed
• Good documentation for setup
• No negative impact

Incentivized