How Kubernetes And Kafka Will Get You Fired
<p>I get to see a lot of companies, their infrastructure and their systems architecture through my consulting activities. Over the past 10 years both Kubernetes and Apache Kafka have become extremely common and popular in many businesses. And very often not for the good.</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:700/1*xSFbT0esxt0lD-N5snbh6A.png" style="height:394px; width:700px" /></p>
<p>Kubernetes and Kafka: Dream team or horror show?</p>
<h1>How it all starts most of the time</h1>
<p>The CEO of a medium-sized software company, whom I knew for some years, called me up one day asking for advice. His SaaS offering was running okay and had seen solid commercial success over the last decades. They had successfully transitioned from a desktop software product for Windows to a sophisticated web-based SaaS product with a modern event-driven microservices architecture. He himself wrote the original product in the mid 90s and as the decades passed by somewhat lost track of the technical development. Nevertheless, the product looked good and as he explained it, it seemed to be a very well architected and professional product. <em>To be honest, I was a bit lost on why he called me up.</em></p>
<p><a href="https://medium.com/@jankammerath/how-kubernetes-and-kafka-will-get-you-fired-a6dccbd36c77"><strong>Read More</strong></a></p>