Spring Cloud Tencent
English | 简体中文
Introduction
Spring Cloud Tencent contains components distributed micro-service applications need during developing phase, developers that built their key architectures based on Spring Cloud can use these components
Based on Spring Cloud Tencent, you only need a small configuration to launch Spring Cloud and micro-service's joint solutions.
Key Features
- Service Registration and Discovery：Based on Spring Cloud's discovery and registration standard.
- Service Routing and LoadBalancer：Based on ribbon's API port, provide dynamic routing and load balancing use cases.
- CircuitBreaker Node：Support circuitbreak's auto-reset ability, ensure the reliability of distributed server
- Rate Limiter：Support rate limit between microservice and access layer, ensure the stability of backend, one can configure policies and traffic data from the control panel
Components
Polaris：Polaris Spring Cloud operation centre, provide solutions to registration, dynamic routing, load balancing and circuitbreaker.
How to build
- master's branch matches Spring Cloud Hoxton, support lowest at JDK 1.8.
Spring Cloud Tencent uses Maven to construct, the fastest way is to clone project to local files, then execute the following orders:
./mvnw install
When all the steps are finished, the project will be installed in local Maven repository.
How to Use
How to Introduce Dependency
Add the following configurations n dependencyManagement, then add the dependencies you need.
<dependencyManagement>
<dependencies>
<dependency>
<groupId>com.tencent.cloud</groupId>
<artifactId>spring-cloud-tencent-dependencies</artifactId>
<!--version number-->
<version>${version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
Example
Spring Cloud Tencent project contains a sub-module spring-cloud-tencent-examples. This module provides examples for users to experience, you can read the README.md in each example, and follow the instructions there.
Example List:
Version Standard
We use a version policy related to Spring Cloud's major version number.
Project version includes ${MAJOR_VERSION}.${MINOR_VERSION}.${PATCH_VERSION}.${CORRESPONDING_MAJOR_VERSION_OF_SPRING_CLOUD}.${CORRESPONDING_MINOR_VERSION_OF_SPRING_CLOUD}-${RELEASE_TYPE}. ${MAJOR_VERSION}, ${MINOR_VERSION}, ${PATCH_VERSION} are in numbers starting from 0. ${CORRESPONDING_MAJOR_VERSION_OF_SPRING_CLOUD} is the same as the major version number of Spring Cloud, like Hoxton, Greenwich. ${CORRESPONDING_MINOR_VERSION_OF_SPRING_CLOUD} is the same as the major version number of Spring Cloud, like RS9. ${RELEASE_TYPE} is like RELEASE or RC currently. Actually, the RELEASE version does not add a release type in the version, and the RS version will add a suffix and start from RC0.
For example: 1.0.0.Hoxton.SR9-RC0
License
The spring-cloud-tencent is licensed under the BSD 3-Clause License. Copyright and license information can be found in the file LICENSE
64 Dec 23, 2022
24.8k Jan 6, 2023
4 Sep 13, 2022
59 Nov 30, 2022
1 Jan 4, 2022
373 Dec 27, 2022
15.7k Dec 31, 2022
1 Oct 26, 2022
3.4k Dec 30, 2022
2 Feb 8, 2022
5.6k Dec 30, 2022
5 Nov 21, 2022
3 Nov 2, 2021
8 May 12, 2022
15 Apr 26, 2022
12.1k Jan 1, 2023
65 Dec 23, 2022
2 Oct 19, 2021