5 ms·
My fear is that Kafka will increasingly require "enterprise" support tools with less and less support and features available to people who do not pay for enterp
by djhworld 10y ago
My fear is that Kafka will increasingly require "enterprise" support tools with less and less support and features available to people who do not pay for enterprise support.
I thought Kafka was an Apache project, don't they have rules against this sort of thing?
- x0x0 10y agoSure, the Apache distro of kafka won't require them. Users who buy from Confluent will download Confluent's build of kafka. Similar to how things work in the hadoop ecosystem: You can get Apache hadoop, but most users get one of Cloudera, Hortonworks, or MapR.
- ptrincr 10y agoAs it stands though, kakfa is no where near as complicated as setting up and managing a hadoop/yarn/spark(etc etc) cluster. Without using something like Hortonwork's Ambari, it's a right pain trying to get everything installed, working together and managing it. Then you have to worry about how you are going to upgrade it. Currently you can use this chef cookbook https://github.com/mthssdrbrg/kafka-cookbook https://github.com/mthssdrbrg/kafka-cookbook , along with the yahoo kafka-manager application and you can get a cluster running without much effort or complication. The cookbook has a coordination feature which allows you to use a locking mechanism ( I use consul as we use it for dns/auto registration), which allows you to roll out changes across the cluster, restarting each broker one at a time, it also allows you to upgrade in a similar fashion.