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

Concepts of IAM

The following are some of the basic concepts involved in an IAM system.

Entity

This is the simplest concept to understand – an entity can be a user, an administrator, or even a system. On its own, it's just a cog in a system with no authority or access (assuming that you are following the Principle of Least Privilege and have given no access by default).

For an entity to be able to access the network/application, it must be given an identity.

Identity

This is where people get confused – an identity is separate from an entity. An identity is a group of entities that all have the same privileges. Recall the concepts of messages and topics from the previous chapter; this is comparable to that. Just as messages are categorized into topics based on similar characteristics, entities are given identities.

Permissions

Permissions (such as read and write) are a part of the identity rather than a standalone concept in IAM. This means...