Why Serverless Is Just Lock-In with Better Branding

12/01/2026 8 min
Why Serverless Is Just Lock-In with Better Branding

Listen "Why Serverless Is Just Lock-In with Better Branding"

Episode Synopsis

Serverless is marketed as "no servers, no ops, just code"—but that convenience hides a deeper tradeoff: long-term freedom. In this video, I break down how platforms like AWS Lambda, Google Cloud Functions, and Firebase quietly lock you into a single provider, not through the language you write in. Still, through the glue you adopt: event formats, IAM models, triggers, logging, deployment pipelines, and tightly coupled managed services.   We'll look at where lock-in really lives architecturally, why leaning hard into proprietary auth, queues, databases, and logging can turn your system into a beautiful cage, and how to avoid that without giving up the speed that makes serverless attractive in the first place. You'll learn practical patterns like hexagonal/onion architecture, keeping business logic pure and side-effect-free, pushing cloud-specifics to the edges, and wrapping provider APIs behind your own interfaces for storage, messaging, and identity. I'll also cover strategies for keeping your data portable and planning for the day you might need to change clouds—or run on bare metal.   Serverless isn't the enemy. Blind trust is. Use the cloud's superpowers, but design as if you'll have to leave.