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)
Part 1: Legacy Estate Options
Chapter 2: Strategies for Modernizing IBM and Unisys Mainframes
Part 2: Architecture Options
Part 3: Azure Deployment and Future Considerations

Deploying and maintaining systems on Azure

There are a number of ways to deploy and maintain applications in Azure. The most important part to take away from the section is that everything can be deployed in Azure via scripting. This scripting can be in the form of the following:

  • ARM
  • JSON templates
  • Using a script extension for PowerShell
  • CLI/Bash scripting
  • Azure landing zone accelerators for mainframe workloads

You can also use Terraform and Bicep for the creation and deployment of Azure resources.

Another way, and probably the easiest, is to use the Azure portal, but keep in mind not every deployment feature is implemented through the portal. The portal is configurable and customizable. One of the features that I like about the portal is that when you are using it to deploy Azure resources, once you have the configuration that you want, you can transform that into a JSON template for future use.

Here is a screenshot of how you would deploy an application...