Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/functions/docs/concepts/version-comparison below:

Compare Cloud Run functions | Cloud Run Documentation

Stay organized with collections Save and categorize content based on your preferences.

This guide compares the latest and original Google Cloud choices for deploying functions. This page helps those who previously created functions with the Cloud Functions API and are transitioning to the Cloud Run Admin API. This page describes key differences in several areas, such as concepts, configuration, deployment, and triggers and retries.

There are two versions of Cloud Run functions:

• Cloud Run functions, is the latest version of functions, deployed as a service on Cloud Run. They can be created in one of the following ways:

  • Cloud Run Admin API (Recommended): Functions created with this API (for example, by using Google Cloud console, gcloud run, the REST API, or Terraform) can be managed exclusively using the Cloud Run Admin API.
  • Cloud Functions v2 API: Functions created with this API (for example, by using gcloud functions, the REST API, or Terraform) can be managed with the Cloud Run Admin API as well as the Cloud Functions v2 API. When using this API, you specify the trigger when deploying your function. Learn how to detach a v2 API function so that it can be managed exclusively using the Cloud Run Admin API.

• Cloud Run functions (1st gen), formerly known as Cloud Functions (1st gen), is the original version of functions with limited event triggers, runtimes, and configurability. Learn more.

By deploying functions directly onto Cloud Run, your functions are automatically built as containers and deployed as a Cloud Run service.

The following table summarizes the conceptual differences for functions.

• HTTP functions
• CloudEvents functions, also referred to as event-driven functions, are supported in all language runtimes.

• HTTP functions
• Only Ruby, .NET, and PHP runtimes support CloudEvents. For Node.js, Go, Python, and Java, create event-driven functions using Background functions.

Functions created with the Cloud Functions v2 API also have a cloudfunctions.net endpoint.

• Cloud Run Source Developer (roles/run.sourceDeveloper)
• Service Usage Consumer (roles/run.serviceusage.serviceUsageConsumer)
• Service Account User (roles/iam.serviceAccountUser)

• Cloud Functions Developer (roles/cloudfunctions.developer)

Cloud Run builds functions into containers and deploys them as services. When you deploy a function to Cloud Run, you have complete access and control over the function's behavior. For example, you can enable Direct VPC, configure GPUs, use volume mounts, and more.

The following table summarizes the configuration differences for functions:

• Up to 60 minutes for HTTP-triggered functions

• Up to 9 minutes for event-driven functions created with the Cloud Functions v2 API

• Up to 9 minutes

Since August 2024, you can use Cloud Run to deploy and manage functions created with the Cloud Functions v2 API. As a result of this change:

• Function metadata such as runtime ID and build configurations are stored in the Cloud Run service definition.
• You can safely edit your function using the Cloud Run Admin API.
• You can rely on the Cloud Run service definition as the source of truth for your function.

However, note that functions created with the Cloud Run Admin API cannot be modified with the Cloud Functions API.

The following table summarizes the differences in how you create, deploy, edit, and manage functions:

The following table compares triggers and retries for functions:

For functions created with the Cloud Functions v2 API, you specify triggers as part of function deployment.

For functions created with the Cloud Functions v2 API, you specify retries as part of function deployment with the --retry flag.

Functions created using the Cloud Functions v2 API (for example, by using gcloud functions, the REST API, or Terraform) can be detached from its existing API environment. After you detach a function, you can only manage it using the Cloud Run Admin API. You might want to do this if your workloads need to stay within the run.googleapis.com API boundary for Assured Workloads, or to ensure that your workloads use the Cloud Run SKU. See Manage functions to learn more.

• Try the getting started guide for deploying a Cloud Run function.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4