Shulou(Shulou.com)06/01 Report--

Nacos is Alibaba's open source service discovery and configuration management project. Version 1.1.4 of this release mainly brings the interface function with Istio, using the latest MCP protocol of Istio. This article will introduce the features of the new release, including this feature. Upgrade Guide server version 0.8.0 and above: after unpacking the installation package, replace {nacos.home} / target/nacos-server.jar and restart Nacos Server one by one, then upgrade to version 1.0.0. The client can replace the pom dependency. Supports Istio MCP protocol, which is the biggest update of this version. It mainly implements the function of sending Nacos service data to Istio. It is also the first official MCP protocol docking version of all registries in the industry. Pilot's latest design uses the MCP protocol to interact with all back-end data sources. The advantage of this is that the code of all extended components can be decoupled, and Pilot maintains lightweight logic, greatly improving code quality, component stability, and extensibility. We can take a look at the official Pilot design provided by Pilot. The address details can be found here.

Figure 1 the latest design concept map of Pilot although there are Consul, Eureka and so on in the MCP Server of the Pilot backend in the design diagram, but these projects currently do not have an officially supported MCP Server. Nacos is currently the first project to officially support the Istio MCP agreement. For the design of the MCP protocol, you can refer to the documentation of Istio. MCP Server implemented by Nacos currently uses a single service number and full service push mode, because Pilot does not support incremental service data push (after the release of Nacos 1.1.4, Pilot already supports endpoint-level incremental push, and Nacos will also support it in the next version). The logic of the implementation is to start a gRPC Server to transfer MCP data. The code can be seen here. Figure 2 how the Nacos MCP Server architecture uses Nacos MCP Server is as follows: 1. Download the latest Nacos 1.1.4 installation package, decompress it; 2. Configure application.properties, and then restart Nacos;nacos.istio.mcp.server.enabled=true Note: if Nacos is a cluster deployment, you only need to configure one Server to start MCP Server, because the data of each Nacos Server is full. At the same time, the port used by Nacos MCP Server is 18848, please note whether the port conflicts; 3. Configure Pilot to use Nacos MCP Server:configSources-- address: x.x.x.x:188484 and restart Pilot; custom instance ID in previous versions, the instanceId field of Instance class is used as a unique attribute to identify this instance, and its value cannot be specified by the client by default. In version 1.1.4, we support allowing the client to customize ID and a new instanceId generation algorithm: a unique integer within the service, which can be used as the unique index of the instance within the service. This feature is contributed by vettal-wu, thank you very much. The use of this shaping instanceId is to configure instance's metadata when registering, and specify the id generation algorithm. The sample code is as follows: Instance instance = new Instance (); instance.setIp ("1.1.1.1"); instance.setPort (80); / / ephemeral=false must be set to ensure that the server uses a strict consistency protocol, otherwise it may result in generated instance id conflicts: instance.setEhpemeral (false); instance.setMetadata (new HashMap ()) Instance.getMetadata (). Put (PreservedMetadataKeys.INSTANCE_ID_GENERATOR, Constants.SNOWFLAKE_INSTANCE_ID_GENERATOR); Nacos also has some optimization updates on code quality in this release, which can be found in the 1.1.4 issue list. How to work together to achieve this goal, you need to actively participate in the Nacos community. If you find spelling mistakes in your document, errors in your code, or want new features or suggestions, you can create an issues on GitHub. If you want to get started, you can choose the issues with the following tags in the github repository. Good first issue: it's a very good introduction to issues for beginners. Contribution welcome: problems that need to be solved and very important modules, but there is a lack of contributors at present. Contributors are welcome to contribute. DISS is cheap, the booming Nacos community, show me your hand is more important than complaining to help. Participate in the community to develop Nacos together as users follow and join the Nacos community. The Nacos community is booming. As of the post, Nacos has nine WeChat groups in just a few months, including 7 full members, 1 QQ group, 1 nail group, and the number of communities following Nacos has reached nearly 5000. Exchange skills, exchange experiences, recruit friends and grab red envelopes in the Nacos group. awfully.

It makes sense to join the Nacos community as a code contributor from Nacos users to become a contributor, and the Nacos development team is indeed growing, from only 4 code contributor to more than 40, 1.1.4 version, developers involved in Nacos repository contribution are: stackisok,loadchange, ly641921791, EZLippi, rushsky518, universefeeler, nkorange, vettal-wu, beldon and so on.

The original link to this article is the original content of Yunqi Community and may not be reproduced without permission.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.