Dimension | Tencent Cloud Gateway Solution | Customer-Owned Gateway Solution |
Cloud backend | Tencent central data center (console / quota / billing). | Tencent central data center (console / quota / billing). |
Control plane | Tencent controller (cross-AZ). | The Tencent controller is deployed across AZs. Communication between the controller and the gateway traverses the public network using mTLS. |
Forwarding plane (accelerated gateway) | Deployed in Tencent Cloud IDC, with cross-AZ / multi-region active-active capability. | Privately deployed in the customer's IDC data center. |
Origin path | Private network back-to-origin (origin server in Tencent Cloud) / public network back-to-origin (origin server in customer data center). | 100% of traffic is sourced via the private network, and forwarding traffic does not leave the customer's IDC. |
Ops responsibility | Tencent is responsible for the deployment, upgrade, scaling, and hardware of the acceleration gateway. | The acceleration gateway is managed by the Tencent controller. The customer is responsible for the hardware/IDC. The customer performs software deployment/upgrades, and Tencent provides the materials. |
Cross-AZ high availability | Natively supported (by Tencent Cloud infrastructure). | The customer's solution achieves equivalent high availability after multiple clusters are deployed across multiple AZs. |
Cluster scheduling logic | The Tencent controller performs unified scheduling. | It is completely consistent with the Tencent Cloud gateway. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback