DOCSEARCHbyAlgolia
Submit Docs

Nacos Documentation

website·Indexed 35 days ago

https://nacos.io/

Documentation for Nacos, featuring guides on deployment, cluster mode, and integration with Spring Boot, Spring Cloud, Dubbo, and Kubernetes. Includes technical details for version 1.X, 2.X, and the unreleased Next version, covering SDKs, management APIs, and system configurations.

Tokens
3M
Snippets
11.3K
Records
20.2K
Agent score
60%

What's inside Nacos

  1. Overview of AgentScope Framework

    AgentScope is an AI Agent development framework designed to provide a balance between the autonomous planning/dynamic decision-making of LLMs and the stability/controllability of structured design. It is available for both Python and Java developers, with the Java version integrated into Spring AI Alibaba as a native, auto-configured Agent framework.

  2. Overview of Nacos Service Infrastructure

    Nacos is a service infrastructure designed for modern application architectures, such as microservices and cloud-native paradigms. It provides a set of features to help developers implement dynamic service discovery, service configuration, service metadata management, and traffic management, enabling more agile construction, delivery, and management of microservice platforms.

  3. Overview of Nacos Control Plugin anti-fragility

    v2

    Starting from version 2.3.0, Nacos uses a Control Plugin system based on SPI to implement anti-fragility strategies. This protects the server from resource exhaustion by restricting access based on frequency and volume. The system is built around two primary concepts:

    1. Control Points: Mappings of server resources. Currently, these include:
      • Connections: Monitors long connections (Nacos 2.X clients) and long polling connections (Nacos 1.X clients) independently.
      • Transactions Per Second (TPS): Monitors access frequency to core interfaces. Similar interfaces (e.g., registration v1 and v2) are grouped as the same monitor point.
    2. Control Rules: Limitation rules applied to control points, categorized as ConnectionControlRule and TpsControlRule.

  4. Overview of Nacos capabilities

    v2.3

    Nacos (Dynamic Naming and Configuration Service) is a cloud-native platform designed for microservice infrastructure. It provides four primary capabilities:

    1. Service Discovery and Health Monitoring: Supports discovery via DNS and RPC. Providers register via SDK, OpenAPI, or Agent. It includes real-time health checks at the transport layer (PING/TCP) and application layer (HTTP, MySQL, user-defined), with support for agent reporting and server-side active detection.
    2. Dynamic Configuration Service: Provides centralized, externalized management of application configurations. This eliminates the need for redeployment during config changes and supports version tracking, Canary releases, one-click rollback, and client update status tracking via a management UI.
    3. Dynamic DNS Service: Enables weighted routing, middle-tier load balancing, and DNS-based service discovery to reduce vendor lock-in. It provides APIs for managing service-associated domains and IP lists.
    4. Service and Metadata Management: Centralizes management of service descriptions, lifecycles, static dependency analysis, routing policies, security strategies, SLAs, and metrics.

  5. Overview of Nacos Distro Protocol

    The Distro protocol is a custom AP (Availability and Partition tolerance) distributed protocol developed by the Nacos community specifically for handling ephemeral (non-persistent) service instances. It ensures that the system remains operational even if some Nacos nodes fail, providing coordinated storage and consistency for hundreds of thousands of service instances across a cluster.

  6. Overview of Nacos Track Tracing Plugins

    v2.4

    Since version 2.2.0, Nacos supports track tracing plugins via SPI (Service Provider Interface). These plugins allow developers to subscribe to and process internal Nacos operation events (e.g., service registration, de-registration, status changes) for logging or storage purposes.

    Note: This is distinct from distributed tracing (like Zipkin or SkyWalking) used for micro-service request tracking; it is specifically for tracing Nacos-related administrative and lifecycle operations. The plugin API is currently in beta and may change in future versions.

  7. Overview of Nacos Config Change Plugins

    v2.4
    Starting from Nacos 2.3.0, the Config Change Plugin system allows users to inject custom logic using SPI to handle configuration changes. Unlike client-side subscriptions, these plugins can perform pre-change operations (e.g., format validation, whitelist checks) or post-change operations (e.g., auditing, webhooks). The system uses an AOP-like design with 'PointCuts' (the event) and 'Execute Types' (when the plugin runs).

  8. Overview of Nacos Capabilities

    v3.1
    Nacos (Dynamic Naming and Configuration Service) is a platform designed for cloud-native applications to handle dynamic service discovery, configuration management, and service management. It supports various service types including Kubernetes Services, gRPC, Dubbo RPC, and Spring Cloud RESTful services.

  9. Overview of Nacos Trace Tracking Plugins

    v2.3
    Starting from version 2.2.0, Nacos supports trace tracking implementation plugins via the SPI (Service Provider Interface) mechanism. Unlike distributed tracing for inter-service communication, Nacos trace tracking focuses on monitoring internal Nacos operations such as service registration, de-registration, pushes, and status changes. Plugins can subscribe to these events to perform actions like logging or storage.

  10. Overview of Nacos MCP Router

    Nacos MCP Router is a standard MCP Server built on the official MCP SDK. It simplifies MCP service usage by providing intelligent search, installation, and proxy capabilities. When integrated with Nacos MCP Registry, it supports MCP Server governance, including version management and tool visibility.

  11. Overview of Nacos Maintainer SDK

    The Nacos Maintainer SDK (Nacos-Maintainer-SDK) is a Java-based SDK designed for administrative operations across the Nacos Config Center, Naming Service, and distributed locks. It is intended for Nacos operators or specialized applications (such as gateway or console applications) that require high-privilege access to perform large-scale data retrieval and management. For standard application usage, the Nacos Client (Java or Go) should be used instead. The SDK is based on the Nacos Admin API.

  12. Overview of Nacos Configuration Change Plugins

    v2.3
    Starting from version 2.3.0, Nacos supports injecting configuration change plugins via SPI. This allows developers to implement custom logic—such as format validation, whitelist checks, and webhooks—that triggers before or after configuration changes (creation, update, deletion). This replaces the previous method of mimicking client subscriptions, which only supported post-change actions and required individual configuration monitoring.