Author | Alibaba middleware team
Edit | Xiaozhi
contributed Dubbo ecosystem, Alibaba Nacos released v0.1.0 versionAt the Dubbo Developer Salon of the Shanghai Station of Aliware Technology Station in June, Alibaba senior technical expert Guo Ping (Kun Yu), announced a new open source project of Alibaba, Nacos, and released the first version in a low-key morning last Friday (July 20).
Kunyu introduced the original intention of this open source project in the last offline event. He said, "The service discovery, configuration and service management platform used by Alibaba in the construction of a shared service system will be contributed to the open source community through the Nacos project. By creating a classic combination of Dubbo + Nacos, Dubbo's power in the cloud-native and Service Mesh era, in the era of cloud-native and Service Mesh, it has been very concerned about the seamless docking and support of mainstream open source communities, such as Spring Cloud and Kubernetes cloud-native systems."
The current plan for this project is to continue to work in the next 6 to 8 months. Version 0.8 of release begins to reach production availability. At the same time, it plans to adhere to community development. It plans to absorb at least 10 external Committers and 5 external PMC in the next year. What is Nacos /nɑ:kəʊs/?
Nacos is Alibaba's new open source project. Nacos released the v0.1.0 version and also released a Chinese and English official website. Judging from its official website description, its core positioning is "a dynamic service discovery, configuration and service management platform that is easier to help build cloud-native applications."
Nacos has three main functions:
Service discovery and service management
Dynamic service discovery is crucial when using modern application architectures such as microservices and cloud-native methods centered on "Services" and are centered on "Services" and dynamic service discovery is crucial. Nacos supports both DNS-based and RPC-based service discovery (such as Dubbo/gRPC) and provides you with real-time health checks for services to prevent sending requests to unhealthy hosts. Based on Nacos, you can also implement service circuit breakers more conveniently. Nacos provides powerful services such as metadata management, routing and traffic management strategies to help you better build a stronger microservice platform.
Dynamic Configuration Management
Dynamic configuration service allows you to manage the configuration of all applications or services in a centralized and dynamic manner across all environments. Dynamic configuration eliminates the need to redeploy applications and services when configuration updates. It can more conveniently help you realize stateless services and more easily achieve on-demand flexible scaling service instances.
Dynamic DNS service
supports dynamic DNS service that supports weight routing. It makes it easier for you to implement intermediate-tier load balancing, flexible routing policies, traffic control and simple DNS resolution services in production environments within the data center. Dynamic DNS services also help you to implement DNS protocol-based service discovery more easily to eliminate the risks coupled to the vendor's private service discovery API.
Why is open source? NacosWhy did Alibaba choose such a point of time to open source? Nacos, what are the thoughts behind it? In earlier offline technology activities, @Kunyu also gave a detailed interpretation. Kunyu said that it is mainly based on the following points:
Distributed infrastructure centered around Service is becoming more and more important
The world is getting faster, and the pace of innovation and market competition is becoming increasingly fierce. How to achieve business growth super fast has become the main theme of commercial competition. Shared bicycles have become popular all over the country almost overnight. In less than a few years, Didi has changed our taxi-hailing method. Tencent has three shifts to achieve "chicken eating" for the whole people. Now the valuation of enterprises is from 0 to 100 The time required for 100 million is getting shorter and shorter, while the average life expectancy of enterprises has dropped from 60 years in the 1960s to 15 years today, and everything indicates that the speed and intensity of innovation and competition are increasing.
On the other hand, the agility and effectiveness of technical infrastructure account for an increasingly large proportion of the factors of business success. The changes in cloud computing in resource and service delivery models have brought about revolutionary improvements in efficiency and more agile infrastructure (starting up no longer has to buy machines and find computer room hosting, from the previous six-year preparation cycle to now creating a full set of services in the hourly level of the cloud). At the application architecture level, the flexibility, resilience, rapid combination and aggregation of atomic services brought by the microservice architecture model brings innovation, providing conditions for rapid innovation and trial and error in business, and has been proven by more and more application platforms. The more agile technology infrastructure provides a foundation for agility of business and competitive advantages of business.
Today, whether it is cloud computing, microservices or cloud native centered around Kubernetes, they emphasize the application architecture model with "service" as the core. If we were discussing "everything is an object" 15 years ago, then today we are talking about "everything is a service". Taobao's service-oriented transformation 10 years ago followed this trend, and microservice architecture ideas also followed this trend 8 years ago. Today, various distributed infrastructures for "services" are becoming more and more important. Based on Alibaba's 10 years of service-oriented development experience, are the existing open source solutions in the field of large-scale service discovery, service governance and service sharing? Based on Alibaba's production experience over the years of service-oriented production, we don't think so.
Alibaba's experience in the construction of "shared service system" can be reused on a large scale in various industries
Alibaba's middle-end concept and system, which is completely in line with the "Tao" of cloud native, that is, "thick technology platform, thin application" supports rapid innovation and trial and error of business, thereby winning the market. The middle-end system advocates a dual-engine architecture, skipping "big data", but looking at the business middle-end is a large shared service platform centered on "service". Online services accumulate business data and synchronize to the big data platform to calculate and mine. The big data platform guides business and service innovation through data feedback, and supports a service registration and service governance platform that can be accumulated and shared "service" systems is one of the key elements of this system.
"Service governance, service precipitation, service sharing and sustainable development of services" is the core value proposition of the "shared service system"
supports innovation from small seedlings to towering trees, and the service platform continues to evolve. All of this requires the support of a strong service platform and service infrastructure.
Alibaba will create a service discovery, service and traffic management, and service sharing platform through Dubbo + Nacos and a series of open source projects.
Nacos and the mainstream open source ecosystem Nacos will not be a closed system. In addition to the support for Alibaba's open source ecosystem such as Dubbo, it also emphasizes the integration into other open source ecosystems. This includes Java's microservice ecosystem Spring Cloud, Kubernetes/CNCF cloud-native ecosystem, as shown in the future panorama of Nacos
Dubbo + Nacos, specifically for Dubbo's registry and configuration center
In Alibaba's production environment, Dubbo and Nacos naturally grew up together. Due to the lack of Nacos, the traditional registry center solution has restricted and weakened the power of Dubbo in service governance, traffic governance, service operation and management. Nacos' open source and openness will release these powers in the user environment using Dubbo
Nacos will be fully compatible with Spring Cloud
Nacos will seamlessly support Spring Cloud, providing Spring Cloud users with easier configuration center and registry solutions, using Nacos There is no need to hold Eureka, Spring Cloud Config Server, Git, RabbitMQ/Kafka at least four open source products.
Nacos supports Kubernetes DNS-based Service Discovery
In his speech, Kunyu also said that Alibaba’s practice on VIPServer DNS-based Service Discovery over the years has proved that in the cloud native era, applications will pay more attention to the decoupling with infrastructure, multilingual and even multi-cloud demands. The future of service discovery will definitely be based on standard DNS protocols, rather than private APIs or protocols like Eureka or ZooKeeper. At the same time, on the cloud, in service discovery scenarios, the registration center focuses more on availability rather than data consistency, so Nacos will first recommend DNS-based Servcie Discovery, and prioritizes usability, which is why Nacos can seamlessly integrate into the Kubernetes service discovery system.
Nacos will fill the gap between the Spring Cloud system and the Kubernetes system
In the future, more and more users of the Java ecosystem will choose the Kubernetes+Spring Cloud combination. Unfortunately, in terms of service discovery and configuration management solutions, these two systems adopt completely different solutions, which brings great unnecessary complexity to users who use the two systems at the same time in the registration center and configuration center needs. Nacos will try to fill the gap between the two so that the same service discovery and configuration management solution can be adopted under the two systems, which will greatly simplify the cost of use and maintenance.
Nacos and Service Mesh
Feature Preview
Nacos v0.1.0 Feature Preview Compared with @Kunyu's June overall preview of some features of Nacos v1.0 version
Nacos v0.1.0 is still in its infancy. From CHANGELOG.md, this version mainly releases basic Server-side code, OpenAPI As well as JavaSDK.
Quick Start
From the quick start of Nacos, Nacos is indeed very easy to get started, almost without installation, you only need a simple decompression package, start the server to register the core service of
. I found that the configuration management Demo API is also very simple and straightforward:
From the Nacos documentation (https://nacos.io/#/docs/architecture.md?lang=en-us), in terms of deployment form, Nacos It will support a variety of deployment forms, including the separate deployment of the registration center and the configuration center. At the same time, it provides free SaaS services for the corresponding commercial version of Nacos on Alibaba Cloud . You can directly open an account on Alibaba Cloud to experience Nacos' corresponding commercial products for free. In terms of the differences in open source and commercial versions, the commercial ACM (https://www.aliyun.com/product/acm) and EDAS ANS (https://www.aliyun.com/product/edas) emphasizes the integration experience and commercial services with other Alibaba Cloud cloud services and other Aliware PaaS commercial products.
Nacos' main product milestones and plans Nacos v0.8.0 - Production Ready Version
In the Nacos community RoadMap document (https://nacos.io/#/docs/roadmap.md?lang=en-us), it also roughly announced the subsequent major milestones and version development plans for Nacos 1.0 and 2.0, and it was also emphasized that Nacos v0.8.0 Production Ready was not recommended to be used on production at a large scale.
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 struggle 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 It seems that because Nacos is derived from Alibaba's production code, the overall system may be very complex, and it is a gradual process in code sorting, reconstruction and stripping and internal coupling. Nacos' overall R&D plan is to reach production availability in the next 6-8 months.
DISS is cheap, show me your hand What is more important than complaining is to help you participate in the community and develop together Nacos
Unlike Alibaba's early open source, Alibaba's new round of open source products including RocketMQ, Pouch Container, Dubbo, Nacos, Sentinel, etc. emphasize the development of community and the diversity of the community, and encourage more companies and more developers to participate in open source projects, relying on the community to make products better. At the same time, we will pay attention to internationalization from the beginning and compete with similar foreign products in a direct way.
Nacos initial plan will absorb at least 5 PMCs from other companies and at least 10 external commissioners in the first year. Moreover, Nacos is in the early stages of open source projects, and there is plenty of room for ideas, passion and capable developers to participate. If you are interested in the open source project Nacos, you can join the Nacos community. You can scan the WeChat QR code of "Choice Brother" on , and let "Choice Brother" help you join the "Nacos Community Exchange Group".
Nacos itself urgently needs community help in many aspects. The following aspects are key directions that can be contributed and co-constructed:
is used, integrated, and co-constructed in future products and production plans Nacos
UI Front-end and visual big guide Nacos Control UI Construction
provides Spring Cloud, Kubernetes, Service Mesh Integrated open source system integration and integration code and project
contribute multilingual client
submit requirements, proposal, PR
contribution document
contribution document
share your own stories related to Nacos
on github star Nacos, encourage programmers
Today's recommended article
Click the picture below to read
WebIDE: The era of writing code in the browser is coming?
Geek Time Big Gramophone, 100 CTOs Growth Heart Sutra
Listen to the technology, what paths have the technological masters who have experienced many battles taken.
