Dave Filoni is officially an Executive Creative Director at Lucasfilm 👏

This iteration of the RedMonk Programming Language Rankings is brought to you by MongoDB. From the edge to the cloud, MongoDB enables you to work with data as code – in any language – so you can build and ship applications faster. If you are a Python, .NET, Java, or Javascript developer, get started now

Spring Boot. Contribute to spring-projects/spring-boot development by creating an account on GitHub.

Технофрик | Разрабатываю Flipper Zero http://flipperzero.one | управляю московским Хакспейсом Нейрон @neuronspace

Sometimes, less is more.
One case where that’s certainly true is dependencies.
And so it shouldn’t come at a surprise that the Apache Kafka community is eagerly awaiting the removal of the dependency to the ZooKeeper service,
which currently is used for storing Kafka metadata (e.g. about topics and partitions) as well as for the purposes of leader election in the cluster.


The Kafka improvement proposal KIP-500
("Replace ZooKeeper with a Self-Managed Metadata Quorum")
promises to make life better for users in many regards:




Better getting started and operational experience by requiring to run only one system, Kafka, instead of two


Removing potential for discrepancies of metadata state between ZooKeeper and the Kafka controller


Simplifying configuration, for instance when it comes to security


Better scalability, e.g. in terms of number of partitions; faster execution of operations like topic creation

Sometimes, less is more.
One case where that’s certainly true is dependencies.
And so it shouldn’t come at a surprise that the Apache Kafka community is eagerly awaiting the removal of the dependency to the ZooKeeper service,
which currently is used for storing Kafka metadata (e.g. about topics and partitions) as well as for the purposes of leader election in the cluster.


The Kafka improvement proposal KIP-500
("Replace ZooKeeper with a Self-Managed Metadata Quorum")
promises to make life better for users in many regards:




Better getting started and operational experience by requiring to run only one system, Kafka, instead of two


Removing potential for discrepancies of metadata state between ZooKeeper and the Kafka controller


Simplifying configuration, for instance when it comes to security


Better scalability, e.g. in terms of number of partitions; faster execution of operations like topic creation