We plan to make Nacos available for production from Nacos 0.8.0. Prior to this release, we recommend that you use it only in development and test environments.

Our current plan is to strive to make Nacos production ready in the 6-8 months. The plan might be adjusted due to various factors, including the priority adjustment according to the voice of the community, but the overall plan is that it should not take longer than one year.

Below are the main roadmaps and plans for the next year.

Nacos 1.0

Main goals:

• Build an easy-to-use, service-related toolset that includes dynamic service discovery, configuration management, service metadata storage and management, push, data consistency, and service&DNS management

• Seamless integration with and support for open-source ecosystems including Spring Cloud , Kubernetes, Dubbo, etc., while at the same time developing a variety of excellent features for large-scale production.
  The following is a rough version plan:

• 0.1 Basic Nacos server and simple OpenAPI and Java SDK;

• 0.2 - 0.3 Seamless support for Kubernetes, Service Mesh and Spring Cloud service discovery and configuration management;
• 0.4 - 0.5 Build an easy-to-use Web UI/User Console;
• 0.6 - 0.7 High availability, ease of use, monitoring and alert etc.;
• 0.8 Production ready;
• 0.9 Large scale performance tuning and benchmark;
• 1.0 GA for large scale production.

Nacos 2.0

Main goal:

Build an open-service platform for unified service management, service sharing and service governance. which can be further divided into two goals.

• Dubbo 4.0 + Nacos 2.0: An Open-Service Platform
  

• Kubernetes + Spring Cloud: Unified Service Management