What’s New in Nacos 3.0? Key Features, AI Integration, and Cloud‑Native Enhancements

In modern micro‑service architectures, Nacos serves as a dynamic naming and configuration platform, providing service discovery, configuration management, and governance capabilities that are essential for building stable, high‑availability cloud‑native applications.

JDK and Spring Boot Version Upgrade

Nacos 3.0 drops support for JDK 8, upgrading its runtime to JDK 17 and its Spring Boot version to 3.4.1, which brings higher performance, stronger security, and full access to the latest language and framework features.

Enhanced Admin API

A brand‑new Admin API is introduced to simplify operational management and enable independent console deployments, with a maintainer SDK planned to further ease API usage.

Default Authentication Enabled

For security reasons, authentication is now enabled by default for the Admin API, Console API, and Inner API, requiring additional configuration on first deployment and helping prevent unauthorized access.

Embracing AI – MCP

Nacos 3.0 proactively adds the Model Content Protocol (MCP), a dedicated protocol for managing and interacting with AI models and related content.

Unified Empty and Public Namespace

The handling of empty and public namespaces is unified, simplifying the namespace concept and providing a more consistent experience for resource isolation.

Distributed Lock (Beta Feature)

A beta distributed‑lock capability is added, offering mutual exclusion across distributed processes to ensure data consistency and avoid resource contention.

Fuzzy Listening for Services and Configurations (Beta)

Pattern‑based (fuzzy) listening allows users to monitor services or configurations by prefix or pattern, such as all services starting with “order‑” or all configs belonging to the “database” group, making management more flexible.

Direct Support for xDS Protocol

The GA version of Nacos 3.0 directly supports the xDS protocol suite (EDS, LDS, RDS, CDS), facilitating seamless integration with service‑mesh ecosystems like Istio.