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

A deeper dive into microservices

First, a word about containers: before we can take a deeper dive into microservices, we need to have a good understanding of the building blocks that make up microservices, which are containers. Essentially, containers are lightweight, standalone packages of executable code. The container includes everything necessary to run the application code within it: things such as configurations, code libraries, and other code dependencies. The container is void of an operating system, and as such, it is lightweight and allows developers to consistently package and deploy applications in a repeatable way. This makes it very easy to deploy these container-based applications to different environments, such as production or development.

Containers differ from virtual machines (VMs) in that, as mentioned earlier, they do not have to worry about the care and feeding of an operating system. They are housed in a host operating system that handles those duties. Typically...