You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -22,74 +21,51 @@ Including [Apache ServiceComb](http://servicecomb.apache.org) and [ServiceStage]
22
21
* Spring Cloud Edgeware, Finchley have all reached end of life status and are no longer supported.
23
22
24
23
## Why use
25
-
1. Gives Blue-green Deployments and Canary Releases ability to your spring cloud application.
26
-
2. Automatically generate a document, which follow open API specification, and register it to service registry, so that members of team can view and download API doc in unified service.
27
-
3. Combined with the ecosystem of Apache servicecomb:
28
-
- Apply multilingual paradigm to your microservice system by using [mesher](https://github.com/apache/servicecomb-mesher), an implementation of service mesh, java or spring cloud is not the only choice anymore.
29
-
- Developer is able to use edge-service, a high-performance gateway which benifits from reactive, outperforms than spring cloud gateway and Netflix zuul.
30
-
- A [go microservice framework](https://github.com/go-chassis/go-chassis) can work with springcloud.
31
-
4. Zero-code thinking, all features are based on configuration, transparent to users, no migration costs.
24
+
25
+
1. Integrate Spring Cloud applications to Apache ServiceComb services, like servicecomb-service-center, servicecomb-kie.
26
+
2. Integrate Spring Cloud applications to use ServiceStage. ServiceStage is a service deployment environment for microservices,
27
+
includs high available discovery and registration service, configuration service, governance service, transaction management
28
+
service and so on.
29
+
3. Other enhancements like swagger generation and registration, canary release and so on.
* Support [ServiceComb-Kie](https://github.com/apache/servicecomb-kie),
48
-
KIE is a key value based configuration center that supports historical version and label management.
49
-
50
-
***spring-cloud-starter-huawei-dtm:**
51
-
* Support for use HuaweiCloud DTM(Distributed Transaction Management),it resolve consistency issues in a distributed environment.
41
+
* Support for use [servicecomb-kie](https://github.com/apache/servicecomb-kie)
42
+
* Support for use [CSE][CSE] as [Configuration Center][Configuration Center]
43
+
* Implements PropertySource
44
+
* Implements @RefreshScope
45
+
46
+
***spring-cloud-starter-huawei-governance:**
47
+
* Support for use [CSE][CSE][Request Marker-based Governance][Request Marker-based Governance]
48
+
* Implements retry for FeignClient and RestTemplate
49
+
* Implements rate limiter, circuit breaker, and bulkhead for Servlet Web MVC
52
50
53
51
***spring-cloud-starter-huawei-router:**
54
-
* The routing management module , for gray release,canary release by config,
55
-
it supports matching HTTP header and proportional traffic distribution.
52
+
* Support for use [ServiceStage][ServiceStage][Canary release features][Canary release features].
56
53
57
-
***spring-cloud-starter-huawei-swagger:**
58
-
* Automatically generate swagger document with zero-code (based on [spring-fox](https://github.com/springfox/springfox)),
59
-
and register to the server-center for interface documentation management.
60
-
* Networking with [ServiceComb-Java-Chassis](https://github.com/apache/servicecomb-java-chassis) based swagger.
61
-
* Using [Edge-Service](https://docs.servicecomb.io/java-chassis/en_US/edge/by-servicecomb-sdk/) gateway,
62
-
Better performance than spring cloud gateway and netflix zuul.
54
+
***spring-cloud-starter-huawei-dtm:**
55
+
* Support for use [ServiceStage][ServiceStage][DTM][DTM]
63
56
64
-
***spring-cloud-starter-huawei-governance:**
65
-
* Based on the dynamic configuration, provide CircuitBreaker, Bulkhead, RateLimiter and Retry feature, based on [resilience4j](https://github.com/resilience4j/resilience4j)。
66
-
* For traffic governance, the operator matching is used to label the traffic, which can accurately govern the traffic for the request path , request method and request header.
67
-
* By using dynamic configuration, zero waiting for governance rules to take effect. No code intrusion, only need distribution configuration.
0 commit comments