How a small team moved from single-region risk to a simple active/passive multi-region setup without doubling complexity.
Multi-region can easily become a science project. This is what worked for a five-person platform team supporting a SaaS product.
We began with everything in one AWS region: RDS, EKS, S3, and a shared VPC.
Instead of cloning the entire stack, we:
```hcl module "vpc" { source = "./modules/vpc" region = var.region primary = var.is_primary } ```
/healthz endpoint.We didn’t solve every theoretical edge case, but we can now lose a region and recover in under an hour with a plan the team has actually rehearsed.
Get the latest tutorials, guides, and insights on AI, DevOps, Cloud, and Infrastructure delivered directly to your inbox.
Prompt injection, data leakage, jailbreaks, and the boring controls that actually keep production AI features safe. The threat model that matters once you ship.
We started routing 90% of LLM traffic through a small internal gateway. The gateway wasn't planned — it emerged from solving the same problem in 5 places. Here's the shape it took.
Explore more articles in this category
There are two hard problems in computer science." We've worked on the cache-invalidation one for a while. The patterns that hold up at scale and the ones that look clean and aren't.
We use Step Functions for batch processing, document ingestion, and a few agentic workflows. The patterns that work, the limits we hit, and where we'd reach for something else.
After two years of running Karpenter on production EKS clusters, the NodePool patterns that survived, the ones we replaced, and the tuning that matters.