Cloud Run Vs App Engine - GCP
Sajana Vijayan
Software Engineering Lead at Boeing with expertise in AI and Machine Learning
Cloud Run Vs App Engine - GCP
All thanks to my ex-collegue as he was not quitely convinced by the idea of choosing App Enginer over Cloud Run .
I have ran an experiment and here are my views as belows:
I am not an advocate of any of the cloud services still , for small web applications with a large database , I found App engine can be used since the results are fast as it runs 24/7 .For Cloud Run we have to containarise everything and Cloud Run will be ran only when it gets requests.It has to do the below tasks , hence it is slow .
But , catch here is Cloud Run is much cheaper compaed to App Engine .
Senior Data Engineer at H&M
2 年App Engine is a Platform-as-a-Service (It uses GCE underneath) which means the code runs inside a secure sandbox environment. You simply deploy your code, and the platform does everything else for you. While Cloud Run is a Serverless offering(It uses GKE underneath), and it is designed for stateless web applications accessed via HTTP, WebSockets, or gRPC requests or streams. Also, when we are talking about App Engine then first we need to consider both the offering of App Engine which are a bit different in the way they work. App Engine Standard - Limited runtimes, no WebSockets support, quick starts up, stateless, more suited for the workload that requires immediate scaling. Scales to 0 when not serving requests. App Engine Flexible - This is more open as it allows you to use custom runtimes as it uses docker containers. So, if your runtime isn't available in the provided runtimes, you can create your own Dockerfile for the execution environment. The caveat here is, that it requires having at least 1 instance running, even if the app is not in use, plus the scaling up and down takes a few minutes. App Engine Flexible environment is a hybrid between the standard, code-centric App Engine and the container-based Cloud Run and GKE.