Google Cloud Run Information Reviews & Insights

We use a Docker container that converts images to smaller sizes and makes map tiles with large images for indoor maps for navigation. Using just serverless functions was not enough because of the time limit. Making conversions with images takes running time that was only supported using Google Run, which increases the time limit to 24 hours.

It's more suited for having tasks that involve calculation or conversions, like converting big images and tiles. Have tasks that take up to 30 minutes for each execution, Cloud Run is well-suited. But when considering smaller tasks the do not take so much time using Cloud Run is not indicated. Using Google functions is more suited.

We use Cloud Run to deploy our isolated service application(s) that are logically far off from our main application but also share some of the resources and database tables with the main application. We use it to "fire and forget" out small serverless projects that don't need periodic maintenance and taking care of all the while maintaining performance and separation of concerns

For scenarios where you need an isolated workspace and application namespace, it is very well suited. It can run up a serverless instance of your application in seconds and will give strong guarantees over its runtime given that all dependencies were taken care of. For entangled workflows, its recommended to use a server/on prem solution

We participated in a trial of modernizing our continuous integration and deployment methods and how we would orchestrate the various resources that need to stand up and down during the different pipelines dynamically. We had to re-architect parts of these pipelines to accommodate the new stateless, serverless infrastructure paradigm. We ran some tests over about a quarter on this and similar offerings.

As our product is event-driven, we were well-versed in this method of using Google Cloud Run. We had various checkpoints in our pipelines during a build, sending events to messaging systems or recording/auditing some steps very well suited to stateless event processing, such as was provided. That said, I don't think participating in a build pipeline is the most effective use of Cloud Run.