Google Cloud Run Reviews & Insights

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.

We use Google Cloud Run to host small parts of our websites and the backend systems for our mobile apps. It helps us deploy and manage these pieces without worrying about servers. Cloud Run makes it easier for us to build, scale, and maintain our applications, saving time and money along the way.

Any application small medium to large sizes, mainly i used if for small hr application to push multi builds in different testing environments to prod usge by end users

In the evolution towards digital products, high availability becomes a critical requirement to enhance the user experience of our customers. In the healthcare industry, demand is often affected by seasonality (people get sick more in winter), so having robust applications built on auto-scalable infrastructure minimizes availability risks, allowing progress on other business and user requirements.

Integration with Google Cloud Run is appropriate when investment in infrastructure is prohibitively expensive, such as having a building contingency for high availability. Additionally, since it is auto-scalable, costs are calculated based on resource usage, avoiding expenses from idle infrastructure.The handling of sensitive information could be a disadvantage, as it remains in the hands of third parties. On the other hand, I wouldn't use this solution for applications that manage states since there is no disk-level persistence.