In the year 2011 Gartner described 6 alternatives to move applications to the cloud. This is known as the 6 R. Based on that initiative, this time let's see 3 different strategies we can use to migrate applications to the cloud.
Photo credits: ukayacan
Institutions need to develop a plan that defines how to approach the migration of each of the applications and in what order they will do it. This plan may be subject to change as migration progresses. and it will depend a lot on how your systems are.
The complexity of migrating applications to the cloud varies depending on the architecture and existing license agreements.. A virtualized service-oriented architecture would be at the low-complexity end of the spectrum, whereas a monolithic mainframe would be at the high complexity end of the spectrum.
Strategies for migrating applications to the cloud
The organization's capabilities, the time available to complete the project and the expectations generated by the plan to move applications to the cloud will determine the strategy to be applied. There are many different ways to achieve it:
- Replataforma: it's about relocating, as an example, an electronic commerce, moving it to a different platform. This action can seek optimization in the cloud or the achievement of some tangible benefit, even though its main characteristic is that it is carried out without changing the central architecture of the application at all. When deciding on this way to migrate applications to the cloud, you should pay attention if you prefer to use a platform fully managed by the provider, as would be the case with Amazon Elastic Beanstalk, o si, Conversely, it is more convenient opt for a database-as-a-service platform. This alternative is recommended when legacy systems begin to fail or if the company discovers that new functionality is needed..
- Rehosting: It is the movement towards a new development carried out by many projects focused on the migration of applications to the cloud, using native cloud capabilities., but in a legacy migration scenario. The objective is scale migration quickly to fulfill a business case. The great utility of this option is the cost savings it implies and the fact that applications are generally easier to take full advantage of and redesign once they are already running in the cloud..
- Repurchase: this strategy is about leveraging preconfigured and cloud-ready solutions.. For many, is the fastest way to easily enter any cloud environment, even the most complex. Through the use of these preconfigured implementations, a lot of the migration work for these apps has already been done. Selecting this shortcut is inexpensive, easy and very profitable. In practice, repurchase (also known as buyback, would consist, as an example, in going from a CRM to Salesforce or from a CMS to Drupal).
They are not the only ones strategies for the transfer of cloud applications. Gartner also proposes others such as refactoring, withhold or withdraw. Which do you think would guarantee a better result in your business? Do you know how to select the option that best suits you?
