
Premium
Title Page
11/3/2025
Copyright Page
11/3/2025
Dedication Page
11/3/2025
About the Author
11/3/2025
About the Reviewers
11/3/2025
Acknowledgement
11/3/2025
Preface
11/3/2025
Table of Contents
11/3/2025
Section 1: Cloud Services by Responsibility
11/3/2025
1. Responsibilities and Utility of a Cloud Platform
11/3/2025
Introduction
11/3/2025
Structure
11/3/2025
Objectives
11/3/2025
General infrastructure considerations
11/3/2025
Identity and authentication
11/3/2025
Scalability
11/3/2025
Asynchronous processing
11/3/2025
Data permanence
11/3/2025
Response delivery
11/3/2025
Analysis of infrastructure considerations
11/3/2025
Interdependence of platform responsibilities
11/3/2025
Assigning roles by platform
11/3/2025
Google Cloud Platform product overview
11/3/2025
Top level categories of Google Cloud services
11/3/2025
Computing power
11/3/2025
Databases
11/3/2025
Storage
11/3/2025
Networking
11/3/2025
Data analytics
11/3/2025
Security and identity
11/3/2025
Developer tools
11/3/2025
Artificial intelligence and machine learning
11/3/2025
Components outside of cloud services
11/3/2025
Conclusion
11/3/2025
2. Dividing up Features of a Cloud Backed Application
11/3/2025
Enumerating responsibilities and dependencies
11/3/2025
Different, valid points of view
11/3/2025
Grouping by topological locality
11/3/2025
Grouping by feature affinity
11/3/2025
Determining feature affinity and proximity
11/3/2025
Grouping by feature performance considerations
11/3/2025
Understanding feature requirements
11/3/2025
Defining application feature composition
11/3/2025
Pertinent qualities of an infrastructure service or component
11/3/2025
Describing infrastructure options
11/3/2025
3. Determining the Infrastructure to Build Features Upon
11/3/2025
Request funneling to scale to O(N)!
11/3/2025
Urgency versus importance
11/3/2025
Eventual consistency in distributed systems
11/3/2025
A case study in eventual consistency
11/3/2025
Guaranteeing user-visible responsiveness
11/3/2025
Horizontal scaling via Pub/Sub
11/3/2025
Transaction guarantees
11/3/2025
Beyond the base transaction model
11/3/2025
Security, privacy and permanence
11/3/2025
Cybersecurity
11/3/2025
Security in Google Cloud Platform
11/3/2025
Data privacy
11/3/2025
4. Choosing Between GCP Options
11/3/2025
Choosing a server-side runtime platform
11/3/2025
The impact of compute platform selection
11/3/2025
Google Application Engine
11/3/2025
Google Cloud Run
11/3/2025
Compute Engine
11/3/2025
Virtual machines
11/3/2025
Compute product comparison
11/3/2025
GCP Compute resource management
11/3/2025
Compute resources offered
11/3/2025
Determining where best to store your data
11/3/2025
Cloud Firestore
11/3/2025
Cloud Structured Query Language
11/3/2025
Bigtable
11/3/2025
Bigtable performance
11/3/2025
Spanner
11/3/2025
Cloud Storage
11/3/2025
Firebase Authentication
11/3/2025
Firebase authentication features
11/3/2025
Google Cloud IAM
11/3/2025
Roles versus users
11/3/2025
Identity Platform
11/3/2025
Identify Platform authentication features
11/3/2025
Asynchronous message handling
11/3/2025
Pub/Sub
11/3/2025
Scalability of a messaging architecture
11/3/2025
Cloud Tasks
11/3/2025
Section 2: Cloud Backed Application Architecture
11/3/2025
5. Client-side Technology Choices
11/3/2025
Native mobile applications
11/3/2025
Android development tools
11/3/2025
iOS development tools
11/3/2025
Cross-platform mobile frameworks
11/3/2025
Flutter
11/3/2025
React Native
11/3/2025
Kotlin Multiplatform
11/3/2025
Web applications
11/3/2025
Desktop client applications
11/3/2025
Native desktop development
11/3/2025
Cross-platform desktop development
11/3/2025
In-browser client applications
11/3/2025
Web application programming languages
11/3/2025
Angular
11/3/2025
React and ReactDOM
11/3/2025
Web application development tools
11/3/2025
GCP support for web application clients
11/3/2025
Chatbots and voice agents
11/3/2025
Chatbots and GCP
11/3/2025
Chatbot voice frontends
11/3/2025
6. Cloud Services at the Backend Border
11/3/2025
Maintaining backend agnostic clients
11/3/2025
General API design principles
11/3/2025
Special considerations for client or cloud interfaces
11/3/2025
Visibility levels to the client
11/3/2025
Planning migration to substitute or equivalent cloud services
11/3/2025
Vendor lock-in
11/3/2025
Product obsolescence
11/3/2025
Designing for migration
11/3/2025
Visibility between cloud services
11/3/2025
Dependencies between cloud service products
11/3/2025
Isolating cloud service products
11/3/2025
Identifying and packaging tightly coupled services
11/3/2025
7. Frontends at the Client Border
11/3/2025
Client-side logic
11/3/2025
Avoid multiple sources of truth
11/3/2025
Presentation of the user interface
11/3/2025
Capturing user input, selection and entry
11/3/2025
Hiding sensitive logic from observation
11/3/2025
Making frequently changed code easy to deploy
11/3/2025
Defining client requests to the backend
11/3/2025
Backends for frontends
11/3/2025
Blocking and non-blocking request responses
11/3/2025
Identifying asynchronous methods
11/3/2025
Client technologies for asynchronous processing
11/3/2025
Pushback and handling unexpected responses
11/3/2025
Defining and handling non-user-initiated actions
11/3/2025
Use cases for server-initiated actions
11/3/2025
Mechanisms for receiving server-generated traffic
11/3/2025
Section 3: End-to-End: A Global Voting System
11/3/2025
8. Making a Voting System Available and Reliable
11/3/2025
Digital voting system overview
11/3/2025
Overview of an online talent competition
11/3/2025
Voting process
11/3/2025
Scalability requirements
11/3/2025
Voting system performance requirements
11/3/2025
Usage models
11/3/2025
Google Cloud Platform regional boundaries
11/3/2025
Voting system demand by continent
11/3/2025
Data aggregation
11/3/2025
Aggregating distributed votes in a global system
11/3/2025
Accessibility
11/3/2025
Strategically relocating resources
11/3/2025
Optimizing the application to fit available resources
11/3/2025
Redesigning the application
11/3/2025
Creating the package and directory structure codelab
11/3/2025
Platform components and initial files
11/3/2025
Voting API
11/3/2025
9. Identifying the Stress Points of our Voting System
11/3/2025
Types of failures
11/3/2025
Scope of a failure
11/3/2025
Progression
11/3/2025
Causes of a failure
11/3/2025
Failure categorization
11/3/2025
Assessing impact
11/3/2025
Determining short-term cost of an outage
11/3/2025
The long-term cost of an outage
11/3/2025
Monitoring, detection and notification
11/3/2025
Observing first and then controlling
11/3/2025
Monitoring terminology
11/3/2025
Types of metrics
11/3/2025
Key reliability metrics
11/3/2025
Monitoring distributed systems
11/3/2025
Monitoring GCP applications
11/3/2025
Performance watchpoints in the voting application
11/3/2025
Incident response
11/3/2025
Matrix of failure modes and appropriate measures
11/3/2025
Implementation of the Vote Ingester API codelab
11/3/2025
Project considerations in setting up the repository
11/3/2025
Web client and common code
11/3/2025
Cloud-based code
11/3/2025
Google Cloud project configuration
11/3/2025
Firebase project configuration
11/3/2025
GCP Monitoring
11/3/2025
10. Securing All User Votes
11/3/2025
Demand modeling
11/3/2025
Independent cycles of demand
11/3/2025
Load balancing
11/3/2025
Types of load balancers
11/3/2025
Load balancing algorithms and considerations
11/3/2025
Load balancing in Google Cloud Platform
11/3/2025
Selecting voting system load balancers
11/3/2025
Employing message queues to pool requests
11/3/2025
Creating Pub/Sub resources for votes
11/3/2025
Publishing votes to Pub/Sub
11/3/2025
Asynchronous processing of requests
11/3/2025
Processing votes published to Pub/Sub
11/3/2025
Scaling backend processing
11/3/2025
Applying GCP scaling
11/3/2025
Vote Processor deployment
11/3/2025
Monitoring of backend performance
11/3/2025
Dispatching user requests asynchronously via Pub/Sub codelab
11/3/2025
Asynchronous vote processing components
11/3/2025