“Lift and Shift” doesn’t mean “No Re-Factoring Required.”

If you have legacy applications and are moving to the cloud, one popular pattern is to do a simple “Lift and Shift.” That means you don’t architecturally change the application but simply move it to your cloud of choice and run it just like you did before. This approach lets you more quickly “get out of the data center” and doesn’t initially imply that you have to refactor any part of the application to use native services provided by your cloud vendor.

In fact, if the application is stable but just legacy, your valid strategy might be to let it run forever in an “as-is” state. Nothing changes. Just get it running in the cloud and out of the data center.

This approach’s major downside is that Lift-and-Shift also carries forward all the Technical Debt accumulated for that application.

Continue reading

Application Archiving in the Cloud

Introducing “Cold Storage” of complete application systems in the Cloud.

Traditional application archiving is often described in one of two ways:

1) Archiving – this is where you have an application that has accumulated large amounts of historical data that exists on Tier 1 primary storage within the data center. The basic concept is that you take some of the older, infrequently accessed data and “archive” it or move it to some other read-only data warehouse that utilizes less expensive storage. The idea is to save money by reducing the pressure to expand more expensive storage and potentially reduce those costs over time. The application system remains “active” but with only newer relevant data.

Continue reading