3 ms·
> ... systems that rely on external dependencies like Apache Zookeeper and BookKeeper. I would argue that building up on existing systems (especially things li
by q3k 6y ago
> ... systems that rely on external dependencies like Apache Zookeeper and BookKeeper.
I would argue that building up on existing systems (especially things like a distributed consensus system like Zookeeper) is generally good practice. Being able to just point a bunch of self-contained JARs/WARs at a Zookeeper/etcd cluster and not worry about startup sequencing or cluster bootstrapping makes me happy.
- imglorp 6y agoHasn't Kafka been talking about eliminating external zk forever? Are they making it an internal library or adopting a new consensus scheme?
- miguno 6y agoYes, you remember correctly. The Kafka community has already started the work on getting rid of ZooKeeper. See https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A... for details.
- FridgeSeal 6y agoFrom my understanding, they’re going to use the brokers as their own metadata store, so the data that was in ZK goes in a topic instead, and I believe Raft for leadership? KIP-500 is the proposal/PR (?) for ZK-free Kafka which I understand has been merged in and work is now progressing on follow up tasks.