This topic describes the limits on the use of Microservices Engine (MSE). Before you use MSE, you must take note of the limits on the use of Microservices Registry, Microservices Governance, and cloud-native gateways provided by MSE.
Microservices Registry
Item | Requirement |
Limits on the maximum number of namespaces on a Nacos instance | 50 |
Limits on the maximum number of configuration files on a Nacos instance | 10,000 |
Limits on the maximum size of a configuration file on a Nacos instance |
|
Limits on the maximum number of ephemeral nodes created for a single session on a ZooKeeper instance | 2,000 |
Microservices Governance
The following limits are imposed only on Microservices Governance.
Item | Requirement |
Microservice frameworks |
For more information about supported components, see Component support for the end-to-end canary release feature. |
Access applications | Applications deployed in Container Service for Kubernetes (ACK) clusters, Elastic Compute Service (ECS) instances, or Serverless App Engine (SAE). |
Java Development Kit (JDK) versions of Java applications | JDK 1.6, 1.7, 1.8, 11, and 17. |
Maximum number of access resources (interfaces) | Maximum number of access resources (interfaces) for an application: 1,600. |
Cloud-native gateways
Item | Requirement |
Regions that support TLS hardware acceleration | Due to limits on the underlying hardware, TLS hardware acceleration is supported only in the following regions:
|
Regions that support WAF 3.0 integration | Cloud-native gateways can be connected to Web Application Firewall (WAF) 2.0 by using traditional methods such as CNAME records. However, WAF 3.0 is required for integration with cloud-native gateways. WAF 3.0 integration is supported only in the following regions:
|
Regions that support Plug-in Marketplace | Plug-in Marketplace is supported only in the following regions. If you have requirements for plug-ins, submit a ticket.
|