In this post, I want to highlight a feature that I often see under-used in IBM Event Streams, and show how you can easily give it a try.
Kafka can enforce quotas to limit the impact that client applications can have on your cluster. To quote the Kafka documentation:
It is possible for producers and consumers to produce/consume very high volumes of data or generate requests at a very high rate and thus monopolize broker resources, cause network saturation and generally DOS other clients and the brokers themselves.
Having quotas protects against these issues and is all the more important in large multi-tenant clusters where a small set of badly behaved clients can degrade user experience for the well behaved ones.
In fact, when running Kafka as a service this even makes it possible to enforce API limits according to an agreed upon contract.
