Thanks for the great talk! The real issue is why use Confluent instead of Kafka? The Confluent pricing is not clear to a single developer to me. Another question: @3713: Does this mean one can have more than 1 kafka framework between each service? Like between fraud detection and reporting? Or a central Kafka system which ingests data for other services to read, process and write to?
The last few questions explore the question in more detail. For a single developer learning Kafka, the benefits might indeed be limited. However, as soon as you need to implement a real project and then deploy to production, it gets much easier: In Confluent Cloud, you get a truly serverless offering with consumption-based pricing (like any other serverless cloud service). Then, you quickly understand the benefits. The cloud pricing is also very transparent.
Thanks for the great talk! The real issue is why use Confluent instead of Kafka? The Confluent pricing is not clear to a single developer to me. Another question: @3713: Does this mean one can have more than 1 kafka framework between each service? Like between fraud detection and reporting? Or a central Kafka system which ingests data for other services to read, process and write to?
The last few questions explore the question in more detail. For a single developer learning Kafka, the benefits might indeed be limited. However, as soon as you need to implement a real project and then deploy to production, it gets much easier: In Confluent Cloud, you get a truly serverless offering with consumption-based pricing (like any other serverless cloud service). Then, you quickly understand the benefits. The cloud pricing is also very transparent.