[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-25。"],[[["\u003cp\u003eApigee hybrid is a platform for managing APIs using a hybrid deployment model, featuring a Google-hosted management plane and a customer-managed runtime plane on supported Kubernetes platforms.\u003c/p\u003e\n"],["\u003cp\u003eThe hybrid model allows for managing both internal and external APIs in one place, providing a unified experience for developers, partners, and customers, while allowing the flexibility to host enterprise-grade hybrid gateways on-premises or across various cloud environments.\u003c/p\u003e\n"],["\u003cp\u003eAll API traffic in Apigee hybrid is processed within the user's network under their control, while the management services, such as UI and API analytics, are managed by Google in the cloud.\u003c/p\u003e\n"],["\u003cp\u003eThe runtime plane is composed of containerized services such as Message Processors, Synchronizer, and Cassandra datastore, which are run and maintained in the user's own Kubernetes cluster, providing agility through staged rollouts and auto-scaling.\u003c/p\u003e\n"],["\u003cp\u003eThe platform caters to various user types, including system administrators/operators responsible for installation and maintenance, and developers who create and deploy API proxies, with advantages including increased agility, reduced latency, increased API adoption, and greater control over API runtimes.\u003c/p\u003e\n"]]],[],null,["# What is Apigee hybrid?\n\n| You are currently viewing version 1.3 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nApigee hybrid is a platform for developing and managing API proxies that features a hybrid deployment model.\nThe hybrid model includes a management plane hosted by Apigee in the Cloud and a runtime plane that you install\nand manage on one of the [supported Kubernetes platforms](/apigee/docs/hybrid/v1.3/install-before-begin#supported-platforms).\n\nAPI programs in a hybrid world\n------------------------------\n\nApigee hybrid consists of a management plane maintained by Google and a runtime plane\nthat you install on a [supported Kubernetes platform](/apigee/docs/hybrid/v1.3/install-before-begin#supported-platforms). Both planes use Google Cloud\nPlatform services, as the following image shows:\n\nAs you can see, hybrid consists of the following primary components:\n\n- [Apigee-run **management plane**](#about-the-management-plane): A set of services hosted in the cloud and maintained by Google. These services include the UI, management API, and analytics.\n- [Customer-managed **runtime plane**](#about-the-runtime-plane): A\n set of containerized runtime services that you set up and maintain in your own Kubernetes\n cluster. All API traffic passes through and is processed within the runtime plane.\n\n You manage the containerized runtime on your Kubernetes cluster for greater agility with\n staged rollouts, auto-scaling, and other operational benefits of containers.\n- **[Google Cloud](#about-gcp)**: A suite of Cloud services hosted by Google.\n\nOne key thing to know about hybrid is that all API traffic is processed within the boundaries of\nyour network and under your control, while management services such as the UI and API analytics run\nin the cloud and are maintained by Google. For more information, see [Where is\nyour data stored?](/apigee/docs/hybrid/v1.3/where-data) \nThe following video provides a deep dive into the hybrid architecture:\n\nAbout the runtime plane\n-----------------------\n\nThe runtime plane is a set of containerized runtime services that you set up and maintain in your\nown Kubernetes cluster running on a [supported Kubernetes platform](/apigee/docs/hybrid/v1.3/install-before-begin#supported-platforms).\nAll API traffic passes through and is processed within the runtime\nplane. The runtime plane includes the following major components:\n\n- [Message Processors](#message-processor)\n- [Synchronizer](#synchronizer)\n- [Cassandra](#cassandra-datastore)\n- [MART](#mart)\n- [UDCA](#udca)\n\nThe runtime plane runs in a Kubernetes cluster running on a\n[supported Kubernetes platform](/apigee/docs/hybrid/v1.3/install-before-begin#supported-platforms) that you maintain.\n\nThe following image shows the primary services that execute on the runtime plane:\n\nFor general information about the runtime components, see the sections that follow. In addition,\nsee [Runtime service configuration overview](/apigee/docs/hybrid/v1.3/service-config).\n\nThe following sections describe each of these primary runtime plane services in more detail.\n\n### Message Processor\n\nHybrid Message Processors (MPs) provide API request processing and policy execution on the\nruntime plane. MPs load all of the deployed proxies, resources, target servers, certificates, and\nkeystores from local storage. You configure an Istio Ingress controller to expose the MPs to\nrequests that come from outside the cluster.\n\n### Synchronizer\n\nThe Synchronizer fetches configuration data about an API environment from the management plane\nand propagates it across the runtime plane. This downloaded data is also called the\n*contract* and is stored on the local file system.\n\nThe Synchronizer periodically polls the Management Server for\nchanges and downloads a new configuration whenever changes are\ndetected. The configuration data is retrieved and stored locally as\na JSON file on the local file system, where the Message Processors can access it.\n\nThe downloaded configuration data allows the runtime plane to\nfunction independently from the management plane. With the contract,\nMessage Processors on the runtime plane use the locally\nstored data as their configuration. If the connection between the\nmanagement and runtime plane goes down, services on the runtime\nplane continue to function.\n\nThe configuration data downloaded by the Synchronizer includes:\n\n- Proxy bundles and shared flow deployments\n- Flow hooks\n- Environment information\n- Shared API resources\n- [Target server\n definitions](/apigee/docs/api-platform/deploy/load-balancing-across-backend-servers)\n- TLS settings\n- Key Value Map (KVM) names\n- [Data masks](/apigee/docs/api-platform/security/data-masking)\n\n### Cassandra datastore\n\n[Apache Cassandra](http://cassandra.apache.org/) is the runtime datastore that provides data persistence for the runtime plane.\n\nCassandra is a distributed data system that provides data persistence on the runtime plane.\nYou deploy the Cassandra database as a [StatefulSet](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/) node pool on your Kubernetes cluster.\nLocating these entities close to the runtime processing services helps support requirements\nfor security and high scalability.\n\nThe Cassandra database stores information about the following entities:\n\n- Key management system (KMS)\n- Key Value Map (KVM)\n- Response cache\n- OAuth\n- Quotas\n\n### Management API for Runtime data (MART)\n\nData that belongs to your organization and is accessed during runtime API calls are\nstored by Cassandra in the runtime plane.\n\nThis data includes:\n\n- Application configurations\n- Key Management System (KMS) data\n- Cache\n- Key Value Maps (KVMs)\n- API products\n- Developer apps\n\nTo access and update that data---for example, to add a\nnew KVM or to remove an environment---you can use the Apigee hybrid UI or the [Apigee APIs](/apigee/docs/reference/apis/apigee/rest). The MART\nserver (Management API for Runtime data) processes the API calls against the runtime\ndatastore.\n\nThis section describes the role that MART plays when you call the Apigee APIs to access the\nruntime datastore.\n\nIt's worth pointing out that both MART and the Message Processors have access to the\nsame runtime datastore (Cassandra), which is how data such as KMS, KVMs, and caches are\nshared.\n\nThe following image shows the flow of an Apigee API call:\n\n### UDCA\n\nThe Universal Data Collection Agent (UDCA) is a service running within the data collection pod\nin the runtime plane that extracts analytics, debug, and deployment status data and sends it to the\nUAP.\n\nFor more information, see [Debug, analytics, and deployment status\ndata collection](/apigee/docs/hybrid/v1.3/other-data-collection).\n\nAbout the management plane\n--------------------------\n\nThe management plane runs on Google Cloud. It includes administrative services such\nas:\n\n- **Apigee hybrid UI:** Provides a UI for developers to create and deploy API proxies, configure policies, create API products, and create developer apps. Administrators can use the Apigee hybrid UI to monitor deployment status.\n- **Apigee APIs:** Provide a programmatic interface for managing your organization and environments.\n- **Unified Analytics Platform (UAP):** Receives and processes analytics and deployment status data from the runtime plane.\n\nThe following image shows the primary services that execute on the management plane:\n\nAbout the Google Cloud services\n-------------------------------\n\nThe following table describes the key Google Cloud services that hybrid leverages:\n\nTypes of users\n--------------\n\nApigee has identified the following primary types of hybrid users:\n\nAdvantages\n----------\n\nApigee hybrid has the following advantages:\n\nIncreased agility\n: Because hybrid is delivered and runs in containers, you can achieve staged rollouts,\n auto-scaling, and other operational benefits of a containerized system.\n\nReduced latency\n: All communication with the hybrid management plane is asynchronous and does not happen as\n part of processing client API requests.\n\nIncreased API adoption\n: Although it is possible to process internal APIs\n using Apigee, the reduced latency and efficiency you can achieve with hybrid makes processing internal\n APIs with hybrid an attractive option. Part of this efficiency is achieved because your API gateway\n runs on-premises, in close proximity to your backend services.\n Also, if you are on Apigee, you can increase your adoption of Apigee by\n processing internal APIs through hybrid.\n\nGreater control\n: Many enterprises are embarking on a hybrid strategy. The ability to\n manage API runtimes deployed in private\n data centers is a key requirement for large enterprises.\n Currently, the hybrid runtime plane can be deployed to Google Cloud\n or in your own data center.\n\nNext step\n---------\n\nSee [the Big Picture](/apigee/docs/hybrid/v1.3/big-picture)---an overview of the hybrid installation\nprocess."]]
