5 Years in Cloud Native: The Good, the Bad, and the Bill

What happens when your data center literally catches fire? Five years ago, a literal disaster was the catalyst for our total migration to Cloud Native. But moving from on-prem microservices to a fully scalable cloud architecture was a journey filled with scars, paranoia, and expensive lessons. In this session, I will share my perspective as a CTO who led a team through a deep cultural transformation: the metamorphosis from traditional system administration to a DevOps mindset, where Infrastructure as Code (IaC) became our most valuable asset. We will dive into “scalability paranoia”—how we optimized container orchestration to beat the competition without losing our sanity (or the entire budget). We will break down the financial reality of elasticity: while on-prem environments force you to distribute workloads over time to avoid saturating fixed hardware, Cloud Native demands a complete mental reboot. I’ll share how we shifted from ‘squeezing every cycle’ out of static servers to an event-driven model designed to scale to zero. We’ll discuss the danger of misconfigured scaling—the ‘blank check’ risk—and how we learned to orchestrate resources so they only exist when there is actual work to do, finally aligning our infrastructure costs with real business value. This isn’t a polished success story; it’s an honest breakdown of complex solutions to simple problems, and how this journey finally allowed us to sleep at night.