Kafka easy
Kafka consumers employ a 'Pull' (polling) model rather than a 'Push' model. What is a primary technical benefit of this approach?
- A It allows the broker to push data faster than the network can handle.
- B Flow Control: It prevents consumers from being overwhelmed by a burst of data, as the consumer decides when and how much data to request from the broker.
- C It eliminates the need for any network connection between the consumer and broker.
- D It ensures that only the Master node can read the data.
Answer: B. Flow Control: It prevents consumers from being overwhelmed by a burst of data, as the consumer decides when and how much data to request from the broker.
In a 'Push' system, a slow consumer might crash when the server sends too much data. In Kafka's 'Pull' system, if a consumer falls behind, its lag increases, but it continues processing at its maximum possible speed until it catches up.
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?