This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
I spent some time and looked through the chapters (in Contents section and those available in abridged form).
I noticed you start from Kafka event stream processing and then proceed with Amazon Kinesis event stream processing.
Question: is Kinesis better platform than Kafka?
I guess the probable answer is - Kinesis is one of the AWS services and thus can easily
use the rich functionality of AWS as a whole, smooth, with no or minor integration efforts, such as:
- Amazon Redshift (used in Ch 10, Analytics-on-read)
- AWS Lambda and Dynamo DB for building Lambda functions (Ch 11, Analytics-on-write)
Just trying to better understand a place / role for Kafka.
Yury Nebieridze wrote:Question: is Kinesis better platform than Kafka?
The quick answer is: neither one is better, each has its pros and cons. For instance, one of the biggest difference is that Kafka provides eternal retention, while Kinesis (only) at most one week.
Kinesis is better connected to all the other AWS services, even though it is now possible to easily spin up a Kafka cluster in AWS using AWS Managed Streaming for Kafka instead of having to install a vanilla Kafka on EC2 all by yourself.