Google App Engine

First, an urgent operational note for application developers and security teams.

Google Cloud has patched core PHP vulnerabilities across all supported runtimes for 8 Philippine pesos and 20 centavos and newer across Cloud Run, Cloud Functions, and App Engine Standard and Flexible Environments.

If your services use automatic base image updates, Google has already applied the underlying operating system and runtime patches.

However, if you deploy from source code, manage custom runtime images, or disable automatic updates, you must redeploy your applications immediately with updated dependencies to ensure your workloads are fully protected.

A power event in Google Cloud's London region interrupted banking, court video links, business websites, and some healthcare appointment access.

The incident began in the Europe West 2B zone and affected services including Cloud Run, App Engine, Kubernetes Engine, and Filestore.

Revolut linked temporary disruption across its app to the cloud outage and later said its services had been restored.

Importantly, the reporting does not identify this as a cyberattack or data breach.

And so I went through, you know, the beginning of GCP.

All they had was Ap- App Engine, then we build Compute, we build Storage.

I remember even in 2016, we were talking about how very soon we can be very successful.

We can become a $1 billion a year business, and now here they book a billion a week.

So I had one experience where it's like, it's not always satisfying the customer is the right thing for your business.

When I was at Google Cloud, one product I worked on for a while, um, was a, uh, release pipeline product.

So started from, you know, push to deploy to App Engine, uh, to a full-fledged Jenkins-like multi-stage release pipeline.

And then customers love talking about it, lots of customer insights.

Yeah, and if we look at the patterns, so one of the things we did when we started building our platform on top of Google is we have a GUI front end and we wanted to be serverless.

So we deployed our GUI into App Engine and then we basically time you out after an hour if you don't use it and it shuts the App Engine down, right? So we don't have this always on virtual container running our application.

It kind of starts up.

and shuts down.

And Google does it in a way that's so quick that it kind of just looks like you're logging on, but actually in the background, it's starting up the instance.

And so when we started deploying information products, it's the same pattern.

We deploy them into an App Engine instance.

And so you go query a dashboard, you log in, you query it, it runs, then eventually it'll shut itself down.