Cloud Run functions では、サーバーの管理やソフトウェアの構成、フレームワークの更新、オペレーティング システムへのパッチ適用などを行う必要がありません。ソフトウェアとインフラストラクチャは完全に Google でフルマネージドされるため、コードの作成に集中できます。また、リクエストまたはイベントに応じてリソースが自動的にプロビジョニングされるため、Cloud Run サービスは、ユーザーによる操作を必要とせず、1 日に数回の関数呼び出しから、何百万回の呼び出しまで自動スケーリングされます。スケーリング動作をより細かく制御する必要がある場合は、手動スケーリングを使用できます。
Cloud Run で関数、ソースコード、コンテナ イメージをデプロイするメリットについては、コンテナ ランタイム契約をご覧ください。
[[["わかりやすい","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,["# When should I deploy a function to Cloud Run?\n\n| **Note:** Cloud Functions has been renamed to Cloud Run functions. For more information, see the [Cloud Run functions blog post](https://cloud.google.com/blog/products/serverless/google-cloud-functions-is-now-cloud-run-functions).\n\nCloud Run removes the work of managing servers, configuring\nsoftware, updating frameworks, and patching operating systems. The software and\ninfrastructure are fully managed by Google so that you just add code.\nFurthermore, provisioning of resources happens automatically in response to\nrequests or events.\nThis means that a Cloud Run service automatically scales out from a few\ninvocations a day to many millions of invocations without any work from you.\nYou can optionally use [manual scaling](/run/docs/configuring/services/manual-scaling)\nif you need more control over your scaling behavior.\n\nWhen you deploy a function, source code or a container image to\nCloud Run, you receive all of the benefits described in the\n[Container runtime contract](/run/docs/container-contract).\n\nUse cases for deploying functions\n---------------------------------\n\nYou can directly deploy a function bound to events in order to implement\nasynchronous workloads (such as lightweight [ETL](/learn/what-is-etl)) or cloud\nautomations (such as triggering application builds).\nIn addition, the automatic provisioning of an HTTPS endpoint makes functions a\nperfect candidate for webhooks.\n\nSee the following table for additional common use cases for deploying a function\nto Cloud Run:\n\nConnect and extend cloud services\n---------------------------------\n\nCloud Run functions provides a connective layer of logic that lets you write\ncode to connect and extend cloud services. Listen and respond to a file upload\nto Cloud Storage, a log change, or an incoming message on a Pub/Sub\ntopic. Cloud Run functions augments existing cloud services and lets you\naddress an increasing number of use cases with arbitrary programming logic.\nCloud Run functions have access to the Google Service Account credential and\nare thus seamlessly authenticated with the majority of Google Cloud services,\nincluding Cloud Vision, as well as many others. In addition,\nCloud Run functions are supported by numerous\n[Cloud Client Libraries](/apis/docs/cloud-client-libraries), which\nfurther simplify these integrations.\n\nWhat's next\n-----------\n\n- Try the [getting started guide for deploying a function](/run/docs/quickstarts/functions/deploy-functions-console).\n- If you have existing functions and need to use the `gcloud functions deploy` command, the Cloud Functions v2 API, or the `google_cloudfunctions2_function` Terraform configuration for backward compatibility, you can [deploy functions with the `gcloud functions` command](/functions/docs/deploy)."]]
