Multi-service gateway-oriented flow limiting and automatic capacity expanding and shrinking method

Abstract

The invention discloses a multi-service gateway-oriented flow limiting and automatic capacity expanding and shrinking method. The method comprises the following steps: providing OpenResty, compiling the service parameters and the OpenResty source code through a cluster makefile, dynamically generating an nginx.conf file, deploying a service gateway corresponding to the service according to the nginx.conf file, counting the flow of each service, and sending the flow to a gateway system; the service passing through the load of the service according to the zabbix and sending the load to the gateway system; the gateway system monitoring the flow and the load in real time, and when the flow and the load are not matched, performing automatic capacity expansion and shrinkage. According to the multi-service gateway-oriented flow limiting and automatic capacity expanding and shrinking method provided by the invention, the number of servers can be increased in a peak period on the basis of flowlimiting, the normal service is ensured, the servers are returned in a valley period, and the cost is reduced.

Description

technical field [0001] The invention relates to the field of computer technology, in particular to a current limiting and automatic expansion and contraction method for multi-service gateways. Background technique [0002] When a user requests a link (API), the background corresponding to this API needs to perform logical processing on the parameters of the API and return it. If the amount of requests is too large, such as a DDOS attack or spike activity, the CPU or memory usage is too large, which may cause the service to be unavailable. Therefore, before this service, it is necessary to add a gateway layer to isolate external and internal services. The core function of this layer is forwarding. It has no business logic itself, and forwards user requests to background services, which then pass the results to the gateway. , the gateway then responds to the background. [0003] Forwarding can record and modify the address, parameters and results of the user's request, so th...

AI Technical Summary

Problems solved by technology

A good gateway, such as the OpenResty used in this invention, supports current limiting. The so-called current limiting means that the background service can only make up to 2000 requests per second, but when the seckill activity is active, it is 2200 per second. Exceeding the amount may cause the service to slow down (CPU rises above 90%) and unavailable (CPU 100%)

The gateway itself has no logic, and the pressure it can withstand is much greater than that of the background service. The gateway can normally release 2000 requests for these 2200 requests, and the remaining 100 requests are waiting in the waiting queue (if the capacity of the waiting queue is only 100). This caused a problem. The waiting time for the users of these 100 requests became longer, and the remaining 100 requests directly returned the result "the current number of requests is too large". Only some people can enter the background service, and the requests of others are rejected by the gateway.

Images