It’s time for companies to flip the script on modernization without creating prohibitive effort or accruing additional technical debt.
Why not just lift-and-shift to cloud?
A conventional wisdom has developed over the last decade–supported by analysts and cloud experts–that moving applications to cloud computing infrastructure is not only desirable, but absolutely necessary to any modernization effort.
The fastest growing unicorn companies like Netflix and Uber were born in the cloud, so why not emulate their path to success?
For an established company, the jump to cloud usually means replatforming applications–lifting VMs and databases from on-premises or conventionally hosted servers onto a pay-as-you-go model with a cloud IaaS provider.
Yes, the old lift-and-shift is alive and well in the cloud. After all, if you can’t build net-new application functionality from scratch, at least putting everything on cloud infrastructure might enable forward progress in flexibility, right?
Lifting virtual servers and J2EE binaries and extracting data onto cloud services does provide some nice capabilities such as reserving excess capacity or maintaining parallel instances of whole environments for failover or recovery purposes. But the heavyweight nature of monolith applications in the cloud also means you can rack up surprisingly high compute and storage costs, while still making new functionality hard to add.
The applications were never optimized for cloud in the first place, much less being ready for truly modern cloud-native agility for change and efficient scaling…
Read the entire BrainBlog on vFunction.com here: https://vfunction.com/flip-the-script-on-lift-and-shift-modernization-with-refactoring/?web=1&wdLOR=cD488AE58-869A-43F8-9A8D-9144EA6A33E2
https://vfunction.com/flip-the-script-on-lift-and-shift-modernization-with-refactoring/?web=1&wdLOR=cD488AE58-869A-43F8-9A8D-9144EA6A33E2
