5 Strategies, Gartner teaches you how to migrate cloud

For companies that are struggling to migrate applications to cloud environments, because they are faced with not only one solution, but five different scenarios in front of them, for redeployment to the infrastructure as a service (IaaS), on the platform as a service (PaaS) refactoring, Modify for IaaS or PAAs, re-establish on PAAs, and replace Software as a service (SaaS). In the face of these five options, the choice is a very difficult thing.

The Gartner Architect was also confused at first, when Richard Watson, director of research at Gartner, said in a statement: "CIO issued After migrating some applications to the cloud environment ' This simple command, choose which option is good and how to proceed with this work; they have to consider the problem, and before they make a decision, they must also consider the needs of the enterprise, evaluation standards and architectural principles. Choosing is a difficult thing to do because there is no foolproof plan. All scenarios require an architect to understand the migration of an application from multiple perspectives and standards such as IT staff skills, existing investment value, and application architecture. ”

Gartner suggests that the five migration strategies that the IT department should consider are as follows:

Redeployment-This means redeploying the application to a different hardware environment and changing the infrastructure configuration of the application. Redeploying an application without changing the schema can provide a solution that migrates quickly to the cloud environment.

However, without benefits like extensibility, the main advantage of IaaS is that the team can migrate the system quickly without changing the architecture, which may be the main drawback.

Refactoring--in other words, running applications on the cloud provider's infrastructure. The main advantage is to integrate the familiar environment with backward-compatible technology innovation. PAAs means that developers can reuse the language, framework, and previously painstakingly developed containers so that they can take full advantage of the enterprise's strategic code.

Disadvantages include lack of functionality, risk of conversion, and possible locking of the framework. In this early stage of the PAAs marketplace, the PAAs solution may be missing some of the functionality that developers on the existing platform rely on.

Modify--Modify or extend an existing code base to support the need to modernize legacy systems, and then deploy to a cloud environment using redeployment or refactoring scenarios. This approach allows organizations to optimize their applications to take full advantage of the cloud characteristics of the provider's infrastructure.

The downside is that starting a development project requires upfront costs to mobilize the development team. Modification is a scheme that may spend most of its time on delivery functions, depending on the size of the scope of the modification.

Re-build--re-establish the solution on the PAAs, discard the code for the existing application, and reset the structure for the application. While re-building needs to discard existing code and frameworks that are already familiar, the advantage of a new application is that it can enjoy the innovative capabilities of the provider's platform. PAAs providers can improve the productivity of developers by allowing tools for application templates and data customization models, meta data-driven engines, and communities that provide prefabricated components.

However, being locked by the provider is the main disadvantage; so if the provider makes a change in price or technology, the consumer is overwhelmed, the provider violates the service level agreement (SLA), or if the customer is forced to switch to a different provider--it is possible to discard some or all of the application assets.

Substitution means discarding an existing application (or a set of applications) and using commercial software that is delivered as a service. When demand for business functions changes rapidly, this scenario avoids upfront costs to mobilize the development team.
Disadvantages may include inconsistent data semantics, data access issues, and potential vendor lock-in.

Watson continued: "The choice of the best application migration scenario cannot be made in isolation." Any decision to migrate to a cloud environment is actually a decision to modernize an application or infrastructure that needs to be put into a broader context, taking into account related application portfolio management and infrastructure portfolio management plans. ”

"This decision is not entirely a migration issue, it is actually an optimization problem: which cloud platforms and migration methods provide the opportunity to maximize the application's help and contribution to established and implied business and it objectives?" Those business and it goals are expected to prompt companies to move to a cloud-rather than to try new technologies and tools. ”

Original name: 5 Ways to Migrate applications to Cloud Author: CIO Update Staff

"This article is 51CTO selected translations, reproduced please indicate the source!" 】

"Edit Recommendation"

Amazon Google Microsoft three trial cloud services (on) cloud migration: How to leverage existing IT resources? Amazon EC2 interrupted "usable area" is challenged! Revelation of the biggest downtime in the Amazon the migration should be prudent! Security issues and considerations for cloud applications The seven lessons learned from the Amazon cloud service failures cloud computing and clustering: Is it a hand or a fight? Protect cloud ≠ protect cloud data cloud storage data in five major unsafe factors Sony Ultra 100 million user data leaked users or reconsider whether to migrate

"Responsible editor: Wang Yong TEL: (010) 68476606"