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

Limitations of Cloud IAM

So far, we've discussed the various features of Cloud, IAM as well as how it works, but before we wrap up Cloud IAM, let's take a look at what you cannot do with Cloud IAM.

Like any other cloud service, policies have limitations. For starters, each Google Cloud resource can only have one policy attached to it. It does not matter at what level in the hierarchy it is; the organization can have the number of policies as a Cloud Storage bucket, which is 1. You can, however, have different versions of a policy, but only one will be active at a time.

A single policy can only have up to 1,500 members (out of which 250 can be Google groups). This might seem like a major limitation at first but from a practical standpoint, 1,500 members per resource is more than most projects require. Furthermore, if you want more than 1,500 individual users, you can simply add them to a Google group because users in a Google group are counted as one member (the Google...