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


ASF is a deployment option that can be very compelling, especially when your goal is to leverage cloud-native services that exploit the benefits of a modern cloud architecture such as Azure. Where technologies such as Kubernetes excel at typically stateless applications, ASF has a strong focus on stateful applications. What exactly does this mean? Stateless applications execute and do what they are supposed to do and then go away. They literally go away in the digital sense in that they have no idea of what they were doing before unless you maintain the state of what they were doing in some place such as a Redis cache. Stateful applications, on the other hand, do maintain their own state. Depending on the application you are creating, one will be better suited than the other. The other thing to keep in mind about ASF is that an ASF cluster can be deployed on-premises or on another cloud. Think about that. It offers most of the benefits of Kubernetes and can span Azure from on-premises...