Book Image

The Definitive Guide to Modernizing Applications on Google Cloud

By : Steve (Satish) Sangapu, Dheeraj Panyam, Jason Marston
Book Image

The Definitive Guide to Modernizing Applications on Google Cloud

By: Steve (Satish) Sangapu, Dheeraj Panyam, Jason Marston

Overview of this book

Legacy applications, which comprise 75–80% of all enterprise applications, often end up being stuck in data centers. Modernizing these applications to make them cloud-native enables them to scale in a cloud environment without taking months or years to start seeing the benefits. This book will help software developers and solutions architects to modernize their applications on Google Cloud and transform them into cloud-native applications. This book helps you to build on your existing knowledge of enterprise application development and takes you on a journey through the six Rs: rehosting, replatforming, rearchitecting, repurchasing, retiring, and retaining. You'll learn how to modernize a legacy enterprise application on Google Cloud and build on existing assets and skills effectively. Taking an iterative and incremental approach to modernization, the book introduces the main services in Google Cloud in an easy-to-understand way that can be applied immediately to an application. By the end of this Google Cloud book, you'll have learned how to modernize a legacy enterprise application by exploring various interim architectures and tooling to develop a cloud-native microservices-based application.
Table of Contents (26 chapters)
1
Section 1: Cloud-Native Application Development and App Modernization in Google Cloud
5
Section 2: Selecting the Right Google Cloud Services
10
Section 3: Rehosting and Replatforming the Application
17
Section 4: Refactoring the Application on Cloud-Native/PaaS and Serverless in Google Cloud

Summary

In this chapter, we refined our infrastructure architecture to address scalability and availability concerns. We updated it to make use of a regional managed instance group to control a collection of identical virtual machine instances. These instances were spread across multiple availability zones to address availability. The regional managed instance group also has autoscaling capabilities and so addresses scalability. Finally, we updated our infrastructure architecture to incorporate an HTTP(S) load balancer to distribute traffic evenly across all the instances.

We implemented this architecture by creating an image from our Tomcat virtual machine. Then, we used the image along with the virtual machine configuration to create an instance template. After that, using the instance template, we created a regional managed instance group. Finally, we created our HTTP(S) load balancer using the regional managed instance group as the backend.

In the next chapter, we will begin...