Kafka easy
Historically, which external service was required by Kafka to manage cluster hierarchy, metadata, and leader election status?
- A PostgreSQL for persistent metadata storage.
- B Memcached for high-speed coordinate caching.
- C Apache ZooKeeper, which acted as the source of truth for the cluster's state.
- D The Google Search API for discoverability.
Answer: C. Apache ZooKeeper, which acted as the source of truth for the cluster's state.
ZooKeeper managed the 'Controller' election and tracked which brokers were alive. Newer versions of Kafka are replacing ZooKeeper with 'KRaft' (Kafka Raft), which integrates metadata management directly into the Kafka brokers.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- When implementing 'Exactly-Once Semantics' (EOS) in a Kafka stream, what is the role of the `isolation.level=read_committed` setting on the Consumer?
- Once a message is successfully appended to a Kafka partition log, what is its mutability status?
- In a Kafka cluster, what is the role of a 'Broker'?
- What is the primary indicator of a bottleneck in a Kafka consumer's processing logic?
- What is the primary architectural role of Apache Kafka in a distributed system?
- When a Producer sends a message with a specific 'Key', how does Kafka interpret this for shard distribution?