Background
Spring Cloud TSF/Tencent implements the service governance component of the Spring Cloud standard microservice SPI, therefore it does not include features related to service invocation components. In other words, while the user's application may inherently contain service invocation components, Spring Cloud TSF/Tencent can provide service governance features based on Spring Cloud standard interfaces during service invocation. Since Spring Cloud TSF/Tencent implements the standard interfaces defined by Spring Cloud, and open-source Spring Cloud has different versions, Spring Cloud TSF/Tencent also requires corresponding support for different Spring Cloud versions.
Meanwhile, Spring Cloud TSF/Tencent also has its own versioning plan, enabling users to select the appropriate Spring Cloud TSF/Tencent version based on their application and Polaris server version. Therefore, this document must specify the version mapping between Spring Cloud TSF/Tencent and Spring Cloud.
Spring Cloud TSF/Tencent Version Compatibility Specification
Spring Cloud TSF/Tencent releases a major version (the first two digits of the version number) every 1-2 years. For example: in 2022, it released Spring Cloud TSF 1.46, and in 2024, it released Spring Cloud Tencent 2.0. Spring Cloud TSF/Tencent's adaptation policy for the open-source version of Spring Cloud:
By default, it adapts to the open-source version of Spring Cloud released two years prior to the release year. For example: Spring Cloud Tencent 2.0 released in 2024 by default adapts to Spring Cloud 2022.
If necessary, it can adapt to the open-source version of Spring Cloud released five years prior to the release year at the earliest. For example: Spring Cloud Tencent 2.0 released in 2024 can adapt to Spring Cloud Hoxton at the earliest.
Adapt on demand to the open-source versions of Spring Cloud from the previous year up to the release year prior to each version's EOS (excluding the EOS year itself).
Spring Cloud TSF/Tencent and Server Version Adaptation
1.x: supports TSF Consul.
2.x: supports Polaris and TSF Consul.
Spring Cloud TSF/Tencent Version Adaptation List
Spring Cloud Tencent 2.1
|
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt by default. | Adapt by default. | Adapt by default. | Adapt by default. |
- | Adapt on demand. | Adapt on demand. | Adapt on demand. |
- | - | Adapt on demand. | Adapt on demand. |
- | - | - | Not adapt. |
Spring Cloud Tencent 2.0
|
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt by default. | Adapt by default. | Adapt by default. | Adapt by default. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
- | Adapt on demand. | Adapt on demand. | Adapt on demand. |
- | - | Adapt on demand. | Adapt on demand. |
- | - | - | Not adapt. |
Spring Cloud TSF 1.46
|
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
Adapt by default. | Adapt by default. | Adapt by default. | Adapt by default. |
Adapt on demand. | Adapt on demand. | Adapt on demand. | Adapt on demand. |
- | Adapt on demand. | Adapt on demand. | Adapt on demand. |
- | - | Adapt on demand. | Adapt on demand. |
- | - | - | Not adapt. |
Spring Cloud TSF/Tencent Version Number Specification
Spring Cloud TSF
Spring Cloud TSF adopts a three-part version number format, a.b.c-xyz-RELEASE, where each part represents the following:
a.b: Aligns with the first two parts of the integrated TSF Consul version number.
c: Version number for requirement development and bug fixes. Increase this version number if there is requirement development or bug fixes.
xyz: Aligns with the major version number of the integrated Spring Cloud.
Example:
The version number 1.46.11-SpringCloud2021-RELEASE corresponds to the TSF Consul server of version 1.46.x and the Spring Cloud 2021 version.
If Spring Cloud TSF has requirement development or bug fixes, and the TSF Consul server remains unchanged, the version number becomes 1.46.12-SpringCloud2021-RELEASE.
Spring Cloud Tencent
Spring Cloud Tencent adopts a four-part version number, a.b.c.d-xyz, where the meaning of each part is as follows:
a.b: Aligns with the first two parts of the version number of the integrated Polaris server.
c: Version number for requirement development. Increase this version number if there is requirement development.
d: Bug fix version number. This version number is increased if there are only bug fixes.
xyz: Aligns with the version number of the integrated Spring Cloud.
Example:
The version number 2.0.0.0-2022.0.5 corresponds to the Polaris server of version 2.0.x.x and the Spring Cloud 2022.0.5 version.
If Spring Cloud Tencent has requirement development and the Polaris server remains unchanged, the version number becomes 2.0.1.0-2022.0.5.
If Spring Cloud Tencent has bug fixes and the Polaris server remains unchanged, the version number becomes 2.0.1.1-2022.0.5.
If Spring Cloud Tencent remains unchanged, the requirement development version number of the Polaris server changes: the version number becomes 2.0.2.0-2022.0.5.
If Spring Cloud Tencent remains unchanged and the bug fix version number of the Polaris server changes: the version number becomes 2.0.2.1-2022.0.5.
Related Links