Amazon Athena vs. Amazon Kinesis

If you are looking to take a lot of the traditional "database administration" work off someone's plate, going with Amazon Athena certainly has "no code" options to optimize lots of database tasks. I would say this option is less appropriate if you have other Microsoft things at play, such as Power BI.

Incentivized

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

• Nested Schemas like JSON data structure
• Ability to adapt the data model to fit your queries better
• Performance Improvement

Incentivized

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

Incentivized

• Response caching can be improved.
• Data Partitioning is tricky and understanding of the same could be improved.

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

Easy to use. Scalable. Gets the job of data warehousing setup done. Using the datalake on S3 has become super convenient.

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

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

• The query speeds help us make more decisions in a day (speed).
• If you need more horsepower for specific times in the day this option helps scale.
• The security of your environment is well protected too.

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