Specifications
Dedicated Gateway Specifications
The following table lists the specifications of dedicated gateways.
Edition |
Maximum Number of Requests per Second |
Bandwidth |
Private Network Connections per Second |
---|---|---|---|
Basic |
2000 |
Single-AZ: 50 Mbit/s Dual-AZ or more: 100 Mbit/s |
1000 |
Professional |
4000 |
Single-AZ: 100 Mbit/s Dual-AZ or more: 200 Mbit/s |
1000 |
Enterprise |
6000 |
Single-AZ: 200 Mbit/s Dual-AZ or more: 400 Mbit/s |
1000 |
Platinum |
10,000 |
Single-AZ: 400 Mbit/s Dual-AZ or more: 800 Mbit/s |
1000 |
Platinum 2 |
20,000 |
Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s |
1000 |
Platinum 3 |
30,000 |
Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s |
1000 |
Platinum 4 |
40,000 |
Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s |
1000 |
Platinum 5 |
50,000 |
Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s |
1000 |
Platinum 6 |
60,000 |
Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s |
1000 |
Platinum 7 |
70,000 |
Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s |
1000 |
Platinum 8 |
80,000 |
Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s |
1000 |
- Some new features (such as gateway specification modification and circuit breaker policy) are available only in new gateways. If your gateway does not support these features, contact technical support to upgrade it.
- The default API-related quotas of dedicated gateways are the same as those of the shared gateway.
- For dedicated gateways, you can adjust the maximum number of requests per second for each API.
- For details about how to modify the specifications of a dedicated gateway, see Modifying Specifications.
- Currently, platinum edition 2 and later are available in CN-Hong Kong.
- The network, request protocol, response latency, and other factors may cause data differences. The parameter values in dedicated gateway specifications are for reference only. The dedicated gateway specifications are tested under the following conditions:
- Protocol: HTTPS
- Connection type: long connection
- Concurrent requests: 100
- Authentication mode: none
- Size of returned data: 1 KB
- Bandwidth: 10 MB/s
Shared Gateway (Old Console) Specifications
The shared gateway on the old console does not provide any specification settings. View the quotas for creating and using APIs in Notes and Constraints.
The feature of shared gateway on the old console has been removed. Please use dedicated gateways on the new console instead.
Differences Between Dedicated and Shared Gateways
APIG provides a shared gateway and dedicated gateways. You can use the shared gateway right out of the box or purchase dedicated gateways to manage APIs.
Dedicated gateways facilitate decoupling internal systems within an enterprise. Services deployed in VPCs communicate with each other through RESTful APIs with high network security. Dedicated gateways support the deployment of frontend or backend services on public networks, and these services can be accessed using elastic IPs (EIPs).
Dimension |
Shared Gateway |
Dedicated Gateway |
---|---|---|
Billing item |
API calls and public network traffic. |
Specifications and public network egress bandwidth. |
Network access |
APIs are accessed over public networks. |
Gateways run in VPCs. APIs in a VPC are called using the access address of the VPC. You can enable access to API resources in a gateway over public networks or access to resources on public networks through APIs in a gateway. |
Target users |
Small enterprises that have low physical isolation requirements and want to selectively expose API capabilities. |
Large and medium enterprises that want to selectively expose and call internal APIs. Dedicated gateways are deployed in physically isolated clusters with different bandwidths for inbound and outbound access. |
The following table shows the functional differences between the shared and dedicated API gateways.
Category |
Feature |
Shared Gateway |
Dedicated Gateway |
---|---|---|---|
Basic functions |
Refined request throttling |
√ |
√ |
Access control by IP address and account |
√ |
√ |
|
Security authentication |
√ |
√ |
|
API lifecycle management |
√ |
√ |
|
Custom domain names |
√ |
√ |
|
Swagger API import and export |
√ |
√ |
|
VPC channels (load balance channels) |
√ |
√ |
|
API parameter orchestration |
√ |
√ |
|
API group variable management |
√ |
√ |
|
Advanced functions |
Custom authentication |
√ |
√ |
Policy-based routing |
√ |
√ |
|
API monitoring |
√ |
√ |
|
Backend load balancing |
× |
√ |
|
Internal API management |
× |
√ |
|
Access to backend services in private clouds |
× |
√ |
|
Service access through Direct Connect |
× |
√ |
|
Plug-ins |
× |
√ |
|
Log analysis |
× |
√ |
|
Performance indicators |
Physically isolated clusters |
× |
√ |
Different bandwidths for inbound and outbound access |
× |
√ |
|
TPS |
200 |
4000~10000TPS |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot