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

When to use Cloud Run

It is the view of the author that Google Cloud Run should be the default deployment environment when containers are under discussion. The question then becomes, when should we not use Google Cloud Run to host our containers?

The following list includes some of the reasons when we would not use Google Cloud Run to host our containers:

  • We need stateful containers.
  • We need to use ConfigMaps or Secrets.
  • We need to have complex ingress routing.
  • We need the services to be hosted on a VPC (it is possible to use a VPC connector to access private IP addresses, but Google Cloud Run is not hosted in our VPC).
  • We always need to have at least one instance of our container active (it is not currently possible to set the minimum number of instances to anything other than zero).

There are exceptions to the preceding list, specifically around ConfigMaps and Secrets, and the VPC. If we are using Google Cloud Run for Anthos instead of fully managed...