Remote interface agent calling method and device, computer equipment and storage medium

Abstract

The invention discloses a remote interface agent calling method and device, computer equipment and a storage medium. The method comprises the steps of responding to a remote interface calling event; storing the parameter information of the remote interface and the execution state of the remote interface in a task database, and initializing the execution state into a to-be-executed state; calling and executing the remote interface according to the parameter information agent, if the remote interface is successfully executed, modifying the execution state of the remote interface into an executed state, and returning and outputting an execution result of the remote interface; and responding to a timed task trigger event to obtain parameter information of the remote interfaces in a to-be-executed state in the task database, and re-executing the step of executing the remote interfaces according to the parameter information agent calling for the remote interfaces. According to the method and the device, queued task scheduling is performed on the remote interface calling event, the remote interface calling is buffered and balanced, and the data communication efficiency of cross-server super remote interface calling in a distributed service cluster can be improved.

Description

technical field [0001] The embodiments of the present application relate to the field of computer network communication, and in particular, to a remote interface proxy calling method, device, computer equipment, and storage medium. Background technique [0002] In the Internet industry, the microservice architecture is very popular. Even if it is just a small business module or product line, the bottom layer is composed of many systems. The interaction between the systems is through remote calls. Many, so the interaction between them is like a network, and the complexity of the interaction relationship can be imagined. At the same time, due to frequent problems such as network delays, network fluctuations, packet loss, and server exceptions, the interactive calls between services become unreliable and prone to failure. At this time, retrying is a relatively common solution. Through continuous retrying, the execution is finally successful. However, given the fact of the mes...

AI Technical Summary

Problems solved by technology

In many cases, after a network problem occurs, it cannot be recovered in a short time, and it will take a long time

At this time, it is useless to retry 3 times at one time. Since the retry 3 times failed, it can only be treated as a failure in the end.

[0006] (3) They are all retried in the memory. The number of retries and whether to retry are calculated in the memory. Once the system restarts or crashes, the previous retry information will be lost, making it impossible to continue retrying

However, for a system based on the agile development model, it is very common for the system to go online and restart the system every three days, or even once a day. In this case, memory-based retries cannot meet the requirements of the system.

Images