이 가이드에서는 함수를 배포하는 데 사용되는 최신 옵션과 기존 Google Cloud 옵션을 비교합니다. 이 페이지는 이전에 Cloud Functions API로 함수를 만들었고 Cloud Run Admin API로 전환하는 개발자에게 도움이 됩니다. 이 페이지에서는 개념, 구성, 배포, 트리거, 재시도와 같은 여러 영역에서의 주요 차이점을 설명합니다.
비교
Cloud Run Functions에는 다음과 같은 두 가지 버전이 있습니다.
Cloud Run Functions는 최신 버전의 함수로, Cloud Run에 서비스로 배포됩니다.
다음 방법 중 하나로 만들 수 있습니다.
Cloud Run Admin API(권장): 이 API (예:Google Cloud 콘솔, gcloud run, REST API 또는 Terraform 사용)로 만든 함수를 Cloud Run Admin API를 사용하여 독점적으로 관리할 수 있습니다.
Cloud Functions v2 API: 이 API(예: gcloud functions, REST API 또는 Terraform 사용)로 만든 함수는 Cloud Run Admin API 및 Cloud Functions v2 API로 관리될 수 있습니다. 이 API를 사용할 경우 함수를 배포할 때 트리거를 지정합니다. Cloud Run Admin API를 사용하여 전적으로 관리할 수 있도록 v2 API 함수를 분리하는 방법을 알아보세요.
Cloud Run Functions(1세대)(이전 명칭: Cloud Functions(1세대))는 제한된 이벤트 트리거, 런타임, 구성 가능성을 갖춘 원래 버전의 함수입니다.
자세히 알아보기
함수를 Cloud Run에 직접 배포하면 함수가 컨테이너로 자동 빌드되고 Cloud Run 서비스로 배포됩니다.
개념
다음 표에는 함수의 개념적 차이점이 요약되어 있습니다.
Cloud Run Functions
Cloud Run Functions(1세대)
이전 제품 이름
Cloud Functions(2세대)
Cloud Functions(1세대)
리소스 모델
함수는 소스 코드에서 배포되는 Cloud Run 서비스입니다.
소스 코드에서 함수가 배포됨
함수 유형 용어
HTTP 함수
이벤트 기반 함수라고도 하는 CloudEvents 함수는 모든 언어 런타임에서 지원됩니다.
HTTP 함수
Ruby, .NET, PHP 런타임만 CloudEvents를 지원합니다. Node.js, Go, Python, Java의 경우 백그라운드 함수를 사용하여 이벤트 기반 함수를 만듭니다.
할당된 HTTPS URL
run.app
Cloud Functions v2 API로 만든 함수에는 cloudfunctions.net 엔드포인트도 있습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Compare Cloud Run functions\n\nThis guide compares the latest and original Google Cloud choices for deploying\nfunctions. This page helps those who previously created functions with the\n[Cloud Functions API](/functions/docs/reference/rest) and are transitioning to the\nCloud Run Admin API. This page describes key differences in several areas,\nsuch as concepts, configuration, deployment, and triggers and retries.\n\nComparison\n----------\n\nThere are two versions of Cloud Run functions:\n\n- **Cloud Run functions** , is the latest version of functions,\n [deployed as a service on Cloud Run](/run/docs/resource-model#functions).\n They can be created in one of the following ways:\n\n - [Cloud Run Admin API](/run/docs/reference/cloud-run-admin-api-overview) (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.\n - [Cloud Functions v2 API](/functions/docs/reference/rest): 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](/functions/docs/managing#detach) a v2 API function so that it can be managed exclusively using the Cloud Run Admin API.\n- **Cloud Run functions (1st gen)** ,\n formerly known as Cloud Functions (1st gen), is the original version of\n functions with limited event triggers, runtimes, and configurability.\n [Learn more](/functions/1stgendocs/concepts/overview).\n\nBy deploying functions directly onto Cloud Run, your functions\nare automatically built as containers and deployed as a Cloud Run\nservice.\n\n### Concepts\n\nThe following table summarizes the conceptual differences for functions.\n\n### Configuration\n\nCloud Run builds functions into containers and deploys them as\nservices. When you deploy a function to Cloud Run, you have\ncomplete access and control over the function's behavior. For example, you can\nenable Direct VPC, configure GPUs, use volume mounts, and more.\n\nThe following table summarizes the configuration differences for functions:\n\n### Deployment\n\nSince August 2024, you can use Cloud Run to deploy and manage\nfunctions created with the Cloud Functions v2 API. As a result of this change:\n\n- Function metadata such as runtime ID and build configurations are stored in the Cloud Run service definition.\n- You can safely edit your function using the Cloud Run Admin API.\n- You can rely on the Cloud Run service definition as the source of truth for your function.\n\nHowever, note that functions created with the Cloud Run Admin API cannot be\nmodified with the Cloud Functions API.\n\nThe following table summarizes the differences in how you create, deploy, edit,\nand manage functions:\n\n### Triggers and retries\n\nThe following table compares triggers and retries for functions:\n\nDetach your function\n--------------------\n\nFunctions created using the [Cloud Functions v2 API](/functions/docs/apis)\n(for example, by using `gcloud functions`, the REST API, or Terraform) can be\ndetached from its existing API environment. After you detach a function, you can\nonly manage it using the\n[Cloud Run Admin API](/run/docs/reference/cloud-run-admin-api-overview). You might\nwant to do this if your workloads need to stay within the\n`run.googleapis.com` API boundary for\n[Assured Workloads](/assured-workloads/docs/overview), or to ensure\nthat your workloads use the [Cloud Run SKU](/skus/sku-groups/cloud-run).\nSee [Manage functions](/functions/docs/managing) to learn more.\n\nWhat's next\n-----------\n\n- Try the getting started guide for [deploying a Cloud Run function](/run/docs/quickstarts/functions/deploy-functions-console)."]]
