Google Cloud Run - Serverless Micro Service on GCP
July 30, 2025
Google Cloud Run - Serverless Micro Service on GCP

Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Google Cloud Run
We have been setting up some new micro services. As the load on them is not consistent throughout the day, we think that going serverless is the right decision. Also, we didn't want to deal with Kubernetes, at least at the moment. That makes Google Cloud Run our obvious choice.
Pros
- Serverless micro service that only runs when there's a real demand
- Serverless micro service that is very elastic, can scale up & down very quickly
- Serverless micro service that integrates with other GCP services naturally
Cons
- Like any other serverless FaaS, cold start is an issue
- Unlike Lambda, simple code zip package is not supported, making the cold start issue worse
- More complex pricing system than AWS Lambda
- As our workload is very light, & intermittent throughout the day, Google Cloud Run is much more cost effective than running a full always-on container or VM
- Using Docker image as package delivery medium simplifies build process, & allows "build once run everywhere" pattern
- Setting up micro services using Google Cloud Run with strictly private networking is not overly complicated
AWS Lambda supports code zip package, enabling lower cold start time. Also, AWS Lambda pricing is much simpler, easier to understand.
Other than that, the 2 products are very similar, including the Docker image support: the image must be built based on proprietary base image.
Obviously, if your other services are running in GCP, then Google Cloud Run is your only choice for tight integration, & private networking.
Do you think Google Cloud Run delivers good value for the price?
Yes
Are you happy with Google Cloud Run's feature set?
Yes
Did Google Cloud Run live up to sales and marketing promises?
Yes
Did implementation of Google Cloud Run go as expected?
Yes
Would you buy Google Cloud Run again?
Yes
Comments
Please log in to join the conversation