huaweicloud / spring-cloud-huawei-samples

This project provide samples for Spring Cloud Huawei. Read each sub-project for details about each sample.
38 stars 90 forks source link

Spring Cloud Huawei Samples 中文

This project provide samples for Spring Cloud Huawei. Read each sub-project and wiki for details about each sample.

Directory description:

Branches:

Prerequisites

Running samples, must first prepare CSE environment

More information can be found in Huawei Cloud.

And edit bootstrap.yml for each microserivce, configure the correct CSE services, like config center and service center.

Samples using CSE 2.0 in default,the config service is kie

spring:
  cloud:
    servicecomb:
      config:
        serverType: kie
        serverAddr:  http://127.0.0.1:30110

If using CSE 1.0,config service change to config-center.

spring:
  cloud:
    servicecomb:
      config:
        serverType: config-center
        serverAddr:  http://127.0.0.1:30113
        fileSource: consumer.yaml

Cloud Service Engine(CSE)

Cloud Service Engine (CSE) provides service registry, service governance, and configuration management. It allows you to quickly develop microservice applications and implement high-availability O&M. Furthermore, it supports multiple languages and runtime systems, and unified access and governance of intrusive frameworks such as Spring Cloud, Apache ServiceComb (Java Chassis/Go Chassis), and Dubbo, and non-intrusive service meshes.

CSE has two versions: CSE 1.0 and CSE 2.0.

CSE 2.0 provides an exclusive edition of the microservice engine. The microservice engine exclusive edition is a commercial engine that supports large-scale microservice application management. You can select different specifications based on service requirements. Engine resources are exclusively used and the performance is not affected by other tenants.

Compared with CSE 1.0, CSE 2.0 completely upgrades the underlying architecture, functions, security, and performance. It provides independent service registration and discovery centers and configuration centers to support definition and governance based on user service scenarios. Table 1 describes the feature comparison between the two versions.

More informationcan be found in Official Documents .