Specifications

Dedicated Gateway Specifications

The query per second (QPS) throughput of a dedicated gateway is affected by multiple factors, such as the response size, whether HTTPS access is enabled, and whether gzip compression is enabled. The following table lists the APIG QPS reference values at 30% CPU usage in non-authentication and single node scenarios.

The security watermark enables APIG to maintain high throughput and low latency even when the burst traffic doubles.

**Table 1** QPS Reference
Edition				Basic	Professional	Enterprise	Platinum	Platinum 2
Connection Type	Number of Response Bytes (KB)	Whether to Use HTTPS	Whether to Use gzip	QPS Reference at 30% CPU Usage
Non-persistent connection	1	No	No	3,500	3,600	9,000	55,000	72,000
Non-persistent connection	1	Yes	No	1,000	1,100	2,800	16,000	20,000
Persistent connection	1	No	No	4,500	4,200	13,000	79,000	105,000
	1	Yes	No	4,000	4,000	11,000	67,000	95,000
	10	No	No	3,500	4,000	10,000	67,000	85,000
	10	Yes	No	3,200	3,800	9,500	65,000	80,000

The bandwidth and private network connections vary depending on the gateway edition. Refer to the following table for optimal settings.

**Table 2** Bandwidth and connections
Edition	Bandwidth	Private Network Connections per Second
Basic	Single-AZ: 50 Mbit/s Dual-AZ or more: 100 Mbit/s	1000
Professional	Single-AZ: 100 Mbit/s Dual-AZ or more: 200 Mbit/s	1000
Enterprise	Single-AZ: 200 Mbit/s Dual-AZ or more: 400 Mbit/s	1000
Platinum	Single-AZ: 400 Mbit/s Dual-AZ or more: 800 Mbit/s	1000
Platinum 2	Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s	1000
Platinum 3	Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s	1000
Platinum 4	Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s	1000
Platinum 5	Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s	1000
Platinum 6	Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s	1000
Platinum 7	Single-AZ: 2 Gbit/s Dual-AZ or more: 4 Gbit/s	1000
Platinum 8	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 details about how to modify the specifications of a dedicated gateway, see Modifying Specifications.
Currently, platinum edition 2 and later are available only in CN North-Beijing4, CN East 2, ME-Riyadh, and CN-Hong Kong.

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).

**Table 3** Basic differences between the shared and dedicated API gateways
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.

**Table 4** 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