Building out a managed Kubernetes service is a bigger job than you think (Ep.443)
Infrastructure as code is complicated enough, but building a managed IAC service is a whole other level of complicated.


Infrastructure as code is complicated enough, but building a managed IAC service is a whole other level of complicated.
Big enterprise clients looking for "lift and shift" are lucrative clients in the cloud market. But there are also millions of independent developers who need cloud tech at their scale.
Managing Kubernetes clusters the way you manage bug fixes.
We explore Stack Overflow's journey into the world of Kubernetes and containers with one of our software engineers, Max Horstmann.
If you’re building a new app today, it might be worth taking a closer look at making it cloud-native and using Kubernetes from the jump. The effort to set up Kubernetes is less than you think. Certainly, it’s less than the effort it would take to refactor your app later on to support containerization.
This is a story about trying to rethink complex systems: the challenges you face when you try to rebuild them, the burdens you face as they grow, and how inaction itself can cause it’s own problems. When you’re weighing the risk and reward of replacing architecture, it can take several attempts to find a solution that works for you.
IaC allows developers to supply IT environments with multiple lines of code and can be deployed in a matter of minutes (in contrast to manual infrastructure, which can take hours if not days to be deployed).
All the cool kids are licensed to operate a cloud.
Before you can wield the power of the lightboard and explain cloud technologies, you must slay a lot of first level slimes.