Nov 2023 · Architecture
Cloud Modernization: Where to Start
Modernization isn't just migration. If you lift and shift legacy architecture directly into the cloud without touching the operating model, you simply move your problems to someone else's data center—and pay a premium to do it.
Start With a Fact-Based Baseline, Not a Migration Plan
Before moving anything, you need an exact read on the current state. This means mapping the infrastructure inventory, applications, deep dependencies, and the current cost and risk profiles. Too often, migration plans are built on assumptions about what's running, leading to stalled waves when unmapped dependencies break in transit.
Prioritize by Business Value, Not Technical Age
It's tempting to migrate the oldest systems first, but age isn't the best proxy for business value. Prioritize workloads that constrain agility, block new revenue streams, or carry unacceptable operational risk. A slightly older system that runs quietly might be better left alone until the systems that actively hurt the business are addressed.
Treat Different Workloads Differently
The "6 Rs" of migration matter here. Not everything needs to be refactored into microservices.
Don't Default to Microservices
Microservices solve organizational scaling problems at the cost of massive operational complexity. If you don't have the engineering maturity to handle distributed tracing, eventual consistency, and complex CI/CD, refactoring a monolith into distributed services will slow you down. Start with modular monoliths unless scale explicitly demands otherwise.
Move in Waves, Not One Big Program
Big bang migrations fail. Build a secure, compliant cloud landing zone first. Move a low-risk pilot workload to prove the tooling and operating model. Then, migrate in controlled waves, iterating the run-state processes as you go. Delivery should feel like a predictable factory, not a singular heroic effort.