WO2019052225A1

WO2019052225A1 - Open platform control method and system, computer device, and storage medium

Info

Publication number: WO2019052225A1
Application number: PCT/CN2018/088835
Authority: WO
Inventors: 汪小波
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-09-13
Filing date: 2018-05-29
Publication date: 2019-03-21
Also published as: CN107800768B; CN107800768A

Abstract

Provided is an open platform control method. The method comprises: a load balancing server receiving a resource invoking request, which carries a resource invoking interface name of a serving party and which is initiated by an invoking party, and allocating the resource invoking request to an execution server according to a pre-set load balancing algorithm; the execution server searching for a serving party identifier corresponding to the resource invoking interface name of the serving party, and counting the number of concurrent task threads corresponding to the service party identifier; if the number of concurrent task threads corresponding to the serving party identifier is less than a first pre-set maximum number of concurrent task threads corresponding to the serving party identifier, creating a task thread corresponding to the resource invoking request; and using the task thread to execute the resource invoking request initiated by the invoking party, and returning an execution result to the invoking party.

Description

Open platform control method, system, computer device and storage medium

The present application claims priority to Chinese Patent Application Serial No. JP-A-A-------------

Technical field

The application relates to an open platform control method, system, computer device and storage medium.

Background technique

In the software industry and the network, the Open Platform refers to a software system that allows an external program to increase the function or use of the software system by exposing its Application Programming Interface (API) or function. The resources of the software system do not need to change the source code of the software system.

As an resource invoking platform, the open platform bears tens of millions of calls per day. Traditional open platform control methods control the invocation of resources by setting up queues. However, for a sudden burst of the call volume of a certain servant system, or a response time of a certain servant system is too long, the resource pool of the open platform is abnormally occupied by some caller systems, which affects the normal resource call of other caller systems. Thereby reducing the stability of the open platform.

Summary of the invention

In accordance with various embodiments disclosed herein, an open platform control method, system, computer device, and storage medium are provided.

An open platform control method includes:

The load balancing server receives a resource invocation request initiated by the caller, where the resource invoking request carries the server name of the calling party resource;

The load balancing server allocates the resource invoking request to the execution server according to a preset load balancing algorithm;

The execution server searches for a service party identifier corresponding to the service provider resource call interface name;

The execution server collects the number of concurrent task threads corresponding to the service party identifier;

If the number of concurrent task threads corresponding to the service provider identifier is less than the number of the first preset maximum concurrent task threads corresponding to the service provider identifier, the execution server creates a task thread corresponding to the resource call request;

Executing, by the execution server, the resource invoke request initiated by the caller by using the task thread; and

The execution server returns an execution result of the resource call request to the caller.

An open platform control system comprising:

a load balancing server, configured to receive a resource invocation request initiated by the caller, where the resource invocation request carries a service party resource to invoke an interface name, and allocates the resource invoking request to the execution server according to a preset load balancing algorithm;

An execution server, configured to receive the resource call request allocated by the load server, search for a service party identifier corresponding to the service provider resource call interface name, and count the number of concurrent task threads corresponding to the service party identifier, if the service is The number of the concurrent task threads corresponding to the party identifier is smaller than the number of the first preset maximum concurrent task threads corresponding to the service party identifier, and the task thread corresponding to the service party identifier is created, and the call is performed by using the task thread. A resource invocation request initiated by the party returns the execution result of the resource invoking request to the calling party.

A computer apparatus comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by a processor, implement the steps of the open platform control method provided in any one of the embodiments of the present application.

One or more non-volatile storage media storing computer readable instructions, when executed by one or more processors, causing one or more processors to implement the opening provided in any one embodiment of the present application The steps of the platform control method.

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features and advantages of the present invention will be apparent from the description, drawings and claims.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings to be used in the embodiments will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present application, Those skilled in the art can also obtain other drawings based on these drawings without any creative work.

1 is an application environment diagram of an open platform control method in accordance with one or more embodiments.

2 is a flow diagram of an open platform control method in accordance with one or more embodiments.

3 is a flow diagram of a resource invocation request allocation method in accordance with one or more embodiments.

4 is a flow chart of a hotspot resource call request control method in another embodiment.

FIG. 5 is a flow diagram of a resource invocation request execution method in accordance with one or more embodiments.

6 is a block diagram of an open platform control system in accordance with one or more embodiments.

FIG. 7 is a block diagram of a computer device in accordance with one or more embodiments.

Detailed ways

In order to make the technical solutions and advantages of the present application more clear, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

The open platform control method provided by the present application can be applied to an application environment as shown in FIG. 1. The load balancing server 102 communicates with the caller 104 over the network, the caller 104 communicates with the execution server 106 over the network, and the load balancing server 102 communicates with the execution server 106 over the network. The load balancing server 102 receives the resource invocation request initiated by the caller 104, and allocates a resource invocation request to the execution server 106 according to the preset load balancing algorithm, so that the execution server 106 executes the resource invocation request, and returns the execution result to the calling party 104. Specifically, the load balancing server 102 receives the resource invocation request initiated by the caller 104, and the resource invoking request carries the service provider resource to invoke the interface name, and the load balancing server 102 allocates the resource invoking request to the execution server 106 according to the preset load balancing algorithm, and executes the server. 106: Find a service party identifier corresponding to the service provider resource call interface name, and execute a server task to count the number of concurrent task threads corresponding to the service party identifier, and if the number of concurrent task threads corresponding to the service party identifier is less than the number corresponding to the service party identifier A predetermined maximum number of concurrent task threads, the execution server 106 creates a task thread corresponding to the resource call request, and executes the resource call request initiated by the caller 104 with the task thread, and returns the execution result to the caller 104. The load balancing server 102 and the execution server 106 can be implemented by a separate server or a server cluster composed of a plurality of servers.

In one embodiment, as shown in FIG. 2, an open platform control method is provided, including the following steps:

Step 202: The load balancing server receives the resource invocation request initiated by the caller, and the resource invoking request carries the name of the interface of the server resource.

The resource call of the open platform involves the caller, the service party and the open platform. The service party publishes the system interface on the open platform for the caller to call. The back end of the open platform is a server cluster composed of several servers, including a load balancing server and an execution server. The load balancing server is a load balancing server. Through the load balancing server, the service requests are evenly distributed to the execution server, thus ensuring the response speed of the entire open platform. The execution server is the server that actually performs the service request.

Receiving, by the load balancing server in the open platform back-end server cluster, a call-initiated resource call request, so as to allocate the resource call request to the execution server, and the resource call request carries the server-side resource call interface name, and the server-side resource call The interface name is used to uniquely identify the servant resource provided by the open platform.

Step 204: The load balancing server allocates a resource invoking request to the execution server according to a preset load balancing algorithm.

The preset load balancing algorithm is a preset resource call request allocation algorithm, which may be a polling algorithm, a random algorithm, a session holding algorithm, and a weighting algorithm.

Specifically, the polling algorithm assigns the received resource call request order to the execution server in a preset allocation order, and the method treats each execution server in a balanced manner. The random algorithm randomly assigns the received resource invocation request to any execution server in the server cluster. The session hold algorithm (also known as source address hashing) first obtains the IP address of the caller that initiated the resource call request, and then calculates the mapped value corresponding to the caller's IP address through the hash function. Using the mapping value to perform the modulo operation on the size of the execution server cluster (the total number of execution server clusters is 5, the size of the execution server cluster is 5), and the result is the server that actually executes the resource call request. Serial number. The source address hashing method is used for load balancing. When the size and order of the execution server cluster are unchanged, the resource invocation requests initiated by the caller of the same IP address are allocated to the same execution server. The weight algorithm forms a load balancing multiple priority queue according to the priority of each execution server or the current load status (ie, weight), and each waiting connection in the queue has the same processing level, between the queues. The equalization process is performed in the order of priority. The weight is an estimate based on the capabilities of each node. The weight algorithm itself is an auxiliary algorithm that needs to be used in conjunction with other algorithms. For example, in combination with the polling algorithm, a weighted rounding algorithm is formed, that is, each execution server is assigned a corresponding weight coefficient in advance. After the load server receives the resource call request, the resource call request is allocated according to a preset allocation order and a weight coefficient. For example, in the execution server cluster, there are execution server A, execution server B, and execution server C, and the preset allocation order is execution server C, execution server A, and execution server B. The corresponding weight coefficients are 1, 2, and 3, respectively, and the execution server is assigned in the order of execution server C, execution server A, execution server A, execution server B, execution server B, and execution server B.

Step 206: The execution server searches for a service party identifier corresponding to the service provider resource call interface name.

The servant ID is used to uniquely identify the servant. It can be the servant IP address, the servant domain name, or a custom string.

Step 208: Perform server statistics on the number of concurrent task threads corresponding to the service party identifier.

The execution server uses a concurrent processing mechanism for resource call requests to improve the execution efficiency of the open platform system. The execution server finds the corresponding service party identifier according to the received service provider resource call interface name, and then counts the number of concurrent task threads corresponding to the service party identifier in the current concurrent task thread to complete the subsequent operations.

Step 210: If the number of concurrent task threads corresponding to the service party identifier is less than the number of the first preset maximum concurrent task threads corresponding to the service party identifier, the execution server creates a task thread corresponding to the resource call request.

The first preset maximum number of concurrent task threads is a preset maximum value of concurrent task threads corresponding to the service party identifier. The first preset maximum concurrent task thread has different corresponding values according to the difference between the servant resource call amount and the servant resource call frequency. For example, the servant resource carrying the interface name carried by the resource call request is the servant A. Since the history call of the servant A is relatively frequent, the preset maximum concurrent task thread processing number of the servant A is 6 (the maximum number of concurrent task threads of the execution server is 10); the other party that the resource call request carries The service party corresponding to the resource call interface name is the service party B. Since the duration of the service party B is relatively small, the preset maximum concurrent task thread processing number of the service party B is 2.

The default maximum number of concurrent task thread processing is for a single server that receives a resource invocation request. In other embodiments, the number of the first preset maximum concurrent task threads may be the maximum number of concurrent task threads corresponding to all execution servers in the server cluster corresponding to the open platform system, and correspondingly, the service party identifier is collected in step 208. The number of corresponding concurrent task threads, that is, the execution server that receives the resource call request, counts the number of concurrent task threads corresponding to the service party identifier among all the execution servers in the server cluster corresponding to the open platform system.

When the number of concurrent task threads corresponding to the servant identifier is less than the number of the first preset maximum concurrent task threads corresponding to the servant identifier, the execution server that receives the resource call request still has processing corresponding to the servant identifier. The resource invokes the request's ability, so the execution server creates a new task thread that is used to execute the resource call request corresponding to the server resource call interface name.

In one embodiment, when the number of concurrent task threads corresponding to the service party identifier is equal to the preset maximum concurrent task thread processing number corresponding to the service party identifier, sending a prompt resource call request rejection message to the caller, to notify The resource call request sent by the caller currently has no available threads to process, so that the caller subsequently resends the resource call request.

Step 212: The execution server executes the resource invocation request initiated by the caller by using the task thread.

After determining that the execution server has the ability to process the resource call request, the created task thread is used to execute the caller initiated resource call request.

In step 214, the execution server returns the execution result of the resource call request to the caller.

After the execution server executes the caller-initiated resource call request by using the created task thread, the execution result is sent to the caller.

In the above-mentioned open platform control, the number of concurrent task threads corresponding to the servant identifier is limited, so that the processing of the resource call request of different servants is controlled, thereby effectively avoiding a sudden burst of the call amount of a certain servant system, or The response time of a certain servant system is too long, which causes the resource pool of the open platform to be abnormally occupied or even embarrassed by some caller systems, thereby improving the stability of the open platform. At the same time, the open platform forwards the received resource call request to the execution server through the load balancing server, so that the execution server performs the resource call request, separates the allocation and execution functions of the resource call request, and improves the execution efficiency of the open platform.

In one embodiment, as shown in FIG. 3, the above step 202 includes:

Step 302: The load balancing server counts the number of current concurrent task threads of each execution server.

After receiving the resource invocation request initiated by the caller, the load balancing server collects the number of current concurrent task threads of each execution server to perform subsequent resource call request allocation.

Step 304: If the number of current concurrent task threads of the execution server is less than the number of the second preset maximum concurrent task threads corresponding to the execution server, calculate the task thread availability rate of the execution server.

The second preset maximum number of concurrent task threads is a preset number of concurrent task threads corresponding to the execution server. If the performance of the server A is good, the number of the second preset maximum concurrent task threads corresponding to the execution server A is set to 20. If the performance of the execution server B is slightly weak, the number of the second preset maximum concurrent task threads corresponding to the execution server B is set to 16. The task thread availability rate is the ratio of the number of available threads in the execution server to the preset maximum number of task threads. For example, the number of current concurrent task threads of a certain execution server is 4, and the preset maximum task corresponding to the execution server The number of threads is 10, the number of currently available task threads is 6, and the task thread availability is 0.6.

If the number of current concurrent threads of the execution server in the server cluster corresponding to the open platform is smaller than the second preset maximum number of threads corresponding to the execution server, the execution server has the capability of processing the resource call request, and then performs the execution by calculating The task thread availability rate of the server prepares for the subsequent execution of the execution server corresponding to the maximum task thread availability rate.

Step 306: Determine an execution server corresponding to the maximum task thread availability rate according to the task thread availability rate of each execution server.

According to the task thread availability rate of the execution server calculated in step 304, in the execution server cluster having the processing resource call request capability, the execution server corresponding to the maximum task thread availability rate is filtered out.

Step 308, assigning a resource call request to an execution server corresponding to the maximum task thread availability rate.

After successfully filtering out an execution server having the ability to process resource call requests and having the highest task thread availability, a resource call request is assigned to the execution server.

In the above open platform control method, first, an execution server set having a capability of processing a resource call request is determined by counting the number of current concurrent task threads of each execution server in the server cluster, and then each of the execution server sets is calculated. The task thread availability rate corresponding to the execution server is allocated to the execution server with the highest availability rate of the task thread, which improves the response speed of the open platform.

In one embodiment, as shown in FIG. 4, before step 206, the method further includes:

Step 402: Perform the server to count the number of resource call requests corresponding to the service party identifier in the resource call request received within the preset time range.

After receiving the resource call request, the execution server first counts the number of resource call requests corresponding to the service party identifier in the resource call request received by all the execution servers corresponding to the open platform in the preset time range. If the execution server statistics of the resource call request are received within 24 hours, all the execution servers corresponding to the open platform receive the same resource call request number as 10000 corresponding to the service party identifier corresponding to the resource call request.

In one embodiment, after receiving the resource invocation request, the execution server first counts the number of resource invocation requests corresponding to the service party identifier in the resource invocation request received by the server in the preset time range. If the execution server statistics of the resource call request is received within one month, the execution server receives the same number of resource call requests as the service party identifier corresponding to the resource call request, and is 500.

Step 404: If the number of resource invocation requests corresponding to the service party identifier is less than the maximum number of calls of the preset resource invocation request corresponding to the service provider identifier, the execution server searches for the service party identifier corresponding to the service provider resource invocation interface name.

The maximum number of calls of the preset resource call request is the preset maximum number of call times of the resource call request in the preset time range corresponding to the service party identifier. For example, the maximum number of calls for a preset resource call request is 20000.

When the number of resource invocation requests corresponding to the service provider identifier is smaller than the maximum number of invocations of the preset resource invocation request corresponding to the service provider identifier, the execution server may currently process the resource invocation request corresponding to the service party identifier, and then continue to perform server search and The servant resource invokes the servant ID corresponding to the interface name.

In the above-mentioned open platform control method, before the resource call request is controlled by limiting the number of task threads corresponding to the service provider identifier, the resource call request corresponding to the service party identifier in the resource call request received in the preset preset time range is counted. The number of the resource call requests is compared with the maximum number of calls of the preset resource call request corresponding to the service party identifier, and the control of the hot resource call request is implemented. Combined with the method of limiting the number of task threads corresponding to the service party identifier, the resource call request is further controlled, thereby further improving the stability of the open platform.

In one of the embodiments, as shown in FIG. 5, step 212 includes:

Step 502: The execution server forwards the resource call request to the service party corresponding to the service party identifier by using the task thread.

After the execution server determines the service party identifier corresponding to the received resource call request and creates a task thread corresponding to the resource call request, the task thread forwards the received resource call request carrying the server resource call interface name to the task thread. The servant corresponding to the servant.

Step 504: The execution server acquires an execution result of the interface function corresponding to the service provider resource call interface name.

After receiving the resource invocation request sent by the open platform and carrying the interface name of the service provider resource, the service party executes the interface function corresponding to the interface name of the service party resource, and returns the execution result to the open platform.

It should be understood that although the various steps in the flowcharts of FIGS. 2-5 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in Figures 2-5 may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, these sub-steps or stages The order of execution is not necessarily performed sequentially, but may be performed alternately or alternately with at least a portion of other steps or sub-steps or stages of other steps.

In one of the embodiments, as shown in FIG. 6, an open platform control system is provided, the system including a load balancing server 602 and an execution server 604, wherein:

The load balancing server 602 is configured to receive a resource invocation request initiated by the caller, where the resource invocation request carries the name of the interface of the service party resource, and allocates a resource invoking request to the execution server according to the preset load balancing algorithm;

The execution server 604 is configured to receive a resource call request allocated by the load server, search for a service party identifier corresponding to the service provider resource call interface name, and count the number of concurrent task threads corresponding to the service party identifier, and if the service party identifier corresponds to the concurrent The number of task threads is less than the number of the first preset maximum concurrent task threads corresponding to the service party identifier, and the task thread corresponding to the service party identifier is created, and the task call is executed by the task thread to execute the resource call request initiated by the caller. The result is returned to the caller.

In one embodiment, the load balancing server 602 is further configured to count the number of current concurrent task threads of each execution server; if the number of current concurrent threads of the execution server is less than the second preset maximum task thread corresponding to the execution server Count, calculate the task thread availability rate of the execution server; determine the execution server corresponding to the maximum task thread availability rate according to the task thread availability rate of each execution server; and allocate the resource call request to the task thread maximum rate corresponding execution server.

In one embodiment, the execution server 604 is further configured to count the number of resource call requests corresponding to the service party identifier in the resource call request received within the preset time range; and if the resource identifier corresponding to the service party identifier is requested by the server If the number of times is less than the maximum number of calls of the preset resource call request corresponding to the servant identifier, the servant identifier corresponding to the servant resource call interface name is searched for.

In one of these embodiments, the servant identification is a domain name or an IP address.

In one embodiment, the execution server 604 is further configured to forward the resource invocation request to the server corresponding to the server identifier by using the task thread; and obtain the execution result of the interface function corresponding to the server resource invocation interface name by the server. .

For specific definitions of the open platform control system, reference may be made to the above definition of the open platform control method, and details are not described herein again.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in FIG. The computer device includes a processor, memory, and network interface coupled by a system bus. Among them, the processor is used to provide computing and control capabilities to support the operation of the entire server. The memory includes a nonvolatile storage medium and an internal memory. The non-volatile storage medium can be a non-transitory computer readable storage medium. An operating system and computer readable instructions are stored in the non-volatile storage medium, the computer readable instructions being executed by the processor to implement an open platform control method. The internal memory provides an environment for the operation of operating systems and computer readable instructions in a non-volatile storage medium. The network interface is used for communicating with an external server or terminal through a network connection, for example, receiving a resource call request initiated by the caller, forwarding the resource call request to the service party, and receiving the execution result of the resource call by the service party, and returning the execution result. Give the initiator and so on. The server can be implemented with a stand-alone server or a server cluster consisting of multiple servers. It will be understood by those skilled in the art that the structure shown in FIG. 7 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the server to which the solution of the present application is applied. The specific server may include a ratio. More or fewer components are shown in the figures, or some components are combined, or have different component arrangements.

A computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executed by the processor such that the one or more processors perform the following steps:

The load balancing server receives the resource invocation request initiated by the caller, and the resource invoking request carries the name of the interface of the server resource;

The load balancing server allocates a resource call request to the execution server according to a preset load balancing algorithm;

Execute server statistics and the number of concurrent task threads corresponding to the service party identifier;

If the number of concurrent task threads corresponding to the service party identifier is less than the number of the first preset maximum concurrent task threads corresponding to the service party identifier, the execution server creates a task thread corresponding to the resource call request;

The execution server utilizes the task thread to execute the resource invocation request initiated by the caller; and

The execution server returns the execution result of the resource call request to the caller.

In one embodiment, the processor performs a step of the load balancing server to allocate a resource call request to the execution server according to a preset load balancing algorithm, including:

The load balancing server counts the number of current concurrent task threads of each execution server;

If the number of the current concurrent task threads of the execution server is less than the number of the second preset maximum concurrent task threads corresponding to the execution server, calculating the task thread availability rate of the execution server;

Determining an execution server corresponding to a maximum task thread availability rate according to a task thread availability rate of each execution server; and

Allocating a resource call request to an execution server corresponding to the highest task availability rate of the task thread.

In one of these embodiments, the processor further implements the following steps when executing the computer readable instructions:

Execute server statistics and the number of concurrent task threads corresponding to the service party identifier; and

If the number of concurrent task threads corresponding to the servant identifier is equal to the number of the first preset maximum concurrent task threads corresponding to the servant identifier, sending a prompt resource call request rejection message to the caller, so that the caller resends the resource call request.

Executing the number of resource invocation requests corresponding to the service party identifier in the resource call request received by the server in the preset time range; and

If the number of resource invocation requests corresponding to the service provider identifier is less than the maximum number of invocations of the preset resource invocation request corresponding to the service provider identifier, the execution server searches for the service party identifier corresponding to the service provider resource invocation interface name.

The execution server forwards the resource invocation request to the service party corresponding to the service party identifier by using the task thread; and

The execution server acquires the execution result of the interface function corresponding to the service provider resource call interface name.

One or more non-volatile storage media storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the following steps:

In one of the embodiments, when the computer readable instructions are executed by the processor, the following steps are further implemented: the load balancing server counts the number of current concurrent task threads of each execution server;

In one of these embodiments, the computer readable instructions, when executed by the processor, also implement the following steps:

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by computer-readable instructions for instructing related hardware, and the computer readable instructions can be stored in a non-volatile computer. The readable storage medium, which when executed, may include the flow of an embodiment of the methods as described above. Any reference to a memory, storage, database or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain. Synchlink DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The technical features of the above-described embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, All should be considered as the scope of this manual.

The above-mentioned embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the claims. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present application. Therefore, the scope of the invention should be determined by the appended claims.

Claims

An open platform control method includes:

The load balancing server receives a resource invocation request initiated by the caller, where the resource invoking request carries the server name of the calling party resource;

The load balancing server allocates the resource invoking request to the execution server according to a preset load balancing algorithm;

The execution server searches for a service party identifier corresponding to the service provider resource call interface name;

The execution server collects the number of concurrent task threads corresponding to the service party identifier;

If the number of concurrent task threads corresponding to the service provider identifier is less than the number of the first preset maximum concurrent task threads corresponding to the service provider identifier, the execution server creates a task thread corresponding to the resource call request;

Executing, by the execution server, the resource invoke request initiated by the caller by using the task thread;

And the execution server returns an execution result of the resource call request to the caller.
The method according to claim 1, wherein the load balancing server allocates the resource invoking request to the execution server according to a preset load balancing algorithm, including:

The load balancing server collects the number of current concurrent task threads of each execution server;

Calculating a task thread availability rate of the execution server if the number of current concurrent task threads of the execution server is less than a second preset maximum number of concurrent task threads corresponding to the execution server; and

Determining, according to the task thread availability rate of each execution server, an execution server corresponding to a maximum task thread availability rate;

Allocating a resource call request to an execution server corresponding to the highest task availability rate of the task thread.
The method of claim 1 further comprising:

The execution server collects the number of concurrent task threads corresponding to the service party identifier; and

And if the number of concurrent task threads corresponding to the servant identifier is equal to the number of the first preset maximum concurrent task threads corresponding to the servant identifier, sending a prompt resource call request rejection message to the caller, so that The caller resends the resource call request.
The method according to claim 1, wherein before the execution server searches for the service party identifier corresponding to the service provider resource call interface name, the method further includes:

The execution server counts the number of resource call requests corresponding to the service party identifier in the resource call request received within the preset time range; and

If the number of resource invocation requests corresponding to the service provider identifier is less than the maximum number of calls of the preset resource invocation request corresponding to the service provider identifier, the execution server searches for a service party corresponding to the service provider resource call interface name. Logo.
The method according to claim 1, wherein the execution server uses the task thread to execute the resource invocation request initiated by the caller, including:

The execution server forwards the resource invocation request to a service party corresponding to the service party identifier by using the task thread; and

The execution server acquires an execution result of the interface function corresponding to the server resource call interface name by the server.
An open platform control system comprising:

a load balancing server, configured to receive a resource invocation request initiated by the caller, where the resource invocation request carries a service party resource to invoke an interface name, and allocates the resource invoking request to the execution server according to a preset load balancing algorithm;

An execution server, configured to receive the resource call request allocated by the load server, search for a service party identifier corresponding to the service provider resource call interface name, and count the number of concurrent task threads corresponding to the service party identifier, if the service is The number of the concurrent task threads corresponding to the party identifier is smaller than the number of the first preset maximum concurrent task threads corresponding to the service party identifier, and the task thread corresponding to the service party identifier is created, and the call is performed by using the task thread. A resource invocation request initiated by the party returns the execution result of the resource invoking request to the calling party.
The system according to claim 6, wherein the load balancing server is further configured to count the number of current concurrent task threads of each execution server; if the number of current concurrent threads of the execution server is smaller than the execution And calculating, by the server, a second preset maximum number of task threads, calculating a task thread availability rate of the execution server; and determining, according to the task thread availability rate of each execution server, an execution server corresponding to a maximum task thread availability rate Assigning a resource call request to an execution server corresponding to the maximum task rate availability.
The system according to claim 6, wherein the execution server is further configured to: use the execution server to count the number of concurrent task threads corresponding to the service party identifier; and concurrently correspond to the service party identifier If the number of task threads is equal to the number of the first preset maximum concurrent task threads corresponding to the service provider identifier, the prompting resource call request rejection message is sent to the caller, so that the caller resends the resource call request.
The system according to claim 6, wherein the execution server is further configured to count the number of resource call requests corresponding to the service party identifier in the resource call request received within the preset time range; If the number of the resource call requests corresponding to the servant identifier is smaller than the maximum number of call times of the preset resource call request corresponding to the servant identifier, the servant identifier corresponding to the servant resource call interface name is searched for.
The system according to claim 6, wherein the execution server is further configured to forward the resource invocation request to a service party corresponding to the service party identifier by using the task thread; and acquire the service party Execute the execution result of the interface function corresponding to the servant resource call interface name.
A computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executed by the one or more processors to cause the one or more The processors perform the following steps:

The load balancing server receives a resource invocation request initiated by the caller, where the resource invoking request carries the server name of the calling party resource;

The load balancing server allocates the resource invoking request to the execution server according to a preset load balancing algorithm;

The execution server searches for a service party identifier corresponding to the service provider resource call interface name;

The execution server collects the number of concurrent task threads corresponding to the service party identifier;

If the number of concurrent task threads corresponding to the service provider identifier is less than the number of the first preset maximum concurrent task threads corresponding to the service provider identifier, the execution server creates a task thread corresponding to the resource call request;

Executing, by the execution server, the resource invoke request initiated by the caller by using the task thread;

And the execution server returns an execution result of the resource call request to the caller.
The computer device according to claim 11, wherein the step of the processor performing the load balancing server to allocate the resource invoking request to the execution server according to a preset load balancing algorithm comprises:

The execution server collects the number of concurrent task threads corresponding to the service party identifier;

Calculating a task thread availability rate of the execution server if the number of current concurrent task threads of the execution server is less than a second preset maximum number of concurrent task threads corresponding to the execution server; and

Determining an execution server corresponding to a maximum task thread availability rate according to the task thread availability rate of each execution server;

Allocating a resource call request to an execution server corresponding to the highest task availability rate of the task thread.
The computer apparatus according to claim 11, wherein said processor further performs the following steps when said computer readable instructions are executed:

The execution server collects the number of concurrent task threads corresponding to the service party identifier; and

And if the number of concurrent task threads corresponding to the servant identifier is equal to the number of the first preset maximum concurrent task threads corresponding to the servant identifier, sending a prompt resource call request rejection message to the caller, so that The caller resends the resource call request.
The computer apparatus according to claim 11, wherein said processor further performs the following steps when said computer readable instructions are executed:

The execution server counts the number of resource call requests corresponding to the service party identifier in the resource call request received within the preset time range; and

If the number of resource invocation requests corresponding to the service provider identifier is less than the maximum number of calls of the preset resource invocation request corresponding to the service provider identifier, the execution server searches for a service party corresponding to the service provider resource call interface name. Logo.
The computer device according to claim 11, wherein the step of executing, by the processor, the execution of the resource call request initiated by the caller by the task thread comprises:

The execution server forwards the resource invocation request to a service party corresponding to the service party identifier by using the task thread; and

The execution server acquires an execution result of the interface function corresponding to the server resource call interface name by the server.
One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:

The load balancing server receives a resource invocation request initiated by the caller, where the resource invoking request carries the server name of the calling party resource;

The load balancing server allocates the resource invoking request to the execution server according to a preset load balancing algorithm;

The execution server searches for a service party identifier corresponding to the service provider resource call interface name;

The execution server collects the number of concurrent task threads corresponding to the service party identifier;

If the number of concurrent task threads corresponding to the service provider identifier is less than the number of the first preset maximum concurrent task threads corresponding to the service provider identifier, the execution server creates a task thread corresponding to the resource call request;

Executing, by the execution server, the resource invoke request initiated by the caller by using the task thread;

And the execution server returns an execution result of the resource call request to the caller.
The storage medium of claim 16 wherein said computer readable instructions are further executed by said processor to perform the following steps:

The execution server collects the number of concurrent task threads corresponding to the service party identifier; and

Calculating a task thread availability rate of the execution server if the number of current concurrent task threads of the execution server is less than a second preset maximum number of concurrent task threads corresponding to the execution server; and

Determining, according to the task thread availability rate of each execution server, an execution server corresponding to a maximum task thread availability rate;

Allocating a resource call request to an execution server corresponding to the highest task availability rate of the task thread.
The storage medium of claim 16 wherein said computer readable instructions are further executed by said processor to perform the following steps:

The execution server collects the number of concurrent task threads corresponding to the service party identifier; and

And if the number of concurrent task threads corresponding to the servant identifier is equal to the number of the first preset maximum concurrent task threads corresponding to the servant identifier, sending a prompt resource call request rejection message to the caller, so that The caller resends the resource call request.
The storage medium of claim 16 wherein said computer readable instructions are further executed by said processor to perform the following steps:

The execution server counts the number of resource call requests corresponding to the service party identifier in the resource call request received within the preset time range; and

If the number of resource invocation requests corresponding to the service provider identifier is less than the maximum number of calls of the preset resource invocation request corresponding to the service provider identifier, the execution server searches for a service party corresponding to the service provider resource call interface name. Logo.
The storage medium of claim 16 wherein said computer readable instructions are further executed by said processor to perform the following steps:

Executing, by the execution server, the resource thread to forward the resource invocation request to a service party corresponding to the service party identifier; and

The execution server acquires an execution result of the interface function corresponding to the server resource call interface name by the server.