Book Image

Architecting Google Cloud Solutions

By : Victor Dantas
Book Image

Architecting Google Cloud Solutions

By: Victor Dantas

Overview of this book

Google has been one of the top players in the public cloud domain thanks to its agility and performance capabilities. This book will help you design, develop, and manage robust, secure, and dynamic solutions to successfully meet your business needs. You'll learn how to plan and design network, compute, storage, and big data systems that incorporate security and compliance from the ground up. The chapters will cover simple to complex use cases for devising solutions to business problems, before focusing on how to leverage Google Cloud's Platform-as-a-Service (PaaS) and Software-as-a-Service (SaaS) capabilities for designing modern no-operations platforms. Throughout this book, you'll discover how to design for scalability, resiliency, and high availability. Later, you'll find out how to use Google Cloud to design modern applications using microservices architecture, automation, and Infrastructure-as-Code (IaC) practices. The concluding chapters then demonstrate how to apply machine learning and artificial intelligence (AI) to derive insights from your data. Finally, you will discover best practices for operating and monitoring your cloud solutions, as well as performing troubleshooting and quality assurance. By the end of this Google Cloud book, you'll be able to design robust enterprise-grade solutions using Google Cloud Platform.
Table of Contents (17 chapters)
1
Section 1: Introduction to Google Cloud
4
Section 2: Designing Great Solutions in Google Cloud
10
Section 3: Designing for the Modern Enterprise

Designing for observability with best practices

In this section, we will discuss some common observability architectures, how to build a cost-effective monitoring solution, and how to define an alerting and incident management strategy.

Choosing the right observability architecture

As mentioned previously, a Workspace can monitor up to 100 projects. It doesn't mean that you should always have a single Workspace for all your projects if you have less than 100 of them. Let's look into some of the common observability architectures and their pros and cons. However, before we get into these design patterns, it's useful to understand the three IAM roles related to monitoring:

  • Monitoring Viewer: Gives the user read-only access to the Cloud Monitoring console and APIs
  • Monitoring Editor: Gives the user read and write access to the Cloud Monitoring console and APIs, including writing monitoring data to a Workspace.
  • Monitoring Admin: Gives the user full access...