Google Cloud Run Review Insights

Score8.7 out of 10

31 Reviews and Ratings

Back to Reviews

Insights from Google Cloud Run Reviewers

Based on 8 verified reviews published in the last 18 months

What other products like Google Cloud Run have you used or evaluated?

8 answered

When considering alternatives or complementary services to Google Cloud Run, a quarter of reviewers (2 of 8) indicated experience with or evaluation of Google Kubernetes Engine (GKE). This suggests that users engaging with serverless container platforms often operate within a broader Google Cloud ecosystem, where GKE serves as a significant offering for container orchestration. The mentions of GKE were consistently positive, indicating that reviewers generally hold a favorable view of this service. This positive sentiment could stem from its robust capabilities for managing complex, scalable containerized applications, even if it requires more operational overhead compared to Cloud Run. The presence of GKE in these discussions highlights its role as a key comparative benchmark or a strategic component within a comprehensive cloud architecture for those leveraging container technologies on Google Cloud, often alongside or as an alternative to Cloud Run depending on specific project requirements and desired levels of abstraction.

Google Kubernetes Engine

2 mentions

Google Kubernetes Engine (GKE) was mentioned by a quarter of reviewers as another product they have used or evaluated.…

Google Kubernetes Engine (GKE) was mentioned by a quarter of reviewers as another product they have used or evaluated. This indicates that users familiar with Google Cloud Run often have experience with or consider GKE, another Google Cloud offering for containerized application deployment. Reviewers' mentions of GKE were positive, suggesting it is viewed as a capable platform within the Google Cloud ecosystem.

What positive or negative impact (i.e. Return on Investment or ROI) has Google Cloud Run had on your overall business objectives?

8 answered

Google Cloud Run has demonstrably contributed to business objectives, primarily through significant cost efficiencies and streamlined operational processes. A substantial majority of reviewers, 5 out of 8, highlighted considerable cost savings, attributing this to its serverless architecture and 'scale-to-zero' capabilities, which eliminate charges for idle resources. Beyond financial benefits, the platform is frequently cited for its ease of use and management, with 4 out of 8 reviewers noting simplified deployment and maintenance. This operational ease, coupled with improved deployment speeds, allows development teams to focus more on feature delivery rather than infrastructure management. Furthermore, its inherent scalability and performance characteristics support agile microservices development, enabling rapid adjustments to resource allocation and granular control over critical services.

Cost Savings

5 mentions

Reviewers consistently report significant cost reductions when utilizing Google Cloud Run, with 5 out of 8 reviewers sp…

Reviewers consistently report significant cost reductions when utilizing Google Cloud Run, with 5 out of 8 reviewers specifically mentioning this benefit. The primary driver for these savings is the platform's serverless nature and 'scale-to-zero' functionality, which means users only pay for active compute time, drastically reducing expenses for intermittent or bursty workloads. One reviewer noted an approximate 60% cost reduction compared to alternative solutions.

Ease of Use and Management

4 mentions

The simplicity of implementing and maintaining services on Google Cloud Run is a frequently praised aspect, cited by 4…

The simplicity of implementing and maintaining services on Google Cloud Run is a frequently praised aspect, cited by 4 out of 8 reviewers. This ease extends to deployment, upgrades, and the overall management of applications. Reviewers appreciate that even complex setups, such as microservices with private networking, are not overly complicated to configure.

Scalability and Performance

3 mentions

Google Cloud Run is recognized for its robust scalability and performance capabilities, which 3 out of 8 reviewers high…

Google Cloud Run is recognized for its robust scalability and performance capabilities, which 3 out of 8 reviewers highlighted as beneficial. The platform's built-in auto-scaling features reduce operational overhead, allowing applications to handle varying loads efficiently. This also provides the flexibility to quickly allocate more resources to address performance issues, supporting the development of microservices with granular control over scaling critical components.

Deployment Speed

2 mentions

Reviewers indicate that Google Cloud Run significantly accelerates deployment processes and testing cycles, with 2 out…

Reviewers indicate that Google Cloud Run significantly accelerates deployment processes and testing cycles, with 2 out of 8 reviewers specifically mentioning this benefit. This increased speed allows development teams to release new features and services much faster, shifting focus from infrastructure management to product innovation. It also proves valuable for rapid prototyping and proof-of-concept development.

Besides Google Cloud Run, what other software do you regularly use? How likely would you be to recommend it to a friend or colleague?

8 answered

Reviewers frequently mentioned other software tools they regularly use alongside Google Cloud Run, with two specific platforms emerging as notable mentions within the small sample of 8 reviews. Docker was cited by 25% of reviewers (2 of 8), indicating its presence in the development workflows of some users. Similarly, AWS Lambda was also mentioned by 25% of reviewers (2 of 8), suggesting its use in serverless architectures or alongside other cloud services. While these tools were identified, the provided review snippets did not elaborate on the specific use cases, detailed reasons for their recommendation, or the nature of their integration with other systems. The sentiment for both Docker and AWS Lambda was categorized as mixed based on the available data, reflecting mentions without explicit positive or negative framing in the provided quotes. This suggests that while these tools are part of the ecosystem, more detailed feedback would be needed to understand user satisfaction or specific recommendations.

Docker

2 mentions

Docker was mentioned by a quarter of reviewers as another software tool they regularly utilize. While its presence in d…

Docker was mentioned by a quarter of reviewers as another software tool they regularly utilize. While its presence in development environments is noted, the provided review excerpts did not offer specific details regarding its application, user experience, or reasons for recommendation.

AWS Lambda

2 mentions

AWS Lambda was cited by 25% of reviewers as a complementary or alternative service in their software stack. The mention…

AWS Lambda was cited by 25% of reviewers as a complementary or alternative service in their software stack. The mentions indicate its use; however, the available data does not provide further context on specific implementation details, user satisfaction, or the rationale behind its regular usage.

Describe how you use Google Cloud Run in your organization. What are the business problems the product addresses and what is the scope of your use case?

8 answered

Organizations primarily utilize Google Cloud Run to address challenges related to infrastructure management, operational efficiency, and cost optimization, particularly for workloads with variable demand. A significant benefit, cited by three of eight reviewers, is the reduction in operational overhead, enabling smaller teams to deploy applications more rapidly without extensive DevOps expertise. This ease of deployment and management directly contributes to cost savings, a key advantage highlighted by nearly 40% of reviewers, especially beneficial for early-stage startups managing cloud expenses based on usage. Furthermore, Cloud Run is frequently chosen for its ability to handle inconsistent loads, with two of eight reviewers noting its suitability for serverless architectures that scale efficiently with fluctuating demand, thereby avoiding the complexities of managing container orchestration platforms like Kubernetes. A specific and recurring use case, also mentioned by three of eight reviewers, involves image processing services, which benefit from Cloud Run's capacity to manage long-running tasks like generating thumbnails and processing large map images.

Cost Savings

3 mentions

Reviewers frequently highlight Google Cloud Run's ability to reduce infrastructure costs. This is attributed to its ser…

Reviewers frequently highlight Google Cloud Run's ability to reduce infrastructure costs. This is attributed to its serverless nature and pay-per-use model, which allows organizations, particularly startups, to manage cloud expenses more effectively by only paying for resources consumed.

Reduced Operational Overhead

3 mentions

A notable advantage of Google Cloud Run, as reported by three of eight reviewers, is the significant reduction in opera…

A notable advantage of Google Cloud Run, as reported by three of eight reviewers, is the significant reduction in operational overhead. Its user-friendly deployment process minimizes the need for specialized DevOps knowledge, allowing development teams to focus more on shipping features and less on infrastructure management.

Image Processing Use Case

3 mentions

Cloud Run is specifically leveraged by three of eight reviewers for image processing tasks, which often involve computa…

Cloud Run is specifically leveraged by three of eight reviewers for image processing tasks, which often involve computationally intensive and time-consuming operations. Its capability to support long-running processes, sometimes up to 24 hours, makes it suitable for tasks such as generating thumbnails, tiling large images, and extracting data from PDF files.

Handling Inconsistent Load

2 mentions

Reviewers find Google Cloud Run particularly effective for applications experiencing inconsistent or fluctuating loads.…

Reviewers find Google Cloud Run particularly effective for applications experiencing inconsistent or fluctuating loads. The serverless architecture allows for automatic scaling, ensuring resources are available when demand is high and scaled down when demand is low, without the need for manual intervention or the complexity of managing Kubernetes.

Please provide some detailed examples of areas where Google Cloud Run has room for improvement.

8 answered

Reviewers of Google Cloud Run identified several areas for potential improvement, primarily concerning operational performance, user experience, and cost structure. A notable concern, cited by 3 out of 8 reviewers, is the platform's cold start performance, which can introduce unpredictable latency, particularly for services requiring rapid response times. This performance characteristic is common in serverless FaaS environments but was highlighted as a specific challenge for Cloud Run users. Beyond performance, 2 of 8 reviewers expressed difficulties with the clarity and completeness of the documentation, indicating that users sometimes resort to trial and error to implement solutions effectively. This suggests a need for more detailed and accessible guidance to streamline the development process. Furthermore, the pricing model was a point of contention for 2 out of 8 reviewers, who found it to be comparatively expensive, even for smaller applications, and more complex than alternative serverless offerings. These observations collectively point to opportunities for Google Cloud Run to enhance its responsiveness, improve user onboarding through clearer resources, and refine its cost-effectiveness for a broader range of deployments.

Cold Start Performance

3 mentions

Reviewers noted that cold starts present a challenge for Google Cloud Run, with 3 out of 8 reviewers specifically menti…

Reviewers noted that cold starts present a challenge for Google Cloud Run, with 3 out of 8 reviewers specifically mentioning this issue. They described it as a common characteristic of serverless functions but highlighted that it can lead to unpredictable latency and slower initial response times, especially for heavier containers or applications demanding quick execution. This can impact the user experience and the suitability of the platform for certain low-latency use cases.

Documentation Clarity

2 mentions

The clarity of Google Cloud Run's documentation was an area of concern for 2 out of 8 reviewers. These users indicated…

The clarity of Google Cloud Run's documentation was an area of concern for 2 out of 8 reviewers. These users indicated that the existing documentation can be complex and sometimes requires developers to engage in trial and error to fully understand and implement features. This suggests a need for more detailed and straightforward guidance to improve the developer experience and reduce implementation friction.

Pricing

2 mentions

The pricing structure of Google Cloud Run was identified as a drawback by 2 out of 8 reviewers. These users felt that t…

The pricing structure of Google Cloud Run was identified as a drawback by 2 out of 8 reviewers. These users felt that the service could be expensive, even for small-scale applications, and perceived its pricing system as more intricate compared to some alternative serverless platforms. This suggests that cost-effectiveness and pricing transparency could be areas for refinement.

Please provide some detailed examples of things that Google Cloud Run does particularly well.

8 answered

Google Cloud Run is frequently recognized for its operational efficiency and flexibility, particularly in managing microservices. Reviewers consistently highlight its robust auto-scaling capabilities, enabling services to quickly adapt to fluctuating demand. A core strength, emphasized by 3 of 8 reviewers, is its serverless and demand-based execution model, which allows applications to run only when needed and scale down to zero during inactivity. This "very cost efficient" approach, noted by 2 of 8 reviewers, makes it well-suited for event-driven architectures and helps optimize resource consumption. Furthermore, 2 of 8 reviewers pointed to its effectiveness in handling background and scheduled tasks, describing it as a reliable "serverless cron." Its seamless integration with other Google Cloud Platform services, such as Cloud SQL and Pub/Sub, also contributes to its appeal for building interconnected cloud-native applications.

Auto Scaling

3 mentions

Reviewers frequently highlight Google Cloud Run's auto-scaling capabilities, noting its elasticity and ability to quick…

Reviewers frequently highlight Google Cloud Run's auto-scaling capabilities, noting its elasticity and ability to quickly adjust resources based on demand. This feature allows services to efficiently handle fluctuating workloads by scaling both up and down rapidly.

Serverless & Demand-Based Execution

3 mentions

Google Cloud Run's serverless and demand-based execution model is a significant strength, highlighted by 3 of 8 reviewe…

Google Cloud Run's serverless and demand-based execution model is a significant strength, highlighted by 3 of 8 reviewers. This approach ensures microservices run only when triggered by actual demand, including scaling completely to zero during idle periods. This capability not only makes it ideal for event-driven architectures, such as handling webhooks, but also contributes to its "very cost efficient" nature, a benefit specifically noted by 2 of 8 reviewers.

Background and Scheduled Tasks

2 mentions

Several reviewers, representing 2 of 8, pointed to Google Cloud Run's effectiveness in managing background and schedule…

Several reviewers, representing 2 of 8, pointed to Google Cloud Run's effectiveness in managing background and scheduled tasks. It is described as a reliable solution for automating routine operations, such as generating reports, scraping data, or sending automated emails, functioning as a "serverless cron" with container flexibility.

Cost Efficiency

2 mentions

Container Image Management

2 mentions