Google should have a documentation explaining cloud run vs app engine standard/flexible differences, is so frustating have to search on stackoverflow to understand it.
Ok, why would we want to migrate away from Google App Engine? I just spent the last 6 months learning App Engine and launched an App built with Ktor running on App Engine Standard...
It is based on philosophy : using containers, Now even App Engine Flex has containers, Flex is not good if your traffic has sudden spikes, because it is built on top of GCE, and it will take time to spawn containers, Then it came a new way to do it on Kubernetes, using Knative, so you will get App Engine classic (scaling down to zero), and getting traffic with spikes to add/remove containers without breaking your head, and this is the magic of Serverless
@@AlianeAbdelouahab there are features in app engine that run does not have. And application restrictions in run that don't apply to your applications in google app engine. This isn't a 1 to 1 but one with containers and one without. I understand the benefits of run and I like it. But I think the way the comparison in this video was presented was misleading.
@@geoffreyjohnston4047 i think the problem is about what the market needed, 2008 and 2021 is more than 10 years of evolution, when App Engine was deployed to the market, Google Cloud dident have as much technologies as there are now, for example Traffic Split is easy using old App Engine way, but now people want fine tune control using other services on GCP (of course we can still have simple easy way on Cloud Run that they forgot to mention in the video when they talked about CI/CD)
I don't know about deploying Rust to Cloud Run with buildpacks. But you can certainly deploy Rust code to Cloud Run using a Dockerfile. Search for "cloud run quickstart" and click the link to "Other" programming languages. From there you can find a Github repo that shows you how to do it.
There are some significant differences in the application restrictions if running in cloud run other than just being in a container. This video seems misleading on that as well as it feels worrying that it's implied that app engine would go away eventually since there is cloud run.
What are some of these "restrictions" you're referring to? The container contract? We have no intent on misleading users, so please explain what you mean. Also, this is an *optional* migration... no one will force you to migrate away from App Engine. (App Engine isn't going away.) This is just an option for those whose software development workflow now includes containers where you still want your app to run serverlessly.
@@WesleyChun Correct me if I'm wrong Im still new to google run concept but doesnt it only work by a request to a single url path and will be forced to scale down to 0 if no requests are coming in? Many applications will break under such a restriction that could work in app engine.
@@geoffreyjohnston4047 App Engine also has a request based autoscaler. And both App Engine and Cloud Run give the ability to specify a minimum number of instances
@@SterenTV even when you set a minimum number of instance in google run it is all drive through http requests. So forget about any background processing. I'm sure for a lot of people it is an easy transition. But it depends on your application and what all it is doing. And there are definitely applications I have in production now that I can put in app engine just fine that won't work in google run.
And again nothing wrong with Google run. I want to use it. The way it downscales and you arent charged is amazing. And is a great boon if your application will work that way or if you can refactor to make it work. But any video talking about migrating from one to the other should mention this type of requirement.
