App Engine got: - better dashboard - because container image is delivered by Google it might be more reliable than custom image (unless you are using buildpacks) I had a case where heavy load services running on App Engine migrated to Cloud Run, and had to be rolled back to App Engine. After months of hassle-free uptime on Cloud Run, suddenly it started to throw 503 on 10-20% of traffic with zero logs or debug info. Cloud Run Google support could always blame it on container image, on App Engine we need to focus on code only.
@@peeratchaipetpadriew7337 in general yes (+ eventual build process is different). Cloud Run is more recent generation comparing to App Engine flex. I wouldn't be surprised if flex was actually migrated to Cloud Run and currently its just extra software layer.
App Engine is our "Serverless 1.0" platform (2008) while Cloud Functions & Cloud Run are "Serverless 2.0" platforms (2017 and 2019, respecticely). As such, they're more modern and adhere more towards today's software development lifecycle. They also cost less (in general) than App Engine. That said, App Engine is the "OG" serverless platform. If you use an original runtime (Python, Java, Go, PHP), you get bundled services like Datastore, Memcache, Task Queues (pull or push), and many others, including a firewall and CDN, none of which come with Cloud Functions or Cloud Run (you have to setup equivalent services on your own).
Don’t forget to like and subscribe for more Google Cloud tips and tricks → goo.gle/GoogleCloudTech
Check out part 2 here! → goo.gle/3uNMyUM
Loved that summary; it was just what I was looking for. Thanks for making it quick and include examples!
Happy to hear it was useful!
We're so glad you found this video helpful! Don't forget to check out part 2 → goo.gle/3uNMyUM
Is there are benefits of using App Engine against Cloud Run?
App Engine got:
- better dashboard
- because container image is delivered by Google it might be more reliable than custom image (unless you are using buildpacks)
I had a case where heavy load services running on App Engine migrated to Cloud Run, and had to be rolled back to App Engine.
After months of hassle-free uptime on Cloud Run, suddenly it started to throw 503 on 10-20% of traffic with zero logs or debug info. Cloud Run Google support could always blame it on container image, on App Engine we need to focus on code only.
@@MichaelSlowik What about app engine flex? In flex, we could use our custom image. So the differences then is only the dashboard?
@@peeratchaipetpadriew7337 in general yes (+ eventual build process is different). Cloud Run is more recent generation comparing to App Engine flex. I wouldn't be surprised if flex was actually migrated to Cloud Run and currently its just extra software layer.
App Engine is our "Serverless 1.0" platform (2008) while Cloud Functions & Cloud Run are "Serverless 2.0" platforms (2017 and 2019, respecticely). As such, they're more modern and adhere more towards today's software development lifecycle. They also cost less (in general) than App Engine. That said, App Engine is the "OG" serverless platform. If you use an original runtime (Python, Java, Go, PHP), you get bundled services like Datastore, Memcache, Task Queues (pull or push), and many others, including a firewall and CDN, none of which come with Cloud Functions or Cloud Run (you have to setup equivalent services on your own).
Excellent one
Thanks