Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Gauge your current knowledge
Gauge your current knowledge
High Availability (HA) keeps systems running during small failures, while Disaster Recovery (DR) handles major outages that affect entire data centers or regions. Architects measure success using two key targets: Recovery Time Objective (RTO), which is the maximum acceptable downtime, and Recovery Point Objective (RPO), which is the maximum acceptable data loss. Designing systems to meet these targets ensures a business can continue operating even when a whole region goes offline.
Google Cloud provides managed database services that handle data replication automatically. Cloud SQL uses a primary and standby instance for regional high availability, while Cloud Spanner can be configured across multiple regions to achieve 99.999% availability. These services use two main replication methods: synchronous replication writes data to multiple places at once to ensure nothing is lost, while asynchronous replication copies data shortly after the first write, which is faster but may lose a small amount of data during a failure.
Multi-region configurations protect against losing an entire geographic area. Services like Bigtable and Firestore can replicate data across different regions automatically, allowing a system to switch to a backup region without noticeable delay. For additional protection, architects use Point-in-Time Recovery (PITR), which lets you restore data from any specific minute in the past to recover from human errors or software bugs. Cloud Storage also offers Turbo Replication, which guarantees data copies to a second region within 15 minutes.
Failover procedures for stateful workloads require tools like Cross-Region Replicas or Snapshots to ensure a backup copy exists in a different location. Automating this failover process reduces manual work and minimizes the time needed to restore service after a catastrophic event.
Google Cloud organizes infrastructure into regions, which are geographic areas, and zones, which are isolated locations within those regions. A Single Point of Failure (SPOF) occurs when one component's failure stops the entire application. By distributing resources across multiple zones and regions, services can remain available even during local outages.
Zonal resources like a single Compute Engine VM exist in one location and fail if that zone goes down. Regional resources spread across several zones within a region, providing higher availability than zonal options. Examples include App Engine applications, Regional Managed Instance Groups, and Regional Cloud Storage buckets. For the highest protection, multi-regional resources spread data across different geographic regions, allowing a system to survive losing an entire region, though this often requires balancing trade-offs between latency and cost.
Managed Instance Groups (MIGs) handle automated failover and scaling. A Regional MIG automatically spreads virtual machines across different zones and recreates failed instances to maintain the desired number of active servers. This automation reduces manual work and keeps applications responsive during hardware failures.
Storage strategies must account for RPO requirements. Using dual-region or multi-region storage buckets ensures data is geo-redundant and protected against regional disasters. Architects must also consider data residency requirements, which may force data to stay within specific geographic borders for legal reasons. As more tiers are added to an application, overall reliability can decrease unless each part is properly redundant, so strategic planning and regular failover testing are essential.
Automated traffic management uses global and regional load balancers to direct users away from broken servers toward healthy ones, maintaining service during failures. This process relies on health checks, which are automated tests that verify whether an application is running correctly.
Managed Instance Groups (MIGs) manage groups of identical virtual machines with powerful automation. Auto-healing detects failed instances and automatically recreates them to maintain service. Auto-scaling adjusts the number of VMs based on current traffic, adding resources during high demand and removing them when demand drops. Regional distribution spreads VMs across zones to avoid a single point of failure.
Health monitoring is the foundation of automated failover design. When a health check detects an issue at the application or instance level, the system triggers a response to restore service. This ensures the application remains reachable even if a specific virtual machine or software service stops working.
Regional resources survive a single zone failing by using multiple zones within a region. To protect against a full region going offline, architects use multi-region resources and global load balancing to steer traffic to a healthy area. Eliminating single points of failure through geographic distribution improves the aggregate availability of the entire system, making it much more reliable than any single component.
StudyCerts
StudyCerts