How Kubernetes and Kafka Will Get You Fired
Not that I want to advocate for Kubernetes, but this is just a stepping stone for another blog post in a few years &quot;How managed services in AWS got us fired!&quot; detailing how when AWS changed their pricing&#x2F;strategies the companies had no way out of their design choices.<p>The &quot;vendor agnostic&quot; approach was the right call to make at that point in time. Sure, every business is unique and some cases fit better for a hands-off (lets pay for the convenience of AWS taking care of managed offerings) approach. But, it is a fallacy to think there is no cost to pay for that decision.<p>The cost of operating your vendor agnostic infrastructure is replaced by your team now needing to learn the intricacies of AWS such as IAM, AWS&#x27;s way of networking, backups etc. Those operational needs dont just go away, they just become &quot;easier&quot; and more defined as AWS&#x27;s way of doing it.<p>As a consultant, one must know where to draw the line and recommend the appropriate route.