How to Upgrade to Nacos‑Spring‑Boot 0.2.10 and Unlock 10× Performance with gRPC

With Nacos 2.0 now stable, Nacos‑spring‑boot has released two core versions, 0.1.10 and 0.2.10, which fully support Nacos 2.0, add automatic configuration‑type detection, and fix data‑consistency issues under high concurrency.

Existing Nacos‑spring‑boot users can upgrade by replacing the Maven dependency as follows:

<dependency>
  <groupId>com.alibaba.boot</groupId>
  <artifactId>nacos-config-spring-boot-starter</artifactId>
  <version>0.2.10</version>
</dependency>

The article introduces the enhanced capabilities of the new version and demonstrates a production‑environment configuration‑management project, showing how the 0.2.10 release delivers up to ten‑fold performance improvement thanks to long‑connection support.

Nacos‑spring‑boot New Version Features

Full Compatibility with Nacos 2.x and Migration to Long‑Connection Era

In Nacos 1, configuration subscription and real‑time push relied on long‑polling over HTTP, which caused latency issues. Nacos 2 rebuilds the subscription and push mechanisms using gRPC long connections, ensuring real‑time configuration refresh and has been proven in many production environments.

Automatic Detection of Configuration File Type

The new version can automatically identify the file type (json, yaml, properties) of a configuration even when the user does not specify it, reducing the risk of processing errors caused by mismatched file types.

@NacosValue Annotation Fully Supports SpEL Expressions

SpEL (Spring Expression Language) allows dynamic string construction. Users can now define @NacosValue with SpEL, seamlessly integrating with Spring Boot and reducing boilerplate.

Fixed Consistency Issues in High‑Concurrency Scenarios

During large‑scale stress tests, some clients fetched stale configuration versions, causing repeated configuration reads. The new version adds intelligent locks and upgrades the Nacos‑spring dependency to eliminate potential thread‑safety risks.

Production Demo – Client Deployment

Spring Boot users can upgrade by adding (or updating) the following dependency in pom.xml:

<dependency>
    <groupId>com.alibaba.boot</groupId>
    <artifactId>nacos-config-spring-boot-starter</artifactId>
    <version>0.2.10</version>
</dependency>

Note: Use version 0.2.10 for Spring Boot 2.x and 0.1.10 for Spring Boot 1.x.

Configure Connection Information in application.properties

nacos.config.server-addr=${nacos_server_address}:8848

${nacos_server_address}

is a placeholder for the Nacos server address, which will be provided later.

Load a dataId with @NacosPropertySource and Enable Auto‑Refresh

@SpringBootApplication
@NacosPropertySource(dataId = "com.alibaba.nacos.example.properties", autoRefreshed = true)
public class NacosConfigApplication {
    public static void main(String[] args) {
        SpringApplication.run(NacosConfigApplication.class, args);
    }
}

Use @NacosValue to Inject Property Values

@Controller
@RequestMapping("config")
public class ConfigController {
    @NacosValue(value = "${connectTimeoutInMills:5000}", autoRefreshed = true)
    private int connectTimeoutInMills;

    @RequestMapping(value = "/get", method = GET)
    @ResponseBody
    public int get() {
        return connectTimeoutInMills;
    }
}

Production Demo – Server Deployment

Two deployment options are available for Spring Boot users: self‑hosted open‑source Nacos or Alibaba Cloud MSE Nacos Professional Edition.

Self‑Hosted Open‑Source Nacos

Users can deploy, operate, and tune the open‑source Nacos cluster on Windows, macOS, or Linux. The project is licensed under Apache 2.0, allowing custom extensions.

MSE Nacos Professional Edition

The professional edition offers automated upgrades, 99.95% high‑availability, 10× performance improvement via long connections, enhanced configuration encryption, and integrated RAM permission control.

Steps to provision MSE Nacos:

Visit the MSE official website and log in.

Click “Buy Now” and “Create Instance”.

Select the “Professional Edition” and configure the required settings.

Confirm the purchase and wait a few minutes for the cluster to be ready.

Copy the internal or public address and replace ${nacos_server_address} in the client configuration.

Enter the instance console, go to “Configuration List”, and create a new configuration matching the client’s dataId.

Publish the configuration and optionally enable encryption.

Result Verification

Start the client application locally and run: curl localhost:8080/config/get If the response shows 3000 , the SDK works correctly.

In the MSE console, modify the configuration com.alibaba.nacos.example.properties to:

connectTimeoutInMills=6000

When the console prints the updated value, the automatic configuration refresh is confirmed, and the application has entered the high‑performance configuration‑center era.