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

Containers

As with VMs, you would have to have been under a rock for the last 10 years to not know what a container is. However, if you are coming from a legacy environment, you might have heard about them but not really worked with them. Let’s do a very quick refresh.

Essentially, containers let application developers break free from the prison of VMs. What do I mean when I say this? Consider that in the old days, you had to deploy your application or applications on a VM. That was it. You might have been forced to deploy multiple applications on one VM or maybe just one. With that, what happened when you needed to update the OS? Did that update affect all applications the same way? This is just one scenario of what happened when the VM model started breaking down and thus came in the age of containers. Containers solve the aforementioned problem and others as well. Too many to go into. The bottom line is that for modern applications, containers are here to stay for a while...