Chapter 88. The Importance of Keeping Working Systems Working
Jan Urbański
There’s a classic phrase in the car enthusiast world: “While I’m there.” Let’s say you want to change your engine. You go through a lot of effort to disconnect all the externals and extract it from the chassis, and when faced with an empty engine bay, you suddenly say, “While I’m there, why not upgrade the radiator as well? And the turbocharger?” You end up with a project that takes twice as long, costs three times as much, and is leaking fluid from that ill-fitting radiator that looked so great in the catalog.
A cloud migration project is a cross-cutting undertaking, often involving touching lots of components that have previously been running smoothly for years. Everything is different in the cloud, even if vendors try their best to provide an illusion of seamlessness. Migrating means challenging all the assumptions your software makes about resource availability, network latencies, and performance characteristics of the underlying hardware. It’s already a tough problem, and any extra changes you introduce to the system carry additional risk of derailing the entire effort.
The code you’re migrating might be cumbersome to work with. It might be too tightly coupled, and it might be hard to configure. But it has one important characteristic: it’s working. It is providing ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access