All Products
Search
Document Center

Microservices Engine:Nacos Enterprise Edition capacity specifications

Last Updated:Dec 16, 2025

MSE Nacos Enterprise Edition supports a 99.99% Service-Level Agreement (SLA) and improves service push performance by 300% compared to a self-managed open source Nacos instance. It offers higher quota capabilities using dedicated underlying core resources. This topic describes the capacity thresholds and provides queries per second (QPS) performance references for different specifications of Nacos Enterprise Edition.

Version overview

Support for dynamic MCP registration

Nacos Enterprise Edition is compatible with the Mesh Configuration Protocol (MCP) used in open source Nacos 3.0. It provides comprehensive capabilities for dynamic service registration, protocol transform, and real-time optimization to support the upgrade requirements of AI agents and microservices models.

  • Unified service management: You can dynamically register MCP services through an SDK or the console. This standardizes service discovery and enables visual configuration.

  • Fast protocol migration: You can convert existing HTTP services to MCP services with a single click. You can also define protocol mapping rules using JSON templates to quickly integrate with the MCP ecosystem.

  • Real-time optimization: You can dynamically update MCP tool descriptions in the console. This optimizes AI agent call performance and improves developer efficiency without requiring code modifications.

Enterprise-grade stability: 99.99% SLA guarantee

MSE Nacos Enterprise Edition provides enterprise-grade stability and guarantees 99.99% availability with its Service-Level Agreement (SLA) using dedicated underlying core resources.

  • High availability (HA) architecture: This architecture is suitable for industries with high business continuity requirements, such as finance, energy, and state-owned enterprises. It ensures that your business runs without interruption throughout the year.

  • Resilience: The system remains efficient and stable during traffic peaks or in complex operational scenarios. This capability supports the continuous operation of critical business applications.

  • Resource isolation: This feature prevents contention for shared resources and significantly reduces the risk of failures.

Enhanced security: Unified data source management

The Enterprise Edition provides end-to-end encrypted data source management. It integrates with the Key Management Service (KMS) credential service to enable dynamic key rotation and zero-configuration access for mainstream databases, such as RDS, Redis, and PolarDB.

  • Key hosting and automatic rotation:

    • The service integrates with KMS to encrypt and store account credentials and rotate them on a schedule. This process eliminates the threat of plaintext credential exposure.

    • When a key changes, the system automatically synchronizes and applies the updated configuration without manual intervention.

  • Seamless application-side access: You can access data sources through configuration without modifying your code. Seamless key rotation is supported at runtime.

  • End-to-end encryption: Data source configuration is encrypted in transit and at rest to ensure the security of sensitive information.

Capacity thresholds

  • Connection assessment: This is the number of connections established between Nacos clients and the Nacos server. In a typical scenario, one pod establishes one connection. However, if you use both the service registry and the configuration center, two connections are required.

  • Level assessment: For core business applications, keep capacity metrics below the safe level. This practice ensures high stability even during sudden traffic bursts. If the QPS or Transaction Per Second (TPS) exceeds the alert level, traffic bursts may threaten stability. You should also keep capacity metrics below the safe level when you restart or upgrade a cluster.

  • Assessment standard: To ensure stability, the following capacity assessments are based on client version 1.x. For better performance, we recommend that you upgrade your client to version 2.x.

The following table shows the capacity metrics for a 3-node cluster.

To estimate the capacity of clusters with a different node count, you can proportionally scale the data from a 3-node cluster of the same specification.

Specification

Number of nodes

Connections

Queries per second (QPS)

Transactions per second (TPS)

Safe level

Alert level

Safe level

Alert level

Safe level

Alert level

Small.Platinum.x2

3

1200

1800

1200

1800

600

900

Medium.Platinum.x1

3

2400

3600

2400

3600

1200

1800

Medium.Platinum.x2

3

4800

7200

4800

7200

2400

3600

Large.Platinum.x1

3

9600

14400

9600

14400

4800

7200

Antifragility throttling

To ensure stability, MSE Nacos Enterprise Edition enables antifragility mode by default. When the resource capacity or API traffic reaches a threshold, the system automatically applies throttling and capacity controls. The following table shows the throttling rules for a single node.

To determine the throttling rules for a multi-node cluster, you can proportionally scale the data from a single node.

Specification

Connections

Publications of the same configuration (times/minute)

Configuration publications (TPS)

Configuration queries (QPS)

Service pushes (TPS)

Small.Platinum.x2

800

20

100

200

800

Medium.Platinum.x1

1600

20

100

400

1600

Medium.Platinum.x2

3200

20

100

800

3200

Large.Platinum.x1

6400

20

100

1600

6400