Microservices Engine:Manage MSE Nacos services by using a cloud-native gateway

No routing policy is configured

1. Log on to the MSE console.

2. In the top navigation bar, select a region.

3. In the left-side navigation pane, choose Cloud-native Gateway > Gateways. On the Gateways page, click the name of the gateway.

4. On the Gateway Ingress tab of the Overview page, view the ingress IP address of the gateway.

   

   Note

   The ingress IP address of a cloud-native gateway is the IP address of an SLB instance that is associated with the gateway. You can replace the SLB instance with a self-managed SLB instance. For more information, see Manage SLB instances that are specified as Ingresses.

5. Run the following command to send a testing request:

   curl -I http://8.136.104.xx/echo-rest/hello

   Note

   The preceding command contains the Demo service of the Nacos service source. You can replace the URL with the URL of your backend service.

   The following result is returned:

   HTTP/1.1 200 OK
   Content-Type: text/plain;charset=UTF-8
   Content-Length: 5
   Date: Thu, 29 Aug 2024 08:21:47 GMT
   req-cost-time: 9
   req-arrive-time: 1724919707979
   resp-start-time: 1724919707988
   x-envoy-upstream-service-time: 8
   server: istio-envoy

A throttling policy is configured

In high-concurrency access scenarios, if no proper throttling policy is configured for your application, the backend service may become overloaded due to excessive requests. This adversely affects service response speed or even causes the service to crash. Throttling ensures that the number of requests is within a range that the system can handle. You can configure throttling policies for cloud-native gateways. For more information about routing policies, see Routing policies.

1. Log on to the MSE console. In the top navigation bar, select a region.

2. In the left-side navigation pane, choose Cloud-native Gateway > Gateways. On the Gateways page, click the name of the gateway.

3. In the left-side navigation pane, click Routes.

4. Find the routing rule that you want to modify and click Policies in the Actions column.

5. In the Policies section of the page that appears, click the Throttling tab.

   Throttling policies are used to monitor the queries per second (QPS) of a route. If the QPS reaches the specified threshold, traffic is immediately blocked. This prevents a breakdown of backend services due to traffic surges and ensures the high availability of the backend services.

   1. On the Throttling tab, click Flow control rules.

   2. On the Throttling Rules tab, configure the following parameters.

      

      Parameter	Description	Example
      Overall QPS Threshold	Enter a value for Overall QPS Threshold.	1
      Web Fallback Behavior	Select Returns the specified content or Jump to the specified page for Web Fallback Behavior.	Returns the specified content
      HTTP status code	Enter the HTTP status code. The default value is 429.	429
      Returned Content-Type	Select Plain text or JSON for Returned Content-Type.	Plain text
      HTTP Text	Enter the returned text.	springcloud-demo flow limit
      Whether to open	If you turn on this switch, the configured throttling policy takes effect.

   3. Click New or Save to create or update the rule. In the message that appears, click OK.

6. Execute the following scripts to send testing requests:

   Windows

   @echo off
   
   set "localUrl= http://8.136.104.xxx/echo-rest/hello"
   
   :loop
   curl -i -s %localUrl%
   
   goto loop

   Linux

   #!/bin/bash
   
   URL="http://8.136.104.xxx/echo-rest/hello"
   
   while true; do
       curl -i -s $URL
   done

   The following result is returned. After you enable the throttling policy, the HTTP status code 429 is returned.

   helloHTTP/1.1 429 Too Many Requests
   content-type: text/plain; charset=UTF-8
   content-length: 26
   date: Thu, 29 Aug 2024 08:54:46 GMT
   server: istio-envoy
   
   springcloud-demo flow limit HTTP/1.1 200 OK
   Content-Type: text/plain;charset=UTF-8
   Content-Length: 5
   Date: Thu, 29 Aug 2024 08:54:46 GMT
   req-cost-time: 8
   req-arrive-time: 1724921686961
   resp-start-time: 1724921686970
   x-envoy-upstream-service-time: 7
   server: istio-envoy