Comparison Item | Cloud-Native Gateway | Self-Built Gateway |
System building and Ops costs | Resources are fully managed and Ops-free. The node specification, node quantity, and billing mode can be changed, and product editions can be upgraded. Nodes of different business modules are distributed to different cluster groups by business type, and multiple access points (Cloud Load Balancer (CLB)) can be configured. Gateway nodes can be scaled automatically (HPC or HPA) to cope with dynamic traffic changes (supported in the Pro edition). Cloud Native API Gateway can interwork with the Cloud Virtual Machine (CVM) auto scaling group to dynamically scale backend CVM nodes. Terraform or TencentCloud API can be used to build the CI/CD process. | The customer needs to purchase various resources to build the system, and Ops and upgrades are labor-consuming, resulting in high labor costs. |
High availability | Access points (CLB), gateway nodes, and gateway configurations can be deployed across availability zones (AZs), and cross-AZ disaster recovery (DR) is supported for key links. Cloud Native API Gateway supports comprehensive traffic protection and open-source and enhanced throttling, grayscale, circuit breaking, and traffic mirroring. Zero-downtime service deployment is supported. Fault simulation and experiment through Chaotic Fault Generator are supported. | The customer needs to explore and develop a high-availability guarantee system, which has high technical capability requirements for the team. |
Ease of use | Multiple access methods are supported, including the Tencent Cloud console, Ingress, TencentCloud API, and the native console (Konga). You can select the method based on your usage habits. The console provides abundant features, supporting convenient operations related to instances, routes, services, certificates, and plugins. |
The customer needs to build and maintain a large number of components of the observability system, which has high technical requirements for the team.
|
Security | Cloud Native API Gateway can interwork with Tencent Cloud Web Application Firewall (WAF). Cloud Native API Gateway can interwork with Tencent Cloud DDoS Protection. Cloud Native API Gateway supports certificate management by using Tencent Cloud SSL Certificate Service. Cloud Native API Gateway supports commonly used API authentication and authorization and custom authentication. Cloud Native API Gateway supports the IP address blocklist/allowlist for access control. | The customer needs to integrate with relevant cloud products.
The customer needs to configure relevant plugins. |
Observability | Cloud Native API Gateway allows users to view monitoring metrics, such as the number of requests, latency, CPU, memory, bandwidth, and number of connections and configure custom alarms in the console. Cloud Native API Gateway can interwork with Prometheus. You can view gateway request logs and error logs in the console. You can also deliver logs to Tencent Cloud Log Service (CLS) for analysis. | Basic monitoring metrics are supported, and the customer needs to build the alarm system. |
Permission management | Cloud Native API Gateway integrates Cloud Access Management (CAM) to manage gateway resource permissions. The IP address blocklist and allowlist can be configured on access points for access control. | The customer needs to implement resource-level permission control. |
Cloud product integration | Cloud Native API Gateway can access services on Tencent Service Framework (TSF), Tencent Kubernetes Engine (TKE), Serverless Cloud Function (SCF), and CVM. Cloud Native API Gateway can interwork with Tencent Cloud Web Application Firewall (WAF) and Tencent Cloud DDoS Protection for security protection. Cloud Native API Gateway is deeply integrated with CLS, Tencent Cloud Observability Platform (TCOP), Tencent Cloud SSL Certificate Service, and Chaotic Fault Generator. | Not supported |
フィードバック