Microservices Engine:Get started with service governance in 15 minutes (Java)

Demo introduction

The demo uses a Nacos instance as the registry and includes a Spring Cloud gateway and a Zuul gateway, which you can enable as needed. The default application call workflow is A -> B -> C. Applications A and C have canary release versions. You can obtain the application code from the code repository.

Download the Helm package

Download the Helm package for the demo. The Helm package and image are updated on a regular basis.

Deployment methods

helm upgrade mse-simple-demo mse-simple-demo \
--set mse.namespace=mse-demo \
--set gateway.springcloud=true  \
--install \
--namespace mse-demo \
--values mse-simple-demo/values.yaml

End-to-end canary release

Log on to the MSE console. In the navigation pane on the left, choose Microservices Governance > End-to-end Canary Release.

Graceful start and shutdown

Log on to the MSE console. In the navigation pane on the left, choose Microservices Governance > Application Governance. On the Application List page, click the name of the desired application to go to its overview page.

Throttling rules

Log on to the MSE console. In the navigation pane on the left, choose Microservices Governance > Application Governance. On the Application List page, click the name of the desired application to go to its overview page.

Sample requests

# Common request
http://localhost:20000/A/a
A[10.0.0.47][config=base] -> B[10.0.0.39] -> C[10.0.0.48]

# Canary request
http://localhost:20000/A/a?name=xiaoming
Agray[10.0.0.41][config=base] -> B[10.0.0.55] -> Cgray[10.0.0.30]

# Common request (Feign)
http://localhost:20000/A/aByFeign
A[10.0.0.47][config=base] -> B[10.0.0.55]

# Common request (A requests B and C sequentially)
http://localhost:20000/A/a2bc
A[10.0.0.47][config=base] -> C[10.0.0.48]
A[10.0.0.47][config=base] -> B[10.0.0.55] -> C[10.0.0.49]

# Dubbo request
http://localhost:20000/A/dubbo
A[10.0.0.44] -> B[10.0.0.39]name:A -> C[10.0.0.49] params:A

# Dubbo canary request
http://localhost:20000/A/dubbo?name=xiaoming
Agray[10.0.0.41] -> B[10.0.0.39]name:A -> Cgray[10.0.0.30] params:A

# Request for throttling test
http://localhost:20000/A/flow
A[10.0.0.17][config=base] -> B[10.0.0.39] sleepTime:9 -> C[10.0.0.48] sleepTime:8 code:200
http://localhost:20000/A/dubbo-flow
A[10.0.0.17] -> B[10.0.0.55]name:A -> C[10.0.0.48] params:A
http://localhost:20000/A/isolate
A[10.0.0.42][config=base] -> B[10.0.0.55] sleepTime:504 -> C[10.0.0.48] sleepTime:8 code:200
http://localhost:20000/A/dubbo-isolate
A[10.0.0.17] -> B[10.0.0.55]name:isolate -> C[10.0.0.49] params:isolate
http://localhost:20000/A/params/hot
A[10.0.0.17][config=base] params:hot -> B[10.0.0.55] sleepTime:5 params:hot -> C[10.0.0.49] sleepTime:6 params:hot code:200
http://localhost:20000/A/dubbo-params/hot
A[10.0.0.17] params:hot -> B[10.0.0.55]name:hot -> C[10.0.0.49] params:hot

# Database request
http://localhost:20000/A/sql?command=query&id=1
A[10.0.0.44][config=base] -> B[10.0.0.39] result:{"age":1,"email":"emailUpdate%40demo.com","id":1,"name":"name1Update"}
http://localhost:20000/A/sql?command=update&name=name1Update&email=emailUpd***@demo.com&age=1&id=1
A[10.0.0.44][config=base] -> B[10.0.0.55] result:true

# spring boot request
http://localhost:20000/spring_boot

Application connection

This method requires you to explicitly add the msePilotAutoEnable: "on" label to the deployment of each application that you want to connect. In practice, you can enable microservices governance for an entire Kubernetes namespace in the MSE Operation Center to connect applications in batches.

For more information, see Connect ACK and ACS microservice applications to the MSE Governance Center (Java).

Graceful start and shutdown

1. To use graceful start and shutdown, log on to the ACK console. In the navigation pane on the left of the Cluster Information page, select Operations Management > Add-ons, search for cronhpa in the search box, and click Install.

2. Use the following YAML file to create a scheduled scaling task. The `Namespace` field must be set to the same Kubernetes namespace that you selected during the Helm installation.

apiVersion: autoscaling.alibabacloud.com/v1beta1
kind: CronHorizontalPodAutoscaler
metadata:
  labels:
    controller-tools.k8s.io: "1.0"
  name: cronhpa-deployment-spring-cloud-b
  namespace: mse-demo # Note: The namespace field must be the same as the Kubernetes namespace that you selected during the Helm installation.
spec:
  jobs:
  - name: scale-out
    schedule: 0 0/6 * * * *
    targetSize: 6
  - name: scale-in
    schedule: 0 5/6 * * * *
    targetSize: 2
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: spring-cloud-b

Gateway automatic request configuration

Automatic request sending is enabled by default. You can log on to the Container Service console. In the navigation bar, click Workloads > Stateless. On the Stateless page, click the spring-cloud-gateway application. On the details page, click Edit in the upper-right corner and configure the following environment variables for automatic requests.