The latest Google Cloud incident in London is the type of occasion that ought to drive enterprises to rethink what cloud resilience actually means. Google stated the disruption was brought on by a “energy occasion” affecting London-based knowledge facilities in its europe-west2 area. The difficulty appeared early within the day and affected cloud companies that many organizations rely on, both instantly via their very own deployments or not directly via third-party platforms that run on Google Cloud.
What made this incident vital was not merely {that a} cloud area had issues. Cloud infrastructure, like all infrastructure, can and can fail. The actual challenge was the scope of the dependency chain. Banks, supply companies, e-bike suppliers, budgeting apps, some appointment companies via the Nationwide Well being Service app, and court docket video-link methods had been all caught within the disruption. These companies might seem unrelated, however in actuality, they’ll share the identical underlying cloud suppliers, regional infrastructure, managed companies, networks, identification methods, APIs, and operational dependencies.
Google later stated companies had recovered for many affected workloads, with solely a small variety of prospects nonetheless impacted. Nevertheless, the injury had already been accomplished. The incident confirmed how a lot fashionable enterprise depends upon cloud platforms which are extremely succesful however not proof against failure. It additionally confirmed that resilience shouldn’t be one thing enterprises robotically acquire by shifting to a hyperscaler. Resilient structure should be designed, funded, examined, and owned.
