Cloud

Most cloud cost problems are visibility problems. Fix tagging, kill idle resources, right-size what remains, and make cost a regular engineering conversation.

Practical Terraform patterns for teams that have outgrown the tutorial stage: module design, state management, environment promotion, and policy enforcement.

Cloud cost management is not a discipline. It is basic engineering hygiene dressed up with a consulting-friendly name.

December 7 reminded everyone that us-east-1 is a single point of failure for half the internet. Again. I am annoyed.

Two years ago I wrote about Terraform patterns for growing teams. Here's what held up, what broke, and what I do differently now.

Most Kubernetes clusters are 40-60% over-provisioned. Here's how I help teams cut their bills without sacrificing reliability.

Multi-cloud sounds great in vendor pitches. In practice, it doubles your operational burden for benefits most teams will never need.

I write Go for a living. Rust is not replacing it. But I have to be honest about where Rust wins.

Serverless is great until it isn't. A comparison of serverless and containers at different traffic scales, with actual numbers on where the economics flip.

Everyone's scrambling to scale cloud infrastructure overnight. I've seen what happens when security gets deprioritized under pressure — at NATO exercises, at Decloud, at the fintech startup. Here's how to not become a headline.

Cloud cost management isn't a finance problem. It's an architecture problem disguised as a spreadsheet. Here's how to treat your AWS bill like the engineering signal it actually is.

Lessons from splitting a 4000-resource Terraform state into something teams can actually work with -- state layout, module boundaries, and the workflow discipline nobody wants to do until they have to.

Multi-region architecture is a strategic decision most teams make too early. Here's when it actually pays off, the patterns that work, and why data is the part that will ruin your week.

A direct comparison of cloud cost optimization strategies -- what actually moves the needle vs. what just makes finance feel better.

Opinionated Infrastructure as Code patterns from running Terraform at the fintech startup. Repo layout, modules, state management, and the stuff that burns you if you ignore it.

Real patterns and antipatterns from running serverless at the fintech startup. Where Lambda shines, where it hurts, and how to tell the difference before it's too late.

We serve financial data to users across Europe at the fintech startup. Here's what I've learned about going multi-region -- the patterns that work, the ones that burn you, and when you should even bother.

That clean AWS pricing page has almost nothing to do with your actual invoice. I learned this the hard way at the fintech startup.

Most serverless tutorials teach you the wrong thing. Here's what matters when you're running it for real.

Most startups have no business running their own servers. The math is not close.

We moved from console-driven, script-heavy infrastructure to Terraform so changes are reviewed, reproducible, and recoverable from code.

Lambda is a sharp tool for specific jobs. The problem is everyone wants to use it for everything.