How to analyze the cost of Kafka?
The article discusses the common cost inefficiencies associated with using Kafka. It highlights five key patterns that lead to overspending, including partition overprovisioning and unnecessary cluster sprawl. Recommendations for optimizing costs include setting sensible defaults and regularly reviewing Kafka environments.
- ▪Most Kafka teams are overpaying by 25 to 40 percent due to inefficient usage patterns.
- ▪Common issues include partition overprovisioning, long retention periods for unused topics, and the existence of zombie topics.
- ▪Optimizing costs can involve setting lower defaults for partitions and retention, as well as consolidating Kafka clusters.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1137771) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Stéphane Derosiaux for Conduktor Posted on May 25 How to analyze the cost of Kafka? #kafka #datastreaming #devops #architecture Which side are you on: "This is just what Kafka costs at scale" or "We should switch to a cheaper Kafka provider"? At Conduktor, our field team works inside Kafka environments that have been running for a long time. We see this: most Kafka teams are overpaying by 25 to 40 percent.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
