Kafka easy
To enable horizontal scaling and high concurrency, a Kafka Topic is horizontally split into smaller, independent segments called what?
- A Shards, similar to NoSQL databases like MongoDB.
- B Partitions, which are the fundamental unit of parallelism and throughput in Kafka.
- C Buckets, used for temporary data hashing only.
- D Frames, which are fixed-length binary windows.
Answer: B. Partitions, which are the fundamental unit of parallelism and throughput in Kafka.
Partitions allow a topic to be distributed across multiple brokers. If a topic has 12 partitions and 3 brokers, each broker hosts 4 partitions. This architecture allows multiple producers and consumers to interact with the same topic simultaneously without contention.
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?
- Historically, which external service was required by Kafka to manage cluster hierarchy, metadata, and leader election status?
- 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?