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

Staged modernization strategy – taking a multi-step approach

While you may ultimately want modernization, you may find that there are goals you need to meet prior to the time needed to make that type of transaction. For example, you might need to get out of your current data center in one year, and your most optimistic estimate for modernizing your application to cloud-native will take a minimum of two years to complete.

In addition, you may find that some of the applications you need to modernize will get less benefit from a complete transformation to Azure-native than others. In this case, you may choose to rehost or refactor some applications first and concentrate on other applications that benefit most from a complete transformation to Azure-native.

In either case, as described previously, you could benefit from a multi-step approach for modernization to Azure. Taking a multi-step approach can also allow your modernization staff to stay focused on fewer applications...