Google Cloud Run is very easy to use.
Overall Satisfaction with Google Cloud Run
The main use is to host an image processing service. This involves generating large quantities of thumbnails, dividing large map images into tiles and extract geometries in floorplan PDF files. Using Cloud Run, we were able to reduce costs compared to using serverless solutions. It works very well for long processing times, with a 24-hour time limit per job. It's very practical and easy to deploy, eliminating the need for advanced DevOps knowledge.
Pros
- Performing time-consuming tasks in the background
- Hosting for high-demand HTTPS services
- Hosting services packaged in Docker images
Cons
- Limited deployment strategies. Traffic splitting exists, but it's basic. Rollback depends on manual intervention.
- Fragile local debugging and development. The local environment never 100% mirrors Cloud Run. Debug removal is nonexistent.
- Lack of more flexible non-HTTP jobs and workloads. No support for: Advanced Cron,
- Communication between jobs
- Cost reduction of approximately 60% when using serverless tools.
- Ease of service implementation and maintenance.
- Ease of rollback, greatly reducing frustration with faulty updates.
It has a similar purpose in terms of hosting and orchestrating applications in Docker containers. GoogleCloud Run stands out for being much easier and more intuitive to maintain and configure, and can even be used by teams with little knowledge of container orchestration (DevOps).That was the main reason we chose to use Google Cloud Run. We didn't want to waste a lot of time with complex deployment configurations.
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?
I wasn't involved with the selection/purchase process
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