http://www.linkedin.com/in/ekassner, https://twitter.com/ekassner

Eduardo Kassner author block

What if you could help your enterprise clients achieve both efficiency and innovation across their entire portfolio? What if you could help them take advantage of the cloud with all of its resources and features to get a “greater than the sum of its parts” effect? With a good road map and proven strategies to lead the way, you can.

We have done extensive research into what it means to move an enterprise environment with its application catalogue to the cloud. In the e-book “Enterprise Cloud Strategy”, we provide examples and learning experiences from Microsoft’s own journey, as well as from those of our customers. This eBook will help you migrate your customers’ IT environments to the cloud and provide insight into building your own cloud Infrastructure as a Service (IaaS).

Cloud Migration Considerations

There are different migration approaches that you and your client must consider. Below we delve into various options including their benefits and complexities:

•  Re-host. Move a Virtual Machine (VM) or an operating environment from the on-premises datacenter to a hoster or a cloud. This model is also known as co-location.

•  Re-platform. A legacy environment becomes unsustainable based on cost or operational requirements; a solution is to “retain and wrap” the application without making changes to the code, possibly compromising the integrity and security of the operation.

•  Retire and Rewrite (or Re-envision). When there are sufficient new requirements that cannot be met by the older environment, the best way to proceed is to rewrite the application in a newer, better-suited environment. Often this occurs when examining the portfolio of applications and consolidating several that have a similar function.

•  Burst out. With all of the new compute, data and service models that are being provided in cloud environments, each providing capabilities and capacities that were never before accessible to an IT environment, many applications are bursting out to the cloud. These applications are doing innovative types of analytics, reporting, high-performance computing, visualization, and so on. Keeping frequently used (“hot”) data locally while aging-out infrequently accessed (“cold”) data to far cheaper cloud storage is another common pattern.

•  Expand. Enterprises are now exploring how to expand their older applications and how to add functionality to provide to mobile devices and Web front ends with the same capabilities that previously were limited to a computer screen. They are even moving to enhance the applications with search or video services, as an example.

•  Cloud-Native Applications. As companies begin their investigation of the cloud, they frequently realize that there are new forms of applications like Big Data, new types of analytics, entirely new capabilities such as machine learning, and applications for the Internet of Things (IoT) that are uniquely fitted to live in the cloud.

Cloud Migration: What to expect

The ideal cloud migration plan will be more of a process than a static document, you’ll find that each migration generally follows this pattern:

1. Analysis

This is the process of mapping the current state to the desired state. This process will help you to identify the gaps between what your client currently has and what it will take to migrate that workload to the cloud. Those gaps might involve changes to the architecture of the workload or might require a complete rewrite of the program.

2. Application Migration

When you determine that a particular workload should be moved to the cloud, a best practice is to create a version of the workload with a minimal amount of data to get the application working on the cloud or to build a new version of the application there. If the application is already running on a VM, it might be possible to simply migrate the VM to the cloud without further changes.

In general, many on-premises applications can run on Microsoft Azure with minimal or no changes, but this does not mean that the application will be optimized for performance, scalability, and security. You might need to redesign and rebuild the application, to some degree, by using modern service-oriented principles.

3. Data Migration

This is somewhat similar to the application migration in that the data structure can be moved as-is to either a relational (Azure SQL Database, SQL Server in Azure VM) or non-relational (blob, table, queue, Azure DocumentDB, and so on) location on the cloud. Several of these kinds of migrations are extremely easy, and you can conduct them with the help of a wizard such as the SQL Server Azure Migration Wizard.

However, you might want to consider rebuilding the data model as a new Azure SQL Database to gain performance, scalability, resiliency, and security improvements. If you need to synchronize data between on-premises and SQL Database or between different SQL Database servers, set up and configure the SQL Data Sync service. In addition, it is a best practice to set up and configure a data recovery plan in case of user errors or natural disasters.

4. Optimization and Testing

After you migrate your client’s application and data to Azure, perform functional and performance tests. At this phase, test the application in the cloud and confirm that it works as expected. Then, compare performance results between on-premises and Azure. After that, resolve any feature, functionality, performance, or scalability issues in the cloud application.

5. Operation and Management

After the testing and optimization phase, set up and implement application monitoring and tracing with the Azure Application Insights, which enables you to collect and analyze telemetry from the application. This data can be used for debugging and troubleshooting, measuring performance, monitoring resource usage, traffic analysis and capacity planning, and auditing.

Download the e-book now for actionable guidance that will help you migrate your enterprise customers’ application portfolios to the cloud.

11-2_CTA1 11-2_CTA2 11-2_CTA3