[[["易于理解","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-07。"],[[["\u003cp\u003eThis documentation covers the system architecture of Apigee and Apigee hybrid, focusing on the components created during provisioning and their roles.\u003c/p\u003e\n"],["\u003cp\u003eApigee offers two provisioning options: with VPC peering, which allows communication via network peering between two VPCs, and without VPC peering, which utilizes Private Service Connect (PSC).\u003c/p\u003e\n"],["\u003cp\u003eWhen VPC peering is enabled, a managed instance group (MIG) of virtual machines (VMs) acts as a network bridge to enable bidirectional communication between the customer's VPC and Apigee's VPC, via the global external HTTPS load balancer (XLB).\u003c/p\u003e\n"],["\u003cp\u003eWhen VPC peering is disabled, Private Service Connect (PSC) facilitates private connections between Apigee and target services in other Google Cloud projects, passing requests through either a global or regional load balancer to service attachments.\u003c/p\u003e\n"],["\u003cp\u003eThe API proxy call lifecycle in a peered configuration involves a client app request landing on the XLB, then being routed through a bridge VM to Apigee for processing and then on to the backend service.\u003c/p\u003e\n"]]],[],null,[]]
