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

Best practices for modernizing the monolith

The transition from a monolithic design to one that is built on microservices can be a difficult process that calls for careful preparation and execution. The following are some examples of excellent practices to think about:

  • Know your monolith: Before implementing any sort of modification, you should make the effort to completely comprehend your existing monolith. Determine the various components, the dependencies between them, and how they interact with one another. This will assist you in determining which components of the system can be broken out into independent services (microservices).
  • Know your microservices’ capability: Determine the limits of your microservices based on the business capabilities of your application. To do this, you must first identify the business capabilities of your application. These should be logical collections of related functionalities that can be deployed, scaled, and maintained separately...