Reducing Kafka's Footprint Means Choosing the Right Trade-offs
A common discussion As a Customer Success Technical Architect, I am often asked how to manage Kafka resources. The question usually comes up when a cluster is growing, a platform team is reviewing capacity, or an architecture needs to become more efficient: How can we reduce Kafka’s footprint without weakening the guarantees our applications need? Kafka can look deceptively light at the beginning. Create a topic, send a few records, and the cluster seems to have plenty of room. The picture changes as the platform grows. More topics bring more partitions. More replicas bring more copies of the data. More consumers can bring more fetch traffic and consumer-group coordination. ...