What’s New in Nacos 2.3.0? A Deep Dive into Its Latest Cloud‑Native Features

Nacos 2.3.0 New Features

1. Anti‑Fragile Plugin

Starting from version 2.2.0, Nacos added an anti‑fragile plugin, which became officially usable in 2.3.0. The Nacos Control Plugin protects the server from large‑scale failures by limiting resource‑intensive requests when usage exceeds defined thresholds. It can be injected via SPI and configured in application.properties, offering flexible extensibility.

2. Server‑Client Capability Negotiation

Previous Nacos versions determined capabilities solely by version numbers, leading to poor readability, maintainability, and extensibility. Version 2.3.0 introduces a negotiation mechanism that lets the server and client exchange supported feature sets, enabling both sides to activate compatible functions and avoid blind trial‑and‑error or unnecessary communication overhead.

3. Config Change Plugin

The Config Change Plugin notifies external systems when configuration changes occur, supporting use cases such as change logging, alerts, auditing, and custom logic before and after updates (e.g., format validation, whitelist checks, webhook notifications). Like the anti‑fragile plugin, it can be injected via SPI and customized by users.

4. Additional New Features

Support for registering or deregistering persistent instances via gRPC.

gRPC connections can use SSL.

Expose client request exception metrics.

Automatically create instance IDs when the client request ID is empty.

More module status and toggle controls in the console.

Enhanced validation for most request parameters.

Support for TOML configuration in the UI.

Batch deregistration of service instances.

Option to disable the console UI and add guide information.

These enhancements make Nacos 2.3.0 the most feature‑rich and resilient release to date, suitable for building robust cloud‑native microservice architectures.