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

Applying SRE

As you've learned throughout this chapter, DevOps is a set of principles and a working culture. On the other hand, SRE is a set of technical practices where many of the underlying principles are similar to those of DevOps. An analogy to object-oriented programming is often made to describe SRE: if DevOps is a class, SRE is an object that instantiates the class. In other words, SRE is a practical implementation of an otherwise abstract set of principles. Moreover, it "extends" the class to include its own unique methodologies.

It doesn't make much sense to start a DevOps journey by hiring "DevOps engineers" and procuring tools. Even the role of a DevOps engineer shouldn't yet exist unless you have already established a basic DevOps foundation. It's easy to fall into the trap of thinking that simply hiring engineers who are well versed in the DevOps ways of working will bring DevOps to your organization. It might help you get there...