Edition | Open source Nacos version | MSE Nacos version | Description |
Professional Edition or Developer Edition | 2.2.3 | 2.2.3.1 | Disables the open source console by default. Supports the RAM AccessKey whitelist feature. Supports the Eureka incremental data protocol. Optimizes the check logic during an engine upgrade or restart. Supports graceful engine change. Improves the stability during an engine upgrade or restart. Optimizes the logic for obtaining source IP addresses to improve the accuracy for obtaining source IP addresses. Optimizes the throttling capability of instances to support more throttling features and improve engine stability. Optimizes the logic for checking request parameters. Identifies error content of parameters. Improves the performance of the Eureka module. Fixes the following issue: When forced empty list protection is not enabled, the client in a version later than V2.2 cannot receive an empty service list. Fixes the following issue: The number of service providers is incorrectly counted when a large number of service providers are registered with an instance at the same time. Fixes the following issue: The limit on the number of configurations does not take effect in V2.2.3.0. Fixes the following issue: Data is not pushed when a single xDS or Mesh Configuration Protocol (MCP) connection encounters an error.
|
2.2.3.0 | Synchronizes kernel features of open source version V2.2.3. For example, the logon page in the open source console remains unchanged if you disable authentication. Allows you to view the registered services, subscribed services, and listener configurations on the client versions that pose risks. Optimizes the authentication-related prompt in the open source console. Optimizes the logic for monitoring the push success rate. This optimization allows you to ignore expected triggering of empty list protection and prevents the decrease of the push success rate when empty list protection is triggered.
|
2.1.2 | 2.1.2.2 | Optimizes the logic for clearing expired metadata of application instances that are registered with Nacos instances. This optimization allows you to immediately clear the metadata that is modified when the application instance does not exist. Uses the automatic switching of running modes and accelerates the speed of automatic doublewrite stopping. This shortens the period in which the system is in the transitory state and inconsistent data exists. Allows underscores (_) to be contained in the name specified by the clusterName parameter of Nacos instances. Allows you to view push tracks after the information is successfully pushed to the Nacos SDK for Go. Fixes the following issue: When a client is disconnected from a Nacos instance and an application is registered with the Nacos instance at the same time, data cannot be queried with a low probability. Fixes the following issue: When a resource involved in authentication is configured at the dataId level, the status code 403 is returned for the listener configuration of the client.
|
2.1.2.1 | Allows you to use the service registration and discovery features of Nacos instances for Java applications for which Microservices Governance is enabled. Code changes are not required for the Java applications. Supports encrypted communications between a Nacos server and a Nacos client.
|
2.1.2.0 | |
2.1.0 | 2.1.0.2 | Optimizes the logic for empty list protection, and narrows down the range within which empty list protection takes effect. Empty list protection is triggered only when necessary. Fixes the following issue: The status code 500 is always returned after the engine calls an API operation. Fixes the following issue: Horizontal notifications and Distro notifications fail during scale-in. Fixes the following issue: The configuration obtained by the AES-256 algorithm is ciphertext when the Nacos 2.x client reads encrypted configurations. Fixes the following issue: Invalid data is released with a low probability when data is sent to a cloud-native gateway. Fixes the following issue: Garbled characters appear in configurations in Chinese that you obtained by using ACM-Node.js-SDK.
|
2.1.0.1 | Optimizes the empty list protection mechanism in scenarios in which Dubbo applications subscribe to provider registration information from multiple registries. This optimization helps prevent the Nacos client from generating a large number of invalid logs related to empty list protection. Optimizes the push task model to improve service stability when a large number of push tasks are implemented at the same time. Fixes the following issue: out-date.is frequently logged on the Nacos client.
|
2.1.0.0 | Supports the empty list protection capability and provides higher availability in the Professional Edition. For more information, see Empty list protection. Optimizes the long polling mechanism that is used to monitor configuration changes and improves the read performance of the configuration management service by about 100%.
|
2.0.4 | 2.0.4.0 | Supports Dragonwell and improves service performance in the Professional Edition. Supports registry authentication. Supports the control policy feature provided by the Resource Directory service of Resource Access Management (RAM). Fixes the following issue: The connections between nodes may be disconnected and not reconnected when these nodes are started at the same time. Fixes the following issue: The encryption algorithm may be invalid when you import the encrypted configuration to the MSE Nacos instance.
|
2.0.3 | 2.0.3.2 | Fixes the following issue: The Address Server fails to be initialized occasionally. Fixes the following issue: Application nodes are always in the Restore state after you enable configuration authentication for the application.
|
2.0.3.1 | Improves compatibility with the Diamond protocol supported by Application Configuration Management, supports the Application Configuration Management client, and allows you to perform configuration operations based on the Diamond protocol. Fixes the following issue: After configurations are changed, the displayed configuration change time is inconsistent with the actual configuration change time. Fixes the following issue: You cannot redirect from the open source Nacos console to the MSE console after you enter {address}:8848/nacos in the open source Nacos console. Fixes the following issue: Garbled characters appear in the open source Nacos console when you release configurations in Chinese in the console. Fixes the following issue: The number of service providers is invalid when the SDK for Go fails to pull data for the first time and stops retrying or the retry status is abnormal. Fixes the following issue: Log information is frequently displayed for the MSE Nacos instance that is compatible with the Eureka protocol. Fixes the following issue: Garbled characters appear when you release configurations in Chinese by using the Nacos SDK for Node.js. Fixes the following issue: The Address Server module in standalone mode does not take effect.
|
2.0.3.0 | Provides compatibility with the Diamond protocol supported by Application Configuration Management. This compatibility allows you to seamlessly migrate configurations from Application Configuration Management to this Nacos version. Improves the stability of import or export of encrypted configurations. Allows you to export configurations from Application Configuration Management and import the configurations to the configuration management service of the MSE Nacos engine.
|
2.0.1 | 2.0.1.1 | Optimizes the logic of database queries to reduce the negative impact of unstable database performance on the servers. Fixes the following issue: Frontend cannot display the instance changes that are caused when the MSE console goes online or offline or the weight is changed. Fixes the following issue: When the Nacos 1.X client is used, expired metadata of a Nacos instance is not deleted after the instance is shut down. Fixes the following issue: A cloud-native gateway cannot identify changes if a Nacos instance is shut down or the weight is changed.
|
2.0.1.0 | Supports Java Client 0.8. Optimizes the performance of MCP and xDS. Improves the stability of service data pushes. Fixes the following issue: The namespace page displays invalid maximum values of configurations. Fixes the following issue: You may fail to add nodes to a Nacos instance when you scale out the instance.
|
2.0.0 | 2.0.0.0 | Supports Nacos registries and configuration centers based on gRPC. Provides Nacos performance that is approximately ten times higher than the Basic Edition. Provides a comprehensive authentication system and a comprehensive encryption and decryption system.
|
Basic Edition
Important The Basic Edition is discontinued. If you are using the Basic Edition, we recommend that you upgrade the Basic Edition to the Professional Edition at the earliest opportunity. For more information, see Upgrade the engine version. | 1.2.1 | 1.2.1.3 | Supports the control policy feature provided by the Resource Directory service of RAM. Optimizes the use of thread pools and supports dynamic adjustment of the thread pools. Fixes the following issue: The service subscribers that are obtained from specific queries are invalid.
|
1.2.1.2 | Optimizes database dependencies to reduce the negative impact of unstable database performance on Nacos responses to requests. Fixes the following issue: You cannot import the configurations that are exported from Application Configuration Management to the Nacos engine.
|
1.2.1.1 | |
1.2.1.0 | Supports Nacos registries and configuration centers based on HTTP connections. |
1.1.3 (End of maintenance. We recommend that you upgrade Nacos 1.1.3 to a later version at the earliest opportunity.) | Supports Nacos registries based on HTTP connections. |
indicates that this feature is supported, and 
indicates that this feature is not supported.