Moving your applications to the cloud
Like so many things in it, there is an instruction manual or recipe book for migrating applications to the cloud. And in fact, each company chooses the type of migration based on a number of factors, from the time of existence of an application even if its development took place to form internal or external.
When you migrate an application to the public cloud, most it organizations choose the procedure “lifting and shifting”, or re-architect any application. And while both approaches have their advantages, organizations should choose carefully when it comes to the development of a strategy for the migration to the cloud.
The lift-and-shift migration takes an application on-premises and the replica to the cloud, i.e. migrates an application or applications from the existing environment for a new cloud-based environment, without changing the logical or the way the application works.
Already the process of re-architecting the application involves making changes in the way an application performs before moving it to the cloud. These changes may include the review of source code, rewrite APIs and interfaces of apps and data binding. Other changes, such as the design of an app to scale dynamically resources using native APIs or make calls to database objects, are specifically intended to maximize the value of the cloud. You fragment the application until its functional components, redesigning it specifically for a platform in the cloud. The model lift-and-shift can vary drastically from the re-architecture of applications regarding initial and long-term costs. While the lift-and-shift can be accomplished in less than a week, the process of re-architecture can take months, or even longer, depending on the application and if the service is hosted in-house or by a third party.
The lift-and-costs shift can start, for example, with 20,000 R$ by application, but that number could grow significantly based on the type of application and the number of external dependencies. However, if a company is migrating a large number of applications at once, the 20,000 R$ can be reduced by half, that is, the cost decreases dramatically.
Where the process of lift-and-shift leaves something to be desired
When a legacy application is migrated to an IaaS platform with little or no modification, you can’t get the most out of one of the greatest benefits of the cloud: cost-efficiency through autoscaling. In the cloud, computing resources scale automatically up or down based on demand application, but most legacy applications are not designed specifically to capitalize on this feature of the native cloud. Then, when those applications are moved to the cloud, they consume more computing and storage resources than they need, which can lead to an increase in unwanted costs.
The idea is to win with the cloud value and reducing costs, matching the peak loads with the amount of infrastructure use. The problem with the lift-and-shift is that on-premises applications are built to adhere to high peak loads, and when these applications are moving to the cloud, they continue to operate that way – even if demand or use is weak.
So sometimes if your application is not at the peak, which can be up to 80% of the day, you’re paying too much.
Because of this inefficiency, move applications lift-and-shift can, in some cases, cost to an organization more than re-architect, and can also be more expensive than leaving the application in existing local infrastructures.
Imagine having your house lights lit during 24 hours a day? Is sure to be much more costly than turn them off only at night and, with lift-and-shift, everything is connected, all the time, no matter what.
On the other hand, there are also companies who choose to architect the application from scratch by the autoscaling.
So, it appears that a lot depends on what your business wants to go to the cloud and why she made this decision, either through reduced costs, increased availability and speed, autoscaling, among others, for then she knows how to go to the cloud and which best ways to adopt.