CN111737022A - Interface calling method, system, equipment and medium based on micro-service - Google Patents

Interface calling method, system, equipment and medium based on micro-service Download PDF

Info

Publication number
CN111737022A
CN111737022A CN201910943957.2A CN201910943957A CN111737022A CN 111737022 A CN111737022 A CN 111737022A CN 201910943957 A CN201910943957 A CN 201910943957A CN 111737022 A CN111737022 A CN 111737022A
Authority
CN
China
Prior art keywords
interface
called
calling
response information
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN201910943957.2A
Other languages
Chinese (zh)
Other versions
CN111737022B (en
Inventor
吴风浪
杨超
孙占龙
杨建强
肖善松
金迪
王松林
严杨
马云林
杨小刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Century Trading Co Ltd, Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN201910943957.2A priority Critical patent/CN111737022B/en
Publication of CN111737022A publication Critical patent/CN111737022A/en
Application granted granted Critical
Publication of CN111737022B publication Critical patent/CN111737022B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/541—Client-server
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/544—Remote
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The invention discloses a method, a system, equipment and a medium for calling an interface based on micro-service, wherein the method comprises the following steps: when receiving task request information sent by a client, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters respectively corresponding to each interface to be called; determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to the server based on the interface calling mode; and when target response information corresponding to the target interface calling request returned by the server is received, sending the target response information to the client. According to the technical scheme of the embodiment of the invention, the information returned by the server is processed through the gateway, and the target response information returned by the target interface is sent to the client, so that the interaction complexity between the client and the server is reduced, and the technical effect of the interface calling efficiency is improved.

Description

Interface calling method, system, equipment and medium based on micro-service
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a method, a system, equipment and a medium for calling an interface based on micro-service.
Background
In the same type of service system, different systems usually include the same or similar service function modules, and the conventional solution is to refine similar functions into micro service interfaces, and implement different services by calling each micro service interface.
If at least two micro service interfaces need to be called in series for realizing a certain service, optionally, 3 micro service interfaces, that is, a front-back dependency relationship exists between the 3 micro service interfaces. In the prior art, referring to fig. 1, a caller (client) first sends an interface parameter corresponding to a micro service interface 1 to the micro service interface 1, and when the micro service interface 1 returns a value, the caller sends an interface parameter corresponding to a micro service interface 2 to the micro service interface 2, and so on, and when the client receives a return value corresponding to a micro service interface 3, the service is completed. If at least two micro-service interfaces need to be called in parallel for realizing a certain service, for example, when a page rendering service is realized, a plurality of micro-service interfaces need to be called in parallel. According to the scheme in the prior art, referring to fig. 2, when a page is determined to be rendered, interface parameters corresponding to each micro service interface are determined, a thread pool is established at a client, the interface parameters are sent to the corresponding micro service interfaces, return values returned by the micro service interfaces are received, and the page is rendered based on the return values.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
when the interfaces are called serially, the client needs to confirm the return value of each interface in real time, so that the complexity of accessing each interface is increased, and the technical problem of low efficiency exists. Once the parallel call interfaces are determined, the client needs to establish a thread pool corresponding to each interface parameter each time, which has the technical problems of large memory occupation and low efficiency.
Disclosure of Invention
The invention provides an interface calling method, system, equipment and medium based on micro-service, which aims to reduce the complexity of accessing each interface and improve the calling efficiency of calling each interface.
In a first aspect, an embodiment of the present invention provides a method for invoking an interface based on a microservice, where the method is applied to a gateway, and includes:
when receiving task request information sent by a client, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters corresponding to each interface to be called; the at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message;
determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to a server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called;
and when target response information corresponding to the target interface calling request returned by the server is received, sending the target response information to the client.
In a second aspect, an embodiment of the present invention further provides a microservice-based interface invoking system, where the system is configured in a gateway, and includes:
the system comprises a calling interface determining module, a task processing module and a task processing module, wherein the calling interface determining module is used for determining at least one interface to be called corresponding to a task request message when the task request message sent by a client is received, and acquiring interface calling parameters corresponding to each interface to be called; the at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message;
the interface calling parameter sending module is used for determining an interface calling mode corresponding to the task request message and sending an interface calling request for each interface to be called to a server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called;
and the target response information sending module is used for sending the target response information to the client when receiving the target response information corresponding to the target interface calling request returned by the server.
In a third aspect, an embodiment of the present invention further provides an apparatus, where the apparatus includes:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a microservice-based interface invocation method as described in any of the embodiments of the present invention.
In a fourth aspect, embodiments of the present invention further provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform the microservice-based interface invocation method according to any of the embodiments of the present invention.
According to the technical scheme of the embodiment of the invention, when task request information sent by a client is received, at least one interface to be called corresponding to the task request information is determined, and interface calling parameters respectively corresponding to the interfaces to be called are obtained; wherein, at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message; determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to the server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called; when target response information corresponding to a target interface calling request returned by a server is received, the target response information is sent to a client, the technical problems that in the prior art, when interfaces are called in series and/or in parallel, the client needs to process the response information returned by the server each time until the response information returned by all the interfaces is received, the complexity of interface access is increased, and the efficiency is low are solved, the information returned by the server is processed through a gateway, the target response information returned by the target interface is sent to the client, the complexity of interaction between the client and the server is reduced, and the technical effect of interface calling efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, a brief description is given below of the drawings used in describing the embodiments. It should be clear that the described figures are only views of some of the embodiments of the invention to be described, not all, and that for a person skilled in the art, other figures can be derived from these figures without inventive effort.
FIG. 1 is a diagram illustrating interaction between a client and a server when interfaces are serially invoked in the prior art;
FIG. 2 is a schematic diagram illustrating interaction between a client and a server when interfaces are called in parallel in the prior art;
fig. 3 is a schematic flowchart of an interface calling method based on microservice according to an embodiment of the present invention;
fig. 4 is another schematic flow chart illustrating a microservice-based interface invoking method according to a second embodiment of the present invention;
fig. 5 is a schematic diagram of interaction between a client and a server according to a second embodiment of the present invention;
fig. 6 is another schematic flow chart illustrating a microservice-based interface invoking method according to a second embodiment of the present disclosure;
fig. 7 is a schematic diagram of interaction between a client and a server according to a second embodiment of the present invention;
fig. 8 is a schematic diagram illustrating scope of interface call parameter scope in micro-service scheduling according to a second embodiment of the present invention;
fig. 9 is another schematic diagram illustrating scope of interface call parameter scope in micro-service scheduling according to a second embodiment of the present invention;
fig. 10 is another flowchart illustrating a method for invoking an interface based on a microservice according to a third embodiment of the present invention;
fig. 11 is a schematic structural diagram of a microservice-based interface invocation system according to a fourth embodiment of the present invention;
fig. 12 is a schematic structural diagram of an apparatus according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 3 is a schematic flowchart of an interface calling method based on a microservice according to an embodiment of the present invention, where the embodiment is applicable to a case of calling a microservice interface, and the method may be applied to a gateway, and may be executed by an interface calling system based on a microservice, and the system may be implemented in a form of software and/or hardware.
As shown in fig. 3, the method of this embodiment includes:
s310, when receiving task request information sent by a client, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters corresponding to the interfaces to be called respectively.
The task request information may be understood as request information corresponding to a user trigger operation. For example, when a user triggers a certain control on the client, the client may generate task request information corresponding to the triggering operation. The at least one call interface can be understood as a logical data transmission protocol. The interface call parameter may be understood as a key to call each interface.
Specifically, when it is detected that the user triggers the control on the client, the client may generate task request information corresponding to the trigger operation, and send the task request information to the gateway. The gateway can determine an interface to be called for executing the task request information according to the task request information. After the to-be-called interfaces corresponding to the task request information are determined, interface calling parameters corresponding to the interfaces are also required to be obtained so as to call the interfaces to be called.
It should be noted that, when the manner of calling the interfaces is different, the interface calling parameters corresponding to the interfaces to be called are obtained differently.
Optionally, the interface calling mode is interface serial calling, and obtaining interface calling parameters corresponding to each interface to be called respectively includes: reading interface calling parameters which are stored in advance and respectively correspond to each interface to be called from a configuration center; the configuration center stores interface calling parameters corresponding to each interface in advance.
It should be noted that the interface call parameters corresponding to each interface may be predetermined, and the interface call parameters are stored in the gateway, so that when the gateway receives the task request information, the task request information may be analyzed, and after the interface to be called corresponding to the task request information is determined, the interface call parameters corresponding to each interface to be called are obtained from the configuration center.
Specifically, when the interface to be called, which needs to be called in response to the task request information, is determined according to the task request information, and the interface calling mode is serial interface calling, the interface calling parameters corresponding to each interface to be called can be acquired from all interface parameter information stored in the configuration center.
It should be further noted that, each task request information, the interface to be called responding to the task request information, and the interface calling parameter may also be bound in advance, so that the gateway receives the task information, searches whether the task request information is stored from the configuration center, and if so, may directly determine the interface to be called and the interface calling parameter according to the binding relationship. For example, if the task request information is a, the interfaces to be called corresponding to the task request information a are a respectively1、A2、A3Then, all the interfaces to be called corresponding to the task request information a may be taken as a whole, and the interfaces to be called a may be established1、A2、A3And the mapping relation table is used for mapping the parameters of the interface to be called, so that when the gateway receives the task request information sent by the client, the interface to be called corresponding to the task request information and the interface calling parameters are searched from the mapping relation table stored in the configuration center.
Of course, the interface calling method further includes interface parallel calling, and then the interface calling parameters respectively corresponding to the interfaces to be called are obtained, including: according to the task request information, determining interfaces to be called corresponding to the task request information, and acquiring interface calling parameters corresponding to each interface to be called; and/or reading an interface calling parameter corresponding to the interface to be called carried in the task request information.
It can be understood that, when the calling mode of the interface is parallel calling, acquiring the interface calling parameter corresponding to each interface to be called includes at least two modes. The first mode may be that the client sends task request information to the gateway, and the gateway performs protocol analysis on the received task request information, may determine interfaces to be called corresponding to the task request information, and configures interface call parameters corresponding to each interface to be called from the configuration center. Another way may be that, before the client sends the task request information to the gateway, the client determines in advance the interface to be called corresponding to the task information and the corresponding interface calling parameter. The advantage of this is that it avoids the failure to configure the interface call parameters corresponding to the task request information from the configuration center due to the flexibility of parallel calling.
And S120, determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to the server based on the interface calling mode.
The interface calling mode may include: the interface is called in parallel, or the interface is called in series. The interface calling request comprises interface calling parameters corresponding to each interface to be called.
Specifically, after the gateway receives the task request information, the gateway may determine, according to the identifier in the task request information, an interface calling manner for executing the task request information, that is, whether to call each interface to be called is an interface serial call or an interface parallel call. And sending an interface calling request for calling each interface to be called to the server according to the determined interface calling mode.
When the calling modes of the interfaces are different, the mode of sending the interface calling parameters to each interface to be called is also different.
Optionally, when the interfaces to be called are called in series, the interface calling parameters may be sent to the interfaces to be called in a manner that interface calling requests for the interfaces to be called are sequentially sent to the server in a serial manner according to the dependency relationship between the interfaces to be called.
The serial calling of each interface to be called can be understood as that a front-back dependency relationship exists between the interfaces to be called. Illustratively, if the interfaces to be called are A respectively1、A2、A3And A is1、A2、A3There is a context dependency between them, i.e. when the gateway will interface with interface a1The corresponding interface parameters are sent to the A1 interface and received to the A interface1When the response information is returned, the interface A can be connected with2Corresponding interface parameters are sent to A2And the interfaces receive response information returned by each calling interface in the same way.
Specifically, when it is determined that the calling mode of the interface is serial calling, the front-back dependency relationship between the interfaces to be called can be determined, that is, the front-back sequence of sending the interface calling parameters to the interfaces to be called is determined. According to the front-back sequence of sending the interface calling parameters, sending the interface calling parameters corresponding to the first interface to be called in the server, when the gateway receives response information returned by the first interface to be called and identification in the response information is that the next interface parameter information is sent, sending the interface calling parameters corresponding to the second interface to be called in the server, and sending the interface calling parameters corresponding to the third interface to be called in the server until the response information returned by the second interface to be called is received, and sending the interface calling parameters to the corresponding interfaces to be called in sequence according to the mode so that the interfaces to be called return corresponding response information.
Optionally, when the interfaces to be called are called in parallel, the manner of sending the interface calling parameters to the interfaces to be called may be: and establishing a thread pool corresponding to each interface calling parameter, and sending an interface calling request for each interface to be called to the server in parallel based on the thread pool.
Specifically, when the gateway determines the interface calling parameters corresponding to each interface to be called, since there is no front-back dependency relationship between the interfaces to be called, the interface calling parameters corresponding to each interface to be called can be simultaneously sent to each interface to be called in the server. In order to improve the efficiency of calling each interface, the request merging module in the gateway may establish a thread pool corresponding to each interface to be called according to the interface calling parameter, and send an interface calling request to each interface to be called to the server based on the thread pool, that is, send the interface calling parameter to the interface to be called in the server. The advantage of establishing the thread pool in the gateway is that when at least one client sends the same task request, the task request information can be processed only by establishing a group of thread pools at the gateway without establishing the thread pools in the clients respectively, and the complexity of processing the task request information by the client is reduced.
Illustratively, in a page rendering service scene, a client needs to acquire response information returned by a plurality of micro service interfaces to implement rendering of a whole page. The client can generate task request information corresponding to page rendering, the task request information is sent to the gateway, the gateway analyzes the received task request information to obtain interface calling parameters corresponding to the task request information, optionally, the interface calling parameters corresponding to the calling page frame, the interface calling parameters corresponding to the calling page content and the like, thread pools corresponding to the interface calling parameters are respectively established, the interface parameters are sent to the server based on the thread pools to obtain the page frame and the page content, and page rendering is achieved based on response information returned by the server.
In this embodiment, the interface call parameters corresponding to each interface are stored in the configuration center in the gateway, and the thread pool corresponding to each interface call parameter is established at the gateway, so as to avoid the problem that when the client side manages each interface parameter, the client side needs to establish the thread pool as long as the client side initiates a task request, configure the interface call parameters corresponding to the task request, thereby increasing the workload of the client side for managing each parameter, and when each client side needs to establish the thread pool for the same task request information, the problem of resource waste exists, and simultaneously, the interface access efficiency is reduced, and the gateway has the advantages that when the same task request sent by at least one client side is received, the task request information sent by each client side can be responded only by establishing a group of thread pools at the gateway, the efficiency of calling each interface is improved.
And S130, when target response information corresponding to the target interface calling request returned by the server is received, sending the target response information to the client.
Optionally, when the interface calling mode is serial calling and the interface calling requests of the interfaces to be called are sequentially sent to the server based on the dependency relationship among the interfaces to be called, and when response information corresponding to the last interface calling request returned by the server is received, the response information corresponding to the last interface calling request is used as target response information; and sending the target response information to the client.
The gateway can generate interface calling requests corresponding to the interfaces to be called and sequentially send the interface calling requests to the interfaces to be called. And when the interface to be called has a front-back dependency relationship, taking the interface calling request corresponding to the calling of the last interface to be called as the calling request of the last interface. The target response information is response information returned by the interface to be called corresponding to the last interface calling request, namely, the response information returned by the last interface to be called after the server receives the last interface calling request.
Illustratively, the interfaces for serial calls are A respectively1、A2、A3. When interface A1When the response information is returned, the gateway can be connected with the interface A2The corresponding interface calling parameter is sent to the interface A2When receiving interface A2When the response information is returned, the gateway will communicate with the interface A3The corresponding interface parameter is sent to interface A3Until the gateway receives interface A3And returning the response information. At this time, the interface A can be connected with3The corresponding interface calling request is used as the last interface calling request, and the interface A is used3The returned response information is used as target response information. And the gateway sends the received target response information to the client, namely the client receives the target response information fed back by the server.
Optionally, the interface calling mode is parallel calling, and after sending each interface calling parameter to the server based on the thread pool, receiving response information corresponding to each interface calling request returned by the server, taking a set of each response information as target response information, and sending the target response information to the client.
Specifically, after sending each interface call parameter to the server based on the thread pool, the server may process each received interface call parameter, determine response information corresponding to each interface to be called, and return the response information to the gateway. And when the gateway receives the response information returned by all the interfaces, the gateway takes the set of each response information as target response information, namely packages each corresponding information as the target response information, and sends the target response information to the client. The advantage of using the set of each response message as the target response message is that the response messages returned by each interface to be called can be integrated and then sent to the client, thereby avoiding the technical problem that the interaction complexity between the client and the server is increased because the server returns the response messages and then sends the response messages to the server.
On the basis, when the data volume of the target response information is detected to be larger than a preset threshold value, a compression mechanism is started to compress the target response information and then send the compressed target response information to the client.
It can be understood that when the amount of the target response information is large, the transmission efficiency of the gateway for sending the target response information to the client may be affected, and a compression mechanism is further arranged in the gateway. When the data volume of the target response information received by the gateway is detected to be larger than the preset threshold value, a compression mechanism is started to compress the target response information so as to reduce the data volume of the target response information, and therefore the transmission efficiency of the gateway for sending the target response information to the client is improved.
Certainly, the gateway is also provided with the timeout mechanism, so that when the gateway does not receive the response information within the preset time, the gateway can send the interface calling parameter corresponding to the interface to the corresponding interface again, and the problem that the response information is waited all the time and the interface calling efficiency is reduced is solved.
According to the technical scheme of the embodiment of the invention, when task request information sent by a client is received, at least one interface to be called corresponding to the task request information is determined, and interface calling parameters respectively corresponding to the interfaces to be called are obtained; wherein, at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message; determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to the server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called; when target response information corresponding to a target interface calling request returned by a server is received, the target response information is sent to a client, the technical problems that in the prior art, when interfaces are called in series and/or in parallel, the client needs to process the response information returned by the server each time until the response information returned by all the interfaces is received, the complexity of interface access is increased, and the efficiency is low are solved, the information returned by the server is processed through a gateway, the target response information returned by the target interface is sent to the client, the complexity of interaction between the client and the server is reduced, and the technical effect of interface calling efficiency is improved.
Example two
Fig. 4 is another flowchart illustrating a method for invoking an interface based on a microservice according to a second embodiment of the present invention; as shown in fig. 4, the method includes:
and S410, the client sends task request information to the gateway.
For clearly introducing the technical solution of the embodiment of the present invention, the schematic interaction diagram between the client and the server when the micro service interface is called in fig. 5 may be combined to understand the solution.
It should be noted that, determining the interface call parameters corresponding to each interface and establishing the thread pool corresponding to each interface call parameter are all completed in the gateway system, that is, all integrated in the gateway and isolated from the specific service.
Specifically, after the user triggers the control on the client, task request information corresponding to the trigger operation may be generated, and the task request information is sent to the gateway. Namely, the caller (client) sends the task request information to the chained call module in the gateway.
And S420, the gateway determines the interface to be called corresponding to the task request information according to the received task request information, acquires the interface calling parameter corresponding to the interface to be called from the configuration center and sends the interface calling parameter to the server.
The gateway determines an interface to be called corresponding to the task request information according to the received task request information, and obtains the interface calling parameter corresponding to the interface to be called from all interface calling parameters pre-stored in the configuration center, or searches whether the request information corresponding to the current task request information is stored from the interface calling parameters pre-stored in the configuration center and corresponding to different request information. If the interface calling parameter exists, the corresponding interface to be called and the interface calling parameter can be directly obtained.
That is to say, when the chained call module receives the task request information, the corresponding interface to be called may be determined according to the task request information, and the interface call parameter corresponding to the interface to be called may be obtained from the configuration. After the interface calling parameters are obtained, if the dependency relationship exists between the interfaces, the calling parameters corresponding to the interface 1 can be sent to a server, namely a server; when the gateway receives response information returned by the interface 1 to be called, sending a calling parameter corresponding to the interface 2 to be called to a server; when the gateway receives the response information returned by the interface 2 to be called, the calling parameters corresponding to the interface 3 are sent to the server, and by analogy, the interface calling parameters corresponding to each interface to be called are sent to the server.
And S430, when the gateway receives the response information, sending the next interface calling parameter information to the server until the gateway receives the response information returned by the target interface to be called.
That is to say, each time the gateway receives the response information returned by the server, the gateway sends the next call request, that is, the interface call parameter, to the server, and sends each interface call parameter to the server in sequence in this way until the last interface call parameter is sent to the server, and the response information returned by the server at this time can be used as the target response information.
S440, when the gateway interface returns the response information to the target interface, the target response information is sent to the client.
When the gateway receives the response information corresponding to the last call request, the response information received at this time may be used as the target response information, and the target response information is sent to the client.
The above embodiment is a flow chart of serial calling of an interface. The interface calling mode also comprises interface parallel calling. Fig. 6 is another flowchart illustrating an interface calling method based on microservice according to a second embodiment of the present invention. As shown in fig. 6, the method includes:
and S610, the client sends the task request information to the gateway.
For a clear understanding of the technical solution of the present embodiment, it can be understood by referring to fig. 7.
Specifically, after a control is triggered on a client (caller), the client (caller) may generate task request information corresponding to the trigger operation and send the task request information to the gateway. And the request merging module is arranged in the gateway and can process the task request information.
S620, the gateway acquires the parameter information corresponding to the task request information, establishes thread pools corresponding to the parameter information, and sends the interface calling parameters to the server based on the thread pools.
Specifically, the task request information may carry an interface call parameter corresponding to the interface to be called. When the gateway receives the interface calling parameters and determines to call each interface to be called in parallel, the request merging module in the gateway can establish a thread pool corresponding to each interface calling parameter, and send each interface calling parameter to a server, namely a server based on the established thread pool. That is, all interface call parameters may be sent to the server at the same time.
S630, the gateway receives response information corresponding to each interface to be called returned by the server, and sends each response information to the client as a whole.
After the gateway sends all the interface calling parameters to the server, the server can return response information, namely return values, and send the response information returned by each interface as a whole, namely a set of return values, to the client, so that the client can realize the function corresponding to the trigger operation according to the received set of return values.
On the basis of the above technical solution, it should be noted that interface call parameters corresponding to each interface are pre-stored in a configuration center of the gateway, the interface call parameters are divided into three levels according to the scope of parameter validity, which are respectively named as an activity level, a component level and an action level, and each level is provided with a corresponding level Identifier (ID), that is, an activity ID, a component ID and an action ID. Where the activity level scope is greater than the component level scope, and the component level scope is greater than the action level scope, see fig. 8 and 9. When the gateway determines the interface calling parameters corresponding to the interfaces to be called according to the task request information, the storage positions of the interface calling parameters corresponding to the interfaces to be called in the configuration center can be positioned according to the level identifications.
In this embodiment, when a caller calls a backend service, that is, a server, only a set of interface names and related parameters needs to be introduced, and then the backend requests to merge an interface, that is, after a request merging module arranged in a gateway receives a request, a thread pool is established and a backend service interface is called based on the thread pool, after all service interfaces return data, query results are summarized and returned to a front end, that is, a client in a unified manner, so that the interface calling efficiency is improved, that is, the response efficiency to a user trigger operation is improved.
According to the technical scheme of the embodiment of the invention, when task request information sent by a client is received, at least one interface to be called corresponding to the task request information is determined, and interface calling parameters respectively corresponding to the interfaces to be called are obtained; wherein, at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message; determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to the server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called; when target response information corresponding to a target interface calling request returned by a server is received, the target response information is sent to a client, the technical problems that in the prior art, when interfaces are called in series and/or in parallel, the client needs to process the response information returned by the server each time until the response information returned by all the interfaces is received, the complexity of interface access is increased, and the efficiency is low are solved, the information returned by the server is processed through a gateway, the target response information returned by the target interface is sent to the client, the complexity of interaction between the client and the server is reduced, and the technical effect of interface calling efficiency is improved.
EXAMPLE III
As a preferred embodiment of the foregoing embodiment, fig. 10 is a schematic flowchart of an interface serial call method provided by a third embodiment of the present invention. As shown in fig. 10, the method includes:
and S1001, starting.
The beginning may be understood as that the gateway receives the task request information sent by the client.
S1002, judging whether the calling is one time, if so, executing S1003; if not, S1004.
The gateway analyzes the task request information, and can determine the interface calling mode and the number to be called. When the number of the interfaces to be called is one, determining that the number of the interfaces to be called is one, and executing S1003; if the number of the interfaces to be called is multiple, determining that the number of the interfaces to be called is multiple times of calling, and executing S1004.
And S1003, acquiring the interface calling parameter and sending the interface calling parameter to the server.
According to the task request information, the interface to be called can be determined, the chained call module can configure interface parameter information corresponding to the interface to be called from the configuration center according to the interface to be called, send the interface parameter information to the server, and send the response information to the client when the server returns the response information, that is, S1007 is executed.
And S1004, executing the core service.
Executing the core service may be understood as sending the interface call parameter to the server, where each interface to be called in the server returns corresponding response information.
S1005, judging whether a post action exists, if so, executing S1006; if not, S1007 is executed.
Judging whether the post action exists or not can mean that when the interface to be called of the server returns the response information, whether the response information carries information for sending the next interface calling parameter to the server or not, if so, judging that the post action exists, and executing S1006, and if not, sending the response information returned by the server to the client.
S1006, calling a post action.
It can be understood that the operation of sending the parameter information to the server is continuously performed until each interface calling parameter is sent to the corresponding interface to be called, and target response information returned by the target interface is received.
And S1007, sending the target response information received by the gateway to the client.
Namely, the gateway sends target response information to the client, namely responding to the trigger operation of the user.
According to the technical scheme of the embodiment of the invention, when task request information sent by a client is received, at least one interface to be called corresponding to the task request information is determined, and interface calling parameters respectively corresponding to the interfaces to be called are obtained; wherein, at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message; determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to the server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called; when target response information corresponding to a target interface calling request returned by a server is received, the target response information is sent to a client, the technical problems that in the prior art, when interfaces are called in series and/or in parallel, the client needs to process the response information returned by the server each time until the response information returned by all the interfaces is received, the complexity of interface access is increased, and the efficiency is low are solved, the information returned by the server is processed through a gateway, the target response information returned by the target interface is sent to the client, the complexity of interaction between the client and the server is reduced, and the technical effect of interface calling efficiency is improved.
Example four
Fig. 11 is a schematic structural diagram of an interface calling system based on microservice according to a fourth embodiment of the present invention, where the system is configured in a gateway, and as shown in fig. 11, the system includes: a calling interface determining module 1101, an interface calling parameter sending module 1102 and a target response information sending module 1103.
The calling interface determining module 1101 is configured to, when receiving task request information sent by a client, determine at least one to-be-called interface corresponding to the task request information, and obtain interface calling parameters corresponding to each to-be-called interface; the at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message; an interface call parameter sending module 1102, configured to determine an interface call mode corresponding to the task request message, and send an interface call request for each interface to be called to a server based on the interface call mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called; the target response information sending module 1103 is configured to send the target response information to the client when receiving target response information corresponding to the target interface call request returned by the server.
On the basis of the above technical solutions, the interface calling mode is interface serial calling, and the calling interface determining module includes:
reading interface calling parameters which are stored in advance and respectively correspond to the interfaces to be called from a configuration center; the configuration center stores interface calling parameters corresponding to each interface in advance.
On the basis of the above technical solutions, the interface call parameter sending module is further configured to:
according to the dependency relationship among the interfaces to be called, sequentially sending interface calling requests of the interfaces to be called to a server in a serial mode;
when target response information corresponding to a target interface calling request returned by a server is received, the target response information is sent to the client, and the method comprises the following steps:
when response information corresponding to the last interface calling request returned by the server is received, taking the response information corresponding to the last interface calling request as target response information; and sending the target response information to the client.
On the basis of the technical schemes, the interface calling mode is interface parallel calling; the interface calling parameter sending module is also used for determining an interface to be called corresponding to the task request information according to the task request information and obtaining the corresponding interface; and/or reading an interface calling parameter which is carried in the task request information and corresponds to the interface to be called.
On the basis of the above technical solutions, the interface call parameter sending module is further configured to:
and establishing a thread pool corresponding to each interface calling parameter, and sending an interface calling request for each interface to be called to a server in parallel based on the thread pool.
On the basis of the above technical solutions, the target response information sending module is further configured to:
and receiving response information corresponding to each interface calling request returned by the server, taking a set of each response information as target response information, and sending the target response information to the client.
On the basis of the above technical solutions, the target response information sending module is further configured to:
and when detecting that the data volume of the target response information is larger than a preset threshold value, starting a compression mechanism to compress the target response information and then sending the compressed target response information to the client.
According to the technical scheme of the embodiment of the invention, when task request information sent by a client is received, at least one interface to be called corresponding to the task request information is determined, and interface calling parameters respectively corresponding to the interfaces to be called are obtained; wherein, at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message; determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to the server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called; when target response information corresponding to a target interface calling request returned by a server is received, the target response information is sent to a client, the technical problems that in the prior art, when interfaces are called in series and/or in parallel, the client needs to process the response information returned by the server each time until the response information returned by all the interfaces is received, the complexity of interface access is increased, and the efficiency is low are solved, the information returned by the server is processed through a gateway, the target response information returned by the target interface is sent to the client, the complexity of interaction between the client and the server is reduced, and the technical effect of interface calling efficiency is improved.
The interface calling system based on the micro-service provided by the embodiment of the invention can execute the interface calling method based on the micro-service provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
It should be noted that, the units and modules included in the system are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be realized; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the embodiment of the invention.
EXAMPLE five
Fig. 12 is a schematic structural diagram of an apparatus according to a fifth embodiment of the present invention. FIG. 12 illustrates a block diagram of an exemplary device 1200 suitable for use in implementing embodiments of the present invention. The device 1200 shown in fig. 12 is only an example and should not bring any limitation to the function and scope of use of the embodiments of the present invention.
As shown in fig. 12, device 1200 is in the form of a general purpose computing device. The components of device 1200 may include, but are not limited to: one or more processors or processing units 1201, a system memory 1202, and a bus 1203 that couples the various system components (including the system memory 1202 and the processing unit 1201).
Bus 1203 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Device 1200 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by device 1200 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 1202 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)1204 and/or cache memory 1205. Device 1200 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, the storage system 1206 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 12, and commonly referred to as a "hard drive"). Although not shown in FIG. 12, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 1203 by one or more data media interfaces. Memory 1202 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the present invention.
A program/utility 1208, having a set (at least one) of program modules 1207, which may be stored, for example, in memory 1202, such program modules 1207 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 1207 generally perform the functions and/or methodologies of the described embodiments of the invention.
The device 1200 may also communicate with one or more external devices 1209 (e.g., keyboard, pointing device, display 1210, etc.), with one or more devices that enable a user to interact with the device 1200, and/or with any devices (e.g., network card, modem, etc.) that enable the device 1200 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 1211. Also, device 1200 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the internet) via network adapter 1212. As shown, the network adapter 1212 communicates with the other modules of the device 1200 via a bus 1203. It should be appreciated that although not shown in FIG. 12, other hardware and/or software modules may be used in conjunction with device 1200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processing unit 1201 executes various functional applications and data processing, for example, implementing a microservice-based interface calling method provided by an embodiment of the present invention, by executing a program stored in the system memory 1202.
EXAMPLE six
A sixth embodiment of the present invention further provides a storage medium containing computer-executable instructions which, when executed by a computer processor, are configured to perform a microservice-based interface invocation method.
The method comprises the following steps:
when receiving task request information sent by a client, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters respectively corresponding to each interface to be called; wherein, at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message;
determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to the server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called;
and when target response information corresponding to the target interface calling request returned by the server is received, sending the target response information to the client.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for embodiments of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (10)

1. A method for calling an interface based on micro service is applied to a gateway and comprises the following steps:
when receiving task request information sent by a client, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters corresponding to each interface to be called; the at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message;
determining an interface calling mode corresponding to the task request message, and sending an interface calling request for each interface to be called to a server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called;
and when target response information corresponding to the target interface calling request returned by the server is received, sending the target response information to the client.
2. The method according to claim 1, wherein the interface calling mode is interface serial calling, and the obtaining of the interface calling parameters corresponding to the interfaces to be called respectively comprises:
reading interface calling parameters which are stored in advance and respectively correspond to the interfaces to be called from a configuration center; the configuration center stores interface calling parameters corresponding to each interface in advance.
3. The method according to claim 2, wherein the sending an interface call request for each interface to be called to a server based on the interface call mode comprises:
according to the dependency relationship among the interfaces to be called, sequentially sending interface calling requests of the interfaces to be called to a server in a serial mode;
when target response information corresponding to a target interface calling request returned by a server is received, the target response information is sent to the client, and the method comprises the following steps:
when response information corresponding to the last interface calling request returned by the server is received, taking the response information corresponding to the last interface calling request as target response information; and sending the target response information to the client.
4. The method of claim 1, wherein the interface calling mode is an interface parallel call;
the acquiring of the interface calling parameters corresponding to the interfaces to be called respectively comprises:
according to the task request information, determining interfaces to be called corresponding to the task request information, and acquiring interface calling parameters corresponding to the interfaces to be called; and/or the presence of a gas in the gas,
and reading an interface calling parameter which is carried in the task request information and corresponds to the interface to be called.
5. The method according to claim 4, wherein the sending an interface call request for each interface to be called to a server based on the interface call mode comprises:
and establishing a thread pool corresponding to each interface calling parameter, and sending an interface calling request for each interface to be called to a server in parallel based on the thread pool.
6. The method according to claim 5, wherein when receiving target response information corresponding to a target interface call request returned by a server, sending the target response information to the client comprises:
and receiving response information corresponding to each interface calling request returned by the server, taking a set of each response information as target response information, and sending the target response information to the client.
7. The method of claim 1, wherein sending the target response message to the client comprises:
and when detecting that the data volume of the target response information is larger than a preset threshold value, starting a compression mechanism to compress the target response information and then sending the compressed target response information to the client.
8. A microservice-based interface invocation system, configured in a gateway, comprising:
the system comprises a calling interface determining module, a task processing module and a task processing module, wherein the calling interface determining module is used for determining at least one interface to be called corresponding to a task request message when the task request message sent by a client is received, and acquiring interface calling parameters corresponding to each interface to be called; the at least one interface to be called comprises all interfaces required to be called for completing the task requested by the task request message;
the interface calling parameter sending module is used for determining an interface calling mode corresponding to the task request message and sending an interface calling request for each interface to be called to a server based on the interface calling mode; each interface calling request comprises an interface calling parameter corresponding to an interface to be called; and the target response information sending module is used for sending the target response information to the client when receiving the target response information corresponding to the target interface calling request returned by the server.
9. An apparatus, characterized in that the apparatus comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the microservice-based interface invocation method of any of claims 1-7.
10. A storage medium containing computer-executable instructions for performing the microservice-based interface invocation method of any of claims 1-7 when executed by a computer processor.
CN201910943957.2A 2019-09-30 2019-09-30 Micro-service-based interface calling method, system, equipment and medium Active CN111737022B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910943957.2A CN111737022B (en) 2019-09-30 2019-09-30 Micro-service-based interface calling method, system, equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910943957.2A CN111737022B (en) 2019-09-30 2019-09-30 Micro-service-based interface calling method, system, equipment and medium

Publications (2)

Publication Number Publication Date
CN111737022A true CN111737022A (en) 2020-10-02
CN111737022B CN111737022B (en) 2024-03-01

Family

ID=72646160

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910943957.2A Active CN111737022B (en) 2019-09-30 2019-09-30 Micro-service-based interface calling method, system, equipment and medium

Country Status (1)

Country Link
CN (1) CN111737022B (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112528202A (en) * 2020-12-17 2021-03-19 湖南快乐阳光互动娱乐传媒有限公司 Service request processing method and device
CN112929358A (en) * 2021-01-29 2021-06-08 中国工商银行股份有限公司 Method and apparatus for microservice orchestration, electronic device, and medium
CN114567621A (en) * 2022-04-29 2022-05-31 成都瑞华康源科技有限公司 Client-side adaptive response content control system, method and storage medium
CN114697396A (en) * 2020-12-29 2022-07-01 北京国双科技有限公司 Request processing method and device, electronic equipment and readable storage medium
CN114885026A (en) * 2022-07-07 2022-08-09 飞狐信息技术（天津）有限公司 Data interface request processing system, method, equipment and storage medium
CN114978813A (en) * 2022-04-12 2022-08-30 浙江数新网络有限公司 Gateway implementation method based on response type thread pool

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105453488A (en) * 2014-04-22 2016-03-30 柏思科技有限公司 Methods and systems for processing a DNS request
CN107241517A (en) * 2017-06-15 2017-10-10 北京京东尚科信息技术有限公司 Communication service platform and system, communication system and method and communicator
CN107918738A (en) * 2016-10-10 2018-04-17 维萨国际服务协会 Regulation management user interface
CN109308266A (en) * 2018-11-30 2019-02-05 北京微播视界科技有限公司 Construction method, test method, device, equipment and the medium of test case
WO2019052526A1 (en) * 2017-09-14 2019-03-21 北京金山云网络技术有限公司 Api invoking system, method and apparatus, electronic device and storage medium
CN110213250A (en) * 2019-05-21 2019-09-06 深圳壹账通智能科技有限公司 Data processing method and terminal device
US20190280992A1 (en) * 2018-03-08 2019-09-12 Andre Arzumanyan Intelligent Apparatus and Method for Responding to Text Messages

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105453488A (en) * 2014-04-22 2016-03-30 柏思科技有限公司 Methods and systems for processing a DNS request
CN107918738A (en) * 2016-10-10 2018-04-17 维萨国际服务协会 Regulation management user interface
CN107241517A (en) * 2017-06-15 2017-10-10 北京京东尚科信息技术有限公司 Communication service platform and system, communication system and method and communicator
WO2019052526A1 (en) * 2017-09-14 2019-03-21 北京金山云网络技术有限公司 Api invoking system, method and apparatus, electronic device and storage medium
US20190280992A1 (en) * 2018-03-08 2019-09-12 Andre Arzumanyan Intelligent Apparatus and Method for Responding to Text Messages
CN109308266A (en) * 2018-11-30 2019-02-05 北京微播视界科技有限公司 Construction method, test method, device, equipment and the medium of test case
CN110213250A (en) * 2019-05-21 2019-09-06 深圳壹账通智能科技有限公司 Data processing method and terminal device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
刘雄文;: "多区块链交易分发和事件处理的系统方案", 计算机科学, no. 2 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112528202A (en) * 2020-12-17 2021-03-19 湖南快乐阳光互动娱乐传媒有限公司 Service request processing method and device
CN114697396A (en) * 2020-12-29 2022-07-01 北京国双科技有限公司 Request processing method and device, electronic equipment and readable storage medium
CN112929358A (en) * 2021-01-29 2021-06-08 中国工商银行股份有限公司 Method and apparatus for microservice orchestration, electronic device, and medium
CN114978813A (en) * 2022-04-12 2022-08-30 浙江数新网络有限公司 Gateway implementation method based on response type thread pool
CN114567621A (en) * 2022-04-29 2022-05-31 成都瑞华康源科技有限公司 Client-side adaptive response content control system, method and storage medium
CN114567621B (en) * 2022-04-29 2022-07-12 成都瑞华康源科技有限公司 Client-side adaptive response content control system, method and storage medium
CN114885026A (en) * 2022-07-07 2022-08-09 飞狐信息技术（天津）有限公司 Data interface request processing system, method, equipment and storage medium

Also Published As

Publication number Publication date
CN111737022B (en) 2024-03-01

Similar Documents

Publication Publication Date Title
CN111737022B (en) Micro-service-based interface calling method, system, equipment and medium
US9244817B2 (en) Remote debugging in a cloud computing environment
CN109213611B (en) Cross-process communication method, device, terminal and storage medium
CN109936587B (en) Control method, control device, electronic apparatus, and storage medium
CN110839084B (en) Session management method, device, equipment and medium
CN110489440B (en) Data query method and device
US10360057B1 (en) Network-accessible volume creation and leasing
CN114528044B (en) Interface calling method, device, equipment and medium
CN111343262B (en) Distributed cluster login method, device, equipment and storage medium
CN110933075B (en) Service calling method and device, electronic equipment and storage medium
CN111221793A (en) Data mining method, platform, computer equipment and storage medium
WO2021088671A1 (en) Method for calling terminal capability, device, and computer storage medium
CN111679911A (en) Management method, device, equipment and medium for GPU (graphics processing Unit) card in cloud environment
CN112769876A (en) Method, device, equipment and medium for acquiring equipment channel information
CN111984849A (en) Information query method, device, equipment and medium
CN114020529A (en) Backup method and device of flow table data, network equipment and storage medium
US20190149601A1 (en) Device list synchronizing method and apparatus, device, and computer storage medium
CN114584618A (en) Information interaction method, device, equipment, storage medium and system
CN113760562A (en) Link tracking method, device, system, server and storage medium
CN114390239B (en) Communication method, device, system, electronic device, and storage medium
CN113986995A (en) Request distribution method and device, storage medium and electronic equipment
CN114356925A (en) Identification generation method and device, electronic equipment and storage medium
CN109068170B (en) Storage method, device, terminal and storage medium for barrage message
CN113765972A (en) Data request response method, device, system, server and storage medium
CN110769027A (en) Service request processing method and device, computer equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant