Service Infrastructure によって、これらのプレーンで複数のパブリック API が使えるようになります。開発者は、これらの API を使用してサービスを Service Infrastructure に直接統合するか、Cloud Endpoints や API ゲートウェイなど、これらの API 上に構築されたフレームワークを使用できます。
API とサービスの作成
Service Infrastructure を使用してマネージドサービスを作成するには、サービス構成を作成して、サービス設定と動作（サービス名や API サーフェスなど）を定義する必要があります。次に、Service Management API にサービス構成をデプロイしてサービスを作成し、 Google Cloudに登録します。
Service Infrastructure を使用してマネージド サービスを実行するには、サービスで Service Control API を呼び出して、各リクエストのアドミッションコントロールと、API キーの検証や API メトリックのレポートなど、各レスポンスのテレメトリー レポートを呼び出す必要があります。これにより、Google Cloud によって提供される種類の豊富な機能をサービスで利用できるようになります。
サービスに課金パイプラインなどの内部コンポーネントがある場合、それらはアドミッション コントロールとテレメトリ レポート用の Service Control API を使用することもできます。たとえば、課金指標をCloud Billingに報告します。
サービス プロデューサーは、Service Consumer Management API と Service Networking API を使用して、サービス ユーザーを管理できます。これには、コンシューマーのテナント プロジェクトの作成、テナント プロジェクトとコンシューマー プロジェクト間のネットワーク ピアリングの設定、コンシューマーの割り当て上限の管理の管が含まれます。
[[["わかりやすい","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-04-21 UTC。"],[],[],null,["# Service Infrastructure\n\n\u003cbr /\u003e\n\nService Infrastructure is a foundational platform for creating, managing,\nsecuring, and consuming APIs and services across organizations. It is used\nby [Google APIs](https://github.com/googleapis/googleapis),\n[Cloud APIs](/apis), [Cloud Endpoints](/endpoints), and\n[API Gateway](/api-gateway). Service Infrastructure\nprovides a wide range of features to service consumers and service producers,\nincluding authentication, authorization, auditing, rate limiting, analytics,\nbilling, logging, and monitoring.\n\nArchitecture\n------------\n\nService Infrastructure is designed to support millions of service producers and\nservice consumers. In order to handle such scalability,\nService Infrastructure uses a distributed microservice architecture.\nThe system is divided into three *planes* based on their functionality:\n\n- The Management Plane, which lets developers manage configurations of their services and their usage of services.\n- The Data Plane, which handles the data traffic between the clients and the services. The data plane can run in different environments and support both internal and external clients.\n- The Control Plane, which controls the data plane based on the configurations coming from the management plane, such as rate limiting.\n\nService Infrastructure provides multiple public APIs for these planes. A developer\ncan use these APIs to integrate their service directly with Service Infrastructure,\nor use a framework built on top of these APIs, such as\n[Cloud Endpoints](/endpoints) and [API Gateway](/api-gateway).\n\nCreating APIs and services\n--------------------------\n\nTo create a managed service using Service Infrastructure, you need to\ncreate a [service configuration](/service-infrastructure/docs/glossary#config) to define your service\nsettings and behaviors, such as service name and API surface. You then deploy\nyour service configuration to the Service Management API to create your\nservice and register it with Google Cloud.\n\nFor more information, see Managing Services in the\n[How-to Guides](/service-infrastructure/docs/how-to).\n\nRunning APIs and services\n-------------------------\n\nTo run a managed service using Service Infrastructure, your service needs to\ncall the Service Control API for admission control on each request, and\ntelemetry reporting on each response, such as validating API keys and reporting\nAPI metrics. It allows your service to leverage the rich set of features\nprovided by Google Cloud.\n\nIf your service has some internal components, such as billing pipelines, they\ncan also use the Service Control API for admission control and telemetry\nreporting. For example, reporting billing metrics to\n[Cloud Billing](https://cloud.google.com/billing/docs).\n\nFor more information, see Integrating with Service Infrastructure in the\n[How-to Guides](/service-infrastructure/docs/how-to).\n\nManaging APIs and services\n--------------------------\n\nIf you are a service producer, you can use the Service Consumer Management API and\nthe Service Networking API to manage consumers of your service,\nincluding creating tenant projects for your consumers, setting up network\npeering between tenant projects and consumer projects, and managing the quota\nlimits of your consumers.\n\nFor more information, see Managing Service Consumers in the\n[How-to Guides](/service-infrastructure/docs/how-to).\n\nConsuming APIs and services\n---------------------------\n\nIf you are a service consumer, you can use the Service Usage to list, enable,\nand disable APIs and services in your Google Cloud projects, and apply quota\nrestrictions to services used by your Google Cloud projects or within your\norganization. You can manage both Google-provided services and services created using\n[Cloud Endpoints](https://cloud.google.com/endpoints).\n\nFor more information, see the [Service Usage](/service-usage/docs)\ndocumentation.\n\nGetting started\n---------------\n\nThe recommended way for most use cases to use Service Infrastructure is to use\n[Cloud Endpoints](/endpoints) to create and manage your services. To get\nstarted, see\n[Cloud Endpoints Quickstart](/endpoints/docs/deploy-api)."]]
