Cloud Native 13 min read

Nacos Hits 30K Stars: Roadmap, New Features, and Future Cloud‑Native Vision

Celebrating Nacos reaching 30,000 stars, this article reviews the past two years of version upgrades, plugin and security enhancements, the revamped website, expanding multi‑language SDKs, and outlines the ambitious goals for Nacos 3.0 to become more secure, versatile, and cloud‑native.

Alibaba Cloud Native
Alibaba Cloud Native
Alibaba Cloud Native
Nacos Hits 30K Stars: Roadmap, New Features, and Future Cloud‑Native Vision

Version Evolution 2.0 → 2.4

From 2.0.4 to 2.4.2, Nacos addressed the performance bottlenecks of the 1.x architecture, added extensibility points, and improved usability and security.

Plugin Capability

Since 2.0.x the client and server fixed gRPC issues and introduced a SPI‑based plugin framework. Users can develop custom authentication, encryption, and data‑source plugins by implementing SPI interfaces and adding JARs, which decouples core logic from extensions.

Released plugins include:

Authentication

Configuration encryption

Data‑source adapters

Change‑tracking

Rate limiting

Configuration‑change hooks

Security and Usability Improvements

Default authentication plugins were refactored: hard‑coded tokens, admin passwords and related key‑values were removed. The console now displays the authentication status and prompts users to enable it. Full‑link TLS is provided for client‑server and server‑server communication.

Usability upgrades:

Batch service registration

Incremental service‑subscription notifications

Native Prometheus Service Discovery protocol support

Multi‑Language SDKs and Ecosystem

Go SDK reached feature parity with the Java SDK in version 2.0.0 (Feb 2022) and has been stable for two years.

Python SDK released a stable 1.0.0 version and is being updated for 2.x compatibility.

Rust SDK (r‑nacos) is at version 0.4.2, providing a lightweight server implementation for resource‑constrained environments.

Additional ecosystem projects:

r‑nacos – Rust‑based Nacos server (0.5.23)

nginx‑nacos‑upstream – dynamic Nacos‑driven configuration for Nginx

Future Outlook: Nacos 3.0

More Secure

Plans include upgrading the default authentication plugin, redesigning APIs (Console, Client, Admin, Inner) with tailored authentication, and separating the console from the engine to allow independent deployment and port configuration.

More Versatile

New features will add distributed lock support, group‑based configuration and service subscription, and explore AI‑driven use cases such as dynamic prompts and training‑task scheduling.

More Cloud‑Native

Roadmap targets native XDS protocol support without Istio, bi‑directional synchronization with Kubernetes, ServiceMesh integration, and a lightweight Nacos Sidecar for zero‑intrusion service registration.

Quality System Revamp

The testing framework (including nacos‑e2e) will be scaled: more unit tests, expanded e2e pipelines, and a restructured integration‑testing process to maintain release quality.

Relevant Repositories

https://github.com/nacos-group/nacos-plugin
https://github.com/nacos-group/nacos-sdk-go
https://github.com/nacos-group/nacos-sdk-python
https://github.com/nacos-group/nacos-sdk-rust
https://github.com/nacos-group/r-nacos?tab=readme-ov-file
https://github.com/nacos-group/nginx-nacos-upstream
https://github.com/nacos-group/nacos-e2e
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

service discoveryNacosopen sourceRoadmap
Alibaba Cloud Native
Written by

Alibaba Cloud Native

We publish cloud-native tech news, curate in-depth content, host regular events and live streams, and share Alibaba product and user case studies. Join us to explore and share the cloud-native insights you need.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.