Table of contents
1. The troublesome multi-version number system
3. Why there are multiple version number systems
1. The troublesome multi-version number system
Due to historical reasons, spring cloud is divided into two systems: Alibaba and Netflix.
Students who want to understand the reason and the ins and outs of the entire spring cloud system can read my other article:
Introduction to SpringCloud__BugMan's Blog-CSDN Blog
After knowing the above, let's take a look at how messy the version number of spring cloud is:
Open the official website and first have a version list of the total project:
Then scroll down, the adaptation relationship between Netflix's spring cloud and spring boot versions:
In other words, the version number of Netflix should be as in the list.
But when we click into the Netflix project, we will find that its version number list is like this:
Ok, the little friends who just started getting started at this time will be deceived, and there will be the following doubts:
- Since it is divided into two systems, Alibaba and Netflix, why does the general project list of spring cloud still have a version number
- Why is the Netflix version number list displayed in the adaptation list of spring boot different from the version number list seen in Netflix? Why are there two sets of Netflix version numbers?
- Which maven coordinates should I use when I want to use spring cloud?
This article will start with the component relationship, clarify the project directory structure of spring cloud, and then clarify the version number issue along the way.
2. Directory relationship
First of all, we need to clarify the relationship between components in the entire spring cloud ecosystem, that is, why the directory on the official website looks like that.
To implement microservices, the core issues are:
- Service Registration and Discovery
- fault tolerance
The two systems of Netflix and Alibaba have given their own different implementations of the above two points. In general, they have launched different registry components and fault-tolerant components. In addition, in terms of easy capability expansion, it is realized through integration and access to third-party components, such as gateways, buses, and configuration centers.
With this understanding, we will not be so dizzy when we look at the entire spring cloud project list.
When we enter the spring official website, we can see the two sub-projects of Alibaba and Netflix, and many sub-projects at the same level as them. The projects of Alibaba and Netflix contain their own registry components and fault-tolerant components, which are at the same level as Alibaba and Netflix. It is some extended tripartite components such as gateway (gateway), config (configuration center), bus (bus) and so on.
3. Why there are multiple version number systems
In fact, after the component relationship is clarified, the issue of the version number is easy to understand. Although due to historical reasons, spring cloud is divided into Alibaba and Netflix, but spring cloud was first created by Netflix, so the official website still uses Netflix as the center to describe the entire spring cloud. The real version of the family bucket launched by Netflix is actually the version listed in the adaptation list:
Let's click into a version of Netflix's family bucket at random, and we can see that it is actually the registration center (Spring Cloud Netflix) + other components:
After the core R&D personnel of Netflix's spring cloud left, the company contributed its spring cloud to the official spring cloud community, and the official community iterated the spring cloud of the Netflix system. Therefore, the list of version numbers on the general project is the iteratively updated version after the spring cloud official community receives the Netflix system:
Just click into a version, and you can see that it is actually a family bucket given around Netflix:
Then the spring cloud Netflix subproject on the official website only maintains the eureka version:
We click into any version, and we can see that it is very simple eureka:
As for spring cloud Alibaba, it is very indifferent to the world, and it simply maintains its own version number:
Maintain your own nacos and sentinel:
