Book Image

Modernizing Legacy Applications to Microsoft Azure

By : Steve Read, Larry Mead
Book Image

Modernizing Legacy Applications to Microsoft Azure

By: Steve Read, Larry Mead

Overview of this book

Organizations have varying circumstances, objectives, and prerequisites when contemplating a hyper-scale cloud solution transformation to a platform such as Azure. Modernizing Legacy Applications to Microsoft Azure uncovers potential scenarios and provides choices, methodologies, techniques, and prospective possibilities for transitioning from legacy applications to the Microsoft Azure environment. You’ll start by understanding the legacy systems and the main concerns regarding migration. Then, you’ll investigate why distributed architectures are compelling and the various components of the Azure platform needed during migration. After that, you’ll explore the approaches to modernizing legacy applications and the Rs of modernizing (i.e., rehost, refactor, rearchitect, and retire). You’ll also learn about integration approaches and potential pitfalls. By the end of this book, you’ll be well equipped to modernize your legacy workloads while being aware of pitfalls and best practices.
Table of Contents (18 chapters)
1
Part 1: Legacy Estate Options
3
Chapter 2: Strategies for Modernizing IBM and Unisys Mainframes
6
Part 2: Architecture Options
10
Part 3: Azure Deployment and Future Considerations

Data center exit – how to get to Azure as quickly as possible

There could be a number of reasons why a legacy application needs to modernize to Azure as quickly as possible, including the following:

  • The customer needs to vacate the facility that houses the legacy system
  • The legacy system is the last application remaining in the data center, driving up costs
  • The contracts on the legacy hardware and software have a pending renewal that will increase costs

The key factors all of these reasons have in common are as follows:

  • Costs related to keeping the data center running are too expensive
  • The application itself currently meets business requirements

This implies that minimal code changes are required. However, the target architecture on Azure and deployment methodologies can be adapted to the needs of a particular customer.

Moving to emulators on VMs

Emulators are probably the fastest way, with the least risk, of moving applications...