Amazon Kinesis vs. IBM Streams (discontinued)

Perfect for real-time data processing and streaming. Also, there's no need for any specific setup - you just start using it immediately and it easily integrates with the rest of AWS capabilities (like Redshift), although integration with Lambda could be better. You can make your overall analytics landscape way simpler with Kineses even if you have non-Amazon solutions like Tableau. It all integrates really well!

Incentivized

Streams is a good fit for situations requiring low end-to-end latency, have complex real-time analytical processing needs on large fast data, or where the reduction of operational costs is important. However, it is very much a data-in-motion technology and not well suited for situations such as some forms of machine learning where the entire historical data set needs to be operated on. Note that it's fairly common to use Streams to perform online scoring using models that were trained offline using other technologies.

Incentivized

• Integrating with other Amazon services
• Scaling requests
• Totally serverless platform
• Simple management

Incentivized

• Query analysis of real time streaming data
• Filter out events based on time windows
• Scalability for large scale data, production tested

Incentivized

• Improve integration with AWS Lambda
• Some duplicate records coming from the stream

Incentivized

• Documentation could be more extensive, with more examples, although overall this is not too bad compared to some of the alternative solutions.
• Seems expensive to use in production.

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

Kinesis is oriented to streaming in a scalable way large volumes of information in real-time. Glue is more an ETL so it is not well suited for real-time applications while Beanstalk is more a simple container platform. Lambda could do the job but it would require a lot of programming to accomplish the same as Kinesis. In fact, our solution employed the four elements for different tasks but using Kinesis as the message bus.

Incentivized

We are using Spark streaming as well as Storm for streaming options. Currently streams provides a better way of building applications easier faster and run efficiently. Also like the flexibility it provides with both us and SPL.

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

• Ability to do more with less
• Admins and data analyst can now focus on more thinking tasks
• No negative impacts yet

Incentivized