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

Configuring public access to the application

We will now look at how we can expose our services to the outside world and make them available on public endpoints. The services we have created thus far are of the NodePort type, which means they are exposed on the IP address of the Node they are running on, using a port generated by the Service. The IP address of each Node is a private IP address on our VPC. To expose our services securely to the outside world, we need to have three things in place. First, we need a public static IP address so that we can map our hostname in our DNS to that address. Next, we need an SSL certificate so that we can use HTTPS. Finally, we need a method that will let us route traffic from the public IP address/hostname to our services. This method is called Ingress.

We create the public static IP address called banking-ip as we did when setting up the Google HTTP(s) load balancer for our virtual machine infrastructure. Please ensure that the A (address...