...

Currently, client produce/consume quota configurations are stored in the Zookeeper. Brokers monitor the changes of quota configurations from Zookeeper, and then enforce them in the process of each produce/consume request. Any changes to the client quota configurations have to talk to Zookeeper directly, which introduces more overhead for users. Given that we have released the KafkaAdminClient, which is capable of managing the configurations of brokers and topics for customers, it's desire to also support the configuration of quota rules. In this case, applications can leverage the unified KafkaAdminClient to manage their quota configurations, instead of the direct dependency on Zookeeper.

Public Interfaces

We need to define these two entities (User and Client) in the client packages as follows:

...