Broker communication in Apache Kafka® 2.7 and beyond

Apache Kafka is moving away from its dependency on ZooKeeper due to scalability and duplication issues. This change will impact the way brokers communicate with each other and with Kafka as a whole. In the post-ZooKeeper world, Apache Kafka would independently take care of its configuration management through a Raft quorum formed by controller nodes. The new architecture will also enhance the creation and deletion of topics. For Aiven for Kafka users, the main difference in a ZooKeeper-free Kafka will be improved performance. The latest release takes some further steps in that direction, impacting the way brokers communicate.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.