CN111737022B - Micro-service-based interface calling method, system, equipment and medium - Google Patents
Micro-service-based interface calling method, system, equipment and medium Download PDFInfo
- Publication number
- CN111737022B CN111737022B CN201910943957.2A CN201910943957A CN111737022B CN 111737022 B CN111737022 B CN 111737022B CN 201910943957 A CN201910943957 A CN 201910943957A CN 111737022 B CN111737022 B CN 111737022B
- Authority
- CN
- China
- Prior art keywords
- interface
- called
- response information
- calling
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 230000004044 response Effects 0.000 claims abstract description 160
- 230000007246 mechanism Effects 0.000 claims description 6
- 230000006835 compression Effects 0.000 claims description 5
- 238000007906 compression Methods 0.000 claims description 5
- 230000003993 interaction Effects 0.000 abstract description 12
- 238000012545 processing Methods 0.000 abstract description 12
- 230000000694 effects Effects 0.000 abstract description 9
- 238000010586 diagram Methods 0.000 description 12
- 230000008569 process Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 6
- 238000009877 rendering Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 4
- 238000013507 mapping Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
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 an interface calling method, a system, equipment and a medium based on micro-service, wherein the method comprises the following steps: when task request information sent by a client is received, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters respectively corresponding to the interfaces 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 a server based on the interface calling mode; and when receiving target response information corresponding to the target interface call request returned by the server, sending the target response information to the client. The technical scheme of the embodiment of the invention realizes the processing of the information returned by the server through the gateway and the sending of the target response information returned by the target interface to the client, reduces the interaction complexity of the client and the server and improves the technical effect of the interface calling efficiency.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to an interface calling method, system, equipment and medium based on micro-services.
Background
In the same class of service systems, different systems usually contain the same or similar service function modules, and a conventional solution is to refine similar functions into micro service interfaces, and call each micro service interface to realize different services.
If at least two micro service interfaces are required to be called in series to realize a certain service, optionally, 3 micro service interfaces, namely, front-back dependency relationship exists among the 3 micro service interfaces. In the prior art, referring to fig. 1, a caller (client) sends an interface parameter corresponding to a micro service interface 1 to the micro service interface 1, 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, 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 to realize a certain service, for example, when a page rendering service is realized, a plurality of micro service interfaces need to be called in parallel. In the prior art, referring to fig. 2, when determining page rendering, 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 each micro-service interface are received, and the page is rendered based on the return values.
In carrying out the invention, the inventors have found that there are at least the following problems in the prior art:
when the interfaces are called in series, 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 interface is determined, the client needs to establish a thread pool corresponding to each interface parameter every time, and the technical problems of large occupied memory and low efficiency exist.
Disclosure of Invention
The invention provides an interface calling method, system, equipment and medium based on micro-service, which are used for reducing the complexity of accessing each interface and improving the calling efficiency of calling each interface.
In a first aspect, an embodiment of the present invention provides a micro-service-based interface calling method, where the method is applied to a gateway, and includes:
when task request information sent by a client is received, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters respectively corresponding to the interfaces 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; wherein, each interface call request contains interface call parameters corresponding to the interface to be called;
and when target response information corresponding to a target interface call request returned by the server is received, the target response information is sent to the client.
In a second aspect, an embodiment of the present invention further provides a micro-service based interface calling system, where the system is configured in a gateway, and the system includes:
the calling interface determining module is used for determining at least one interface to be called corresponding to the task request message when receiving the task request message sent by the client, and acquiring interface calling parameters respectively corresponding to the interfaces 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; wherein, each interface call request contains interface call parameters corresponding to the 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 call request returned by the server.
In a third aspect, an embodiment of the present invention further provides an apparatus, including:
one or more processors;
storage means for storing one or more programs,
the 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 also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a microservice-based interface invocation method according to any of the embodiments of the present invention.
According to the technical scheme, 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 corresponding to the interfaces to be called are acquired; 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 call request comprises interface call parameters corresponding to the interface to be called; when receiving target response information corresponding to a target interface call request returned by a server, the target response information is sent to the client, so that the technical effects that in the prior art, when serial and/or parallel interfaces are called, the client needs to process response information returned by the server each time until response information returned by all interfaces is received, the complexity of interface access is increased, the efficiency is low, the processing of information returned by the server through a gateway is realized, the target response information returned by the target interface is sent to the client, the interaction complexity of the client and the server is reduced, and the interface call efficiency is improved are achieved.
Drawings
In order to more clearly illustrate the technical solution of the exemplary embodiments of the present invention, a brief description is given below of the drawings required for describing the embodiments. It is obvious that the drawings presented are only drawings of some of the embodiments of the invention to be described, and not all the drawings, and that other drawings can be made according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of interactions between a client and a server when serially invoking various interfaces in the prior art;
FIG. 2 is a schematic diagram of interaction between a client and a server when each interface is invoked in parallel in the prior art;
FIG. 3 is a flowchart of an interface calling method based on micro-services according to an embodiment of the present invention;
FIG. 4 is a flowchart of a micro service interface calling 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 a flowchart of a micro service interface calling method according to a second embodiment of the present invention;
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 diagram illustrating the scope of interface call parameters in a micro-service arrangement according to a second embodiment of the present invention;
FIG. 9 is another diagram illustrating the scope of interface call parameters in a micro-service arrangement according to a second embodiment of the present invention;
FIG. 10 is a flowchart of a micro-service-based interface calling method according to a third embodiment of the present invention;
FIG. 11 is a schematic diagram of an interface calling system based on micro-services according to a fourth embodiment of the present invention;
fig. 12 is a schematic diagram of an apparatus structure according to a fifth embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Example 1
Fig. 3 is a schematic flow chart of an interface calling method based on micro service according to an embodiment of the present invention, where the embodiment is applicable to a case of calling a micro service interface, and the method may be applied to a gateway and may be executed by a micro service-based interface calling system, 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 task request information sent by a client is received, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters respectively corresponding to the interfaces to be called.
The task request information may be understood as request information corresponding to a user-triggered operation. For example, when a user triggers a control on a client, the client may generate task request information corresponding to the trigger. The at least one call interface may be understood as a logical data transfer protocol. The interface call parameter may be understood as a key that calls each interface.
Specifically, when detecting that the user triggers the control on the client, the client may generate task request information corresponding to the triggering 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 determining the interfaces to be called corresponding to the task request information, the interface calling parameters corresponding to the interfaces are required to be acquired so as to call the interfaces to be called.
When the ways of calling the interfaces are different, the interface calling parameters corresponding to the interfaces to be called are also different.
Optionally, the interface calling mode is interface serial calling, and the obtaining interface calling parameters corresponding to each interface to be called respectively includes: reading pre-stored interface calling parameters corresponding to each interface to be called from a configuration center; the configuration center stores interface calling parameters corresponding to the interfaces in advance.
It should be noted that, interface call parameters corresponding to each interface may be predetermined, and the interface call parameters may be stored in the gateway, so that when the gateway receives the task request information, the gateway may parse the task request information, and obtain, from the configuration center, the interface call parameters corresponding to each interface to be called after determining the interface to be called corresponding to the task request information.
Specifically, when the interface to be called required 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 obtained from all interface parameter information stored in the configuration center.
It should be noted that, each task request information, the interface to be called responding to the task request information, and the interface call parameter may be bound in advance, so that the gateway may receive the task information, find 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 call parameter according to the binding relationship. For example, if the task request information is a, the interfaces to be invoked corresponding to the task request information a are a respectively 1 、A 2 、A 3 Then it can be associated with the taskAll interfaces to be called corresponding to the request information A are taken as a whole, and the interface A to be called is established 1 、A 2 、A 3 And the mapping relation table is used for searching the interface to be called and the interface calling parameter corresponding to the task request information from the mapping relation table stored in the configuration center when the gateway receives the task request information sent by the client.
Of course, the interface calling mode further includes parallel calling of the interfaces, and then obtaining interface calling parameters corresponding to the interfaces to be called respectively includes: 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 reading interface calling parameters corresponding to the interface to be called, which are carried in the task request information.
It can be understood that, when the calling mode of the interface is parallel calling, obtaining the interface calling parameters corresponding to each interface to be called includes at least two modes. The first way may be that the client sends task request information to the gateway, the gateway performs protocol analysis on the received task request information, and may determine interfaces to be invoked corresponding to the task request information, and configure interface invoking parameters corresponding to the interfaces to be invoked from the configuration center. Alternatively, before the client sends the task request information to the gateway, the client determines an interface to be invoked corresponding to the task information and corresponding interface invoking parameters in advance. The advantage of this arrangement is that failure to configure interface call parameters corresponding to the task request information from the configuration center due to the flexibility of parallel calls is avoided.
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: interface parallel call, or interface serial call. The interface call request comprises interface call parameters corresponding to each interface to be called.
Specifically, after the gateway receives the task request information, the interface calling mode for executing the task request information can be determined according to the identifier in the task request information, that is, whether each interface to be called is serial interface call or parallel interface call is determined. 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 each interface to be invoked is invoked in a serial manner, the manner of sending the interface invocation parameters to each interface to be invoked may be that, according to the dependency relationship between each interface to be invoked, interface invocation requests for each interface to be invoked are sent to the server in a serial manner in turn.
The serial call of each interface to be called can be understood as that a front-back dependency relationship exists between each interface to be called. Exemplary, if the interfaces to be invoked are A respectively 1 、A 2 、A 3 And A is 1 、A 2 、A 3 There is a front-to-back dependency between the gateway and the interface A 1 Corresponding interface parameters are sent to the A1 interface and received from the interface A 1 Only when response information is returned, the interface A can be connected with 2 Corresponding interface parameters are sent to A 2 And the interface receives response information returned by each calling interface in the similar way.
Specifically, when the calling mode of the interface is serial calling, the front-back dependency relationship among the interfaces to be called can be determined, namely, the front-back sequence of sending the calling parameters of the interfaces to be called to the interfaces to be called is determined. According to the front-back sequence of the interface calling parameters, the interface calling parameters corresponding to the first interface to be called are sent 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 the identifier in the response information is information for sending the next interface parameter, the interface calling parameters corresponding to the second interface to be called are sent to the second interface to be called in the server, until the response information returned by the second interface to be called is received, the interface calling parameters corresponding to the third interface to be called are sent to the third interface to be called in the server, and according to the mode, the interface calling parameters are sequentially sent to the corresponding interfaces to be called, so that the interfaces to be called return the corresponding response information.
Optionally, when each interface to be invoked is invoked in parallel, the manner of sending the interface invocation parameters to each interface to be invoked may be: and establishing a thread pool corresponding to each interface call parameter, and sending an interface call request for each interface to be called to the server in parallel based on the thread pool.
Specifically, when the gateway determines the interface call parameters corresponding to the interfaces to be called, the gateway can send the interface call parameters corresponding to the interfaces to be called in the server at the same time because the front-back dependency relationship does not exist between the interfaces to be called. In order to improve the efficiency of calling each interface, the request merging module in the gateway can establish a thread pool corresponding to each interface to be called according to the interface calling parameters, and send an interface calling request to each interface to be called to the server based on the thread pool, namely, send the interface calling parameters to the interfaces to be called in the server. The method has the advantages that when at least one client sends the same task request, the thread pools are not required to be respectively built in the clients, and the task request information can be processed only by building a group of thread pools at the gateway, so that the complexity of processing the task request information by the clients is reduced.
For example, in the page rendering service scene, the client needs to acquire response information returned by a plurality of micro service interfaces, so as to render the whole page. The client can generate task request information corresponding to the page rendering and send the task request information to the gateway, the gateway analyzes the received task request information to obtain interface call parameters corresponding to the task request information, and optionally, the interface call parameters corresponding to the call page frame, the interface call parameters corresponding to the call page content and the like, respectively establish thread pools corresponding to the interface call parameters, send the interface parameters to the server based on the thread pools so as to obtain the page frame and the page content, and realize the page rendering 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 built in the gateway, so that when the client manages each interface parameter, the client needs to build the thread pool as long as the client initiates the task request, the interface call parameters corresponding to the task request are configured, so that the workload of the client for managing each parameter is increased, and when each client needs to build the thread pool for the same task request information, the problem of resource waste exists, and meanwhile, the interface access efficiency is reduced.
S130, when target response information corresponding to the target interface call request returned by the server is received, the target response information is sent to the client.
Optionally, when the interface calling mode is serial calling, and based on the dependency relationship between the interfaces to be called, after the interface calling requests sent to the interfaces to be called are sequentially sent to the server, 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 may generate an interface call request corresponding to each interface to be called, and send the interface call request to each interface to be called in sequence. When the front-back dependency relationship exists among the interfaces to be called, the interface calling request corresponding to the last interface to be called is used as the last interface calling request. The target response information is response information returned by the interface to be called corresponding to the last interface call request, namely, after the server receives the last interface call request, the last interface to be called returns response information.
Exemplary, interfaces for serial call are A respectively 1 、A 2 、A 3 . When interface A 1 When response information is returned, the gateway can be connected with the interface A 2 Corresponding interface call parameters are sent to the interface A 2 When receiving interface A 2 In response to the returned information, the gateway will communicate with interface A 3 Corresponding interface parameters are sent to the interface A 3 Until the gateway receives interface A 3 And returned response information. At this time, interface A may be connected with 3 The corresponding interface call request is used as the last interface call request, and the interface A is used as the interface 3 The 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, after each interface calling parameter is sent to the server based on the thread pool, response information corresponding to each interface calling request returned by the server is received, the set of each response information is used as target response information, and the target response information is sent 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 to the gateway. When the gateway receives response information returned by all interfaces, the gateway takes the set of each response information as target response information, packages each corresponding information as target response information, and sends the target response information to the client. The method has the advantages that the response information returned by each interface to be called can be integrated and then sent to the client, so that the technical problem that the interaction complexity between the client and the server is increased due to the fact that the response information is sent to the server only by 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 number of target response information stored 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 set in the gateway. When the data volume of the target response information received by the gateway is detected to be larger than a preset threshold value, a compression mechanism is started to compress the target response information, so that the data volume of the target response information is reduced, and the transmission efficiency of the gateway for sending the target response information to the client is improved.
Of course, the gateway is also provided with a timeout mechanism, which has the advantage that when the gateway does not receive the response information within the preset time, the gateway can send the interface calling parameters corresponding to the interface to the corresponding interface again, so that the problem of waiting for the response information all the time and reducing the interface calling efficiency is avoided.
According to the technical scheme, 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 corresponding to the interfaces to be called are acquired; 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 call request comprises interface call parameters corresponding to the interface to be called; when receiving target response information corresponding to a target interface call request returned by a server, the target response information is sent to the client, so that the technical effects that in the prior art, when serial and/or parallel interfaces are called, the client needs to process response information returned by the server each time until response information returned by all interfaces is received, the complexity of interface access is increased, the efficiency is low, the processing of information returned by the server through a gateway is realized, the target response information returned by the target interface is sent to the client, the interaction complexity of the client and the server is reduced, and the interface call efficiency is improved are achieved.
Example two
FIG. 4 is a flowchart of a micro-service-based interface calling method according to a second embodiment of the present invention; as shown in fig. 4, the method includes:
s410, the client sends task request information to the gateway.
For the sake of clearly describing the technical solution of the embodiment of the present invention, the solution can be understood by referring to the interaction schematic diagram between the client and the server when the micro service interface is invoked in fig. 5.
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, i.e. 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 triggering operation may be generated, and the task request information may be sent to the gateway. I.e. the caller (client) sends the task request information to the chained call module in the gateway.
S420, the gateway determines an interface to be called corresponding to the task request information according to the received task request information, and obtains interface calling parameters corresponding to the interface to be called from the configuration center and sends the interface calling parameters 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 interface call parameters corresponding to the interface to be called from all interface call parameters stored in the configuration center in advance, or searches whether the request information corresponding to the current task request information is stored in the interface call parameters corresponding to different request information stored in the configuration center in advance. If the interface call parameters exist, the corresponding interface to be called and the interface call parameters can be directly obtained.
That is, when the chained call module receives the task request information, the corresponding interface to be called can be determined according to the task request information, and the interface call parameters corresponding to the interface to be called are obtained from the configuration. After the interface call parameters are obtained, if the dependency relationship exists between the interfaces, the call 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, the gateway sends calling parameters corresponding to the interface 2 to be called to the 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 the like, and the interface calling parameters corresponding to the interfaces to be called are sent to the server.
And S430, when the gateway receives the response information, the gateway transmits the next interface call parameter information to the server until the gateway receives the response information returned by the target interface to be called.
That is, every time the gateway receives the response information returned by the server, the next call request, that is, the interface call parameters are sent to the server, and in this way, each interface call parameter is sequentially sent to the server 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 response information from 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 target response information, and the target response information may be sent to the client.
The above embodiment is a schematic flow chart of serial call of the interface. The interface calling mode also comprises interface parallel calling. Fig. 6 is a schematic flow chart of an interface calling method based on micro-services 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 with reference to fig. 7.
Specifically, after a control is triggered on the client (caller), the client (caller) may generate task request information corresponding to the trigger operation, and send the task request information to the gateway. The request merging module is arranged in the gateway and can process task request information.
S620, the gateway acquires parameter information corresponding to the task request information, establishes thread pools corresponding to the parameter information, and sends 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 the server, namely the 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 a return value, and send the response information returned by each interface as a whole, namely a return value set, to the client so that the client realizes the function corresponding to the triggering operation according to the received return value set.
On the basis of the above technical solution, it should be noted that, in the configuration center of the gateway, interface call parameters corresponding to each interface are prestored, and these interface call parameters are divided into three levels according to the scope size of the parameter validity, and are 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. Wherein the activity level scope is larger than the component level scope, which is larger than the action level scope, see fig. 8 and fig. 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 identifiers.
In this embodiment, when a caller calls a back-end service, that is, a server, only needs to input an interface name and a set of related parameters, then the back-end requests a merging interface, that is, a request merging module arranged in a gateway establishes a thread pool and calls a back-end service interface based on the thread pool after receiving the request, after all service interfaces return data, query results are summarized and returned to the front end, that is, a client, so that interface calling efficiency is improved, that is, response efficiency to user triggering operation is improved.
According to the technical scheme, 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 corresponding to the interfaces to be called are acquired; 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 call request comprises interface call parameters corresponding to the interface to be called; when receiving target response information corresponding to a target interface call request returned by a server, the target response information is sent to the client, so that the technical effects that in the prior art, when serial and/or parallel interfaces are called, the client needs to process response information returned by the server each time until response information returned by all interfaces is received, the complexity of interface access is increased, the efficiency is low, the processing of information returned by the server through a gateway is realized, the target response information returned by the target interface is sent to the client, the interaction complexity of the client and the server is reduced, and the interface call efficiency is improved are achieved.
Example III
As a preferred embodiment of the foregoing embodiments, fig. 10 is a schematic flow chart of an interface serial call method according to a third embodiment of the present invention. As shown in fig. 10, the method includes:
s1001, starting.
It may be understood that the gateway receives the task request information sent by the client.
S1002, judging whether the call is one time, if yes, executing S1003; if not, S1004.
The gateway analyzes the task request information and can determine the calling mode of the interface and the number to be called. When the number of interfaces to be called is one, determining that the interface is called once, and executing S1003; if the number of interfaces to be called is plural, it is determined that the call is plural, and S1004 is executed.
S1003, acquiring interface calling parameters and sending the interface calling parameters to a server.
According to the task request information, an interface to be called can be determined, and the chained call module can be configured in interface parameter information corresponding to the interface to be called from the configuration center according to the interface to be called, and send the interface parameter information to the server, and when the server returns response information, send the response information to the client, that is, execute S1007.
S1004, executing the core business.
The execution core service can be understood as sending the interface calling parameters to the server, and each interface to be called in the server returns corresponding response information.
S1005, judging whether a post-operation exists, if so, executing S1006; if not, S1007 is performed.
Judging whether the post-action exists or not may mean that when the interface to be called of the server returns response information, whether the response information carries information for sending the next interface call parameter to the server or not, if yes, judging that the post-action exists, executing S1006, and if not, sending the response information returned by the server to the client.
S1006, invoking a post action.
It can be understood that the operation of sending the parameter information to the server is continuously performed until each interface call parameter is sent to the corresponding interface to be called, and the target response information returned by the target interface is received.
And S1007, the target response information received by the gateway is sent to the client.
The gateway sends target response information to the client, namely, responds to the triggering operation of the user.
According to the technical scheme, 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 corresponding to the interfaces to be called are acquired; 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 call request comprises interface call parameters corresponding to the interface to be called; when receiving target response information corresponding to a target interface call request returned by a server, the target response information is sent to the client, so that the technical effects that in the prior art, when serial and/or parallel interfaces are called, the client needs to process response information returned by the server each time until response information returned by all interfaces is received, the complexity of interface access is increased, the efficiency is low, the processing of information returned by the server through a gateway is realized, the target response information returned by the target interface is sent to the client, the interaction complexity of the client and the server is reduced, and the interface call efficiency is improved are achieved.
Example IV
Fig. 11 is a schematic diagram of an interface calling system based on micro services according to a fourth embodiment of the present invention, where the system is configured in a gateway, as shown in fig. 11, and the system includes: an interface determination module 1101, an interface call parameter transmission module 1102, and a target response information transmission module 1103.
The calling interface determining module 1101 is configured to determine, when task request information sent by a client is received, at least one interface to be called corresponding to the task request information, and obtain interface calling parameters corresponding to the interfaces to be called respectively; 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; wherein, each interface call request contains interface call parameters corresponding to the interface to be called; the target response information sending module 1103 is configured to send, when target response information corresponding to a target interface call request returned by the server is received, the target response information to the client.
Based on the above technical solutions, the interface calling mode is interface serial calling, and the calling interface determining module includes:
reading pre-stored interface calling parameters corresponding to the interfaces to be called respectively from a configuration center; the configuration center stores interface calling parameters corresponding to the interfaces 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 for the interfaces to be called to a server in a serial mode;
when receiving target response information corresponding to a target interface call request returned by a server, the method for sending the target response information to the client comprises the following steps:
when response information corresponding to the last interface call request returned by the server is received, the response information corresponding to the last interface call request is used as target response information; and sending the target response information to the client.
Based on 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 interface to be called; and/or reading interface calling parameters corresponding to the interface to be called, which are carried in the task request information.
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 call parameter, and sending an interface call 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:
receiving response information corresponding to each interface call request returned by the server, taking the 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 the data quantity of the target response information is detected to be 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, 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 corresponding to the interfaces to be called are acquired; 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 call request comprises interface call parameters corresponding to the interface to be called; when receiving target response information corresponding to a target interface call request returned by a server, the target response information is sent to the client, so that the technical effects that in the prior art, when serial and/or parallel interfaces are called, the client needs to process response information returned by the server each time until response information returned by all interfaces is received, the complexity of interface access is increased, the efficiency is low, the processing of information returned by the server through a gateway is realized, the target response information returned by the target interface is sent to the client, the interaction complexity of the client and the server is reduced, and the interface call efficiency is improved are achieved.
The micro-service-based interface calling system provided by the embodiment of the invention can execute the micro-service-based interface calling method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
It should be noted that, the units and modules included in the above system are only divided according to the functional logic, but not limited to the above division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the embodiments of the present invention.
Example five
Fig. 12 is a schematic structural diagram of a device according to a fifth embodiment of the present invention. Fig. 12 shows a block diagram of an exemplary device 1200 suitable for use in implementing the embodiments of the invention. The apparatus 1200 shown in fig. 12 is merely an example, and should not be construed as limiting the functionality and scope of use of 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 connects the various system components (including the system memory 1202 and the processing units 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, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include 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 or write to non-removable, non-volatile magnetic media (not shown in FIG. 12, commonly referred to as a "hard disk drive"). Although not shown in fig. 12, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 1203 via 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 configured to carry out the functions of embodiments of the invention.
A program/utility 1208 having a set (at least one) of program modules 1207 may be stored in, for example, memory 1202, such program modules 1207 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 1207 typically carry out the functions and/or methods of the described embodiments of the present invention.
The device 1200 may also communicate with one or more external devices 1209 (e.g., keyboard, pointing device, display 1210, etc.), one or more devices that enable a user to interact with the device 1200, and/or 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 through an input/output (I/O) interface 1211. Also, device 1200 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, e.g., the internet, through network adapter 1212. As shown, network adapter 1212 communicates with other modules of device 1200 via bus 1203. It should be appreciated that although not shown in fig. 12, other hardware and/or software modules may be used in connection with device 1200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 1201 executes various functional applications and data processing by running a program stored in the system memory 1202, for example, implementing a micro service-based interface calling method provided by an embodiment of the present invention.
Example six
A sixth embodiment of the present invention also provides a storage medium containing computer-executable instructions for performing a microservice-based interface invocation method when executed by a computer processor.
The method comprises the following steps:
when task request information sent by a client is received, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters respectively corresponding to the interfaces 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 call request comprises interface call parameters corresponding to the interface to be called;
and when receiving target response information corresponding to the target interface call request returned by the server, sending the target response information to the client.
The computer storage media of embodiments of the invention may take the form of 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. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any 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 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.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 ++ 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 kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. 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, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (7)
1. An interface calling method based on micro-service is characterized in that the method is applied to a gateway, a configuration center of the gateway stores interface calling parameters corresponding to each interface in advance, and the method comprises the following steps:
when task request information sent by a client is received, determining at least one interface to be called corresponding to the task request information, and acquiring interface calling parameters respectively corresponding to the interfaces 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 information;
Determining an interface calling mode corresponding to the task request information, and sending an interface calling request for each interface to be called to a server based on the interface calling mode; wherein, each interface call request contains interface call parameters corresponding to the interface to be called;
when target response information corresponding to a target interface call request returned by a server is received, the target response information is sent to the client;
the sending, based on the interface calling manner, an interface calling request for each interface to be called to a server includes:
under the condition that the interface calling mode is interface serial calling, according to the dependency relationship among the interfaces to be called, sequentially sending interface calling requests for the interfaces to be called to a server in a serial mode;
correspondingly, when receiving the target response information corresponding to the target interface call request returned by the server, the method sends the target response information to the client, including:
when response information corresponding to the last interface call request returned by the server is received, the response information corresponding to the last interface call request is used as target response information; sending the target response information to the client;
Under the condition that the interface calling mode is interface parallel calling, 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; when receiving target response information corresponding to a target interface call request returned by a server, the method for sending the target response information to the client comprises the following steps:
receiving response information corresponding to each interface call request returned by the server, taking the set of each response information as target response information, and 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 the interface calling parameters corresponding to the interfaces to be called respectively includes:
and reading the pre-stored interface calling parameters corresponding to the interfaces to be called respectively from a configuration center.
3. The method according to claim 1, wherein the interface call mode is an interface parallel call;
the obtaining the interface calling parameters respectively corresponding to the interfaces to be called comprises the following steps:
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 number of the groups of groups,
and reading interface calling parameters corresponding to the interface to be called, which are carried in the task request information.
4. The method of claim 1, wherein the sending the target response information to the client comprises:
and when the data quantity of the target response information is detected to be 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.
5. An interface calling system based on micro service, characterized in that the system is configured in a gateway, a configuration center of the gateway prestores interface calling parameters corresponding to each interface, and the device comprises:
the calling interface determining module is used for determining at least one interface to be called corresponding to task request information when the task request information sent by the client is received, and acquiring interface calling parameters respectively corresponding to the interfaces 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 information;
The interface calling parameter sending module is used for determining an interface calling mode corresponding to the task request information and sending an interface calling request for each interface to be called to a server based on the interface calling mode; wherein, each interface call request contains interface call parameters corresponding to the interface to be called;
the target response information sending module is used for sending target response information corresponding to a target interface call request returned by the server to the client when the target response information is received;
the call interface determination module is further configured to:
under the condition that the interface calling mode is interface serial calling, according to the dependency relationship among the interfaces to be called, sequentially sending interface calling requests for the interfaces to be called to a server in a serial mode;
correspondingly, the target response information sending module is further configured to, when receiving response information corresponding to a last interface call request returned by the server, use the response information corresponding to the last interface call request as target response information; sending the target response information to the client;
under the condition that the interface calling mode is interface parallel calling, 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;
Correspondingly, the target response information sending module is further configured to receive response information corresponding to each interface call request returned by the server, take a set of each response information as target response information, and send the target response information to the client.
6. An apparatus, the apparatus comprising:
one or more processors;
storage means for storing one or more programs,
the 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-4.
7. A storage medium containing computer executable instructions for performing the microservice-based interface invocation method of any of claims 1-4 when executed by a computer processor.
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 CN111737022A (en) | 2020-10-02 |
| CN111737022B true 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) |
Families Citing this family (6)
| 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 |
| CN112929358B (en) * | 2021-01-29 | 2022-12-30 | 中国工商银行股份有限公司 | 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 |
| 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 |
Citations (6)
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10778614B2 (en) * | 2018-03-08 | 2020-09-15 | Andre Arzumanyan | Intelligent apparatus and method for responding to text messages |
-
2019
- 2019-09-30 CN CN201910943957.2A patent/CN111737022B/en active Active
Patent Citations (6)
| 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 |
| 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)
| Title |
|---|
| 多区块链交易分发和事件处理的系统方案;刘雄文;;计算机科学(S2);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111737022A (en) | 2020-10-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111737022B (en) | Micro-service-based interface calling method, system, equipment and medium | |
| CN111367983B (en) | Database access method, system, device and storage medium | |
| US9244817B2 (en) | Remote debugging in a cloud computing environment | |
| CN110489440B (en) | Data query method and device | |
| CN110839084B (en) | Session management method, device, equipment and medium | |
| WO2021017771A1 (en) | Service request processing method and related device | |
| US20190294466A1 (en) | Network-accessible volume creation and leasing | |
| CN113765980A (en) | Current limiting method, device, system, server and storage medium | |
| CN111343262B (en) | Distributed cluster login method, device, equipment and storage medium | |
| CN111679911A (en) | Management method, device, equipment and medium for GPU (graphics processing Unit) card in cloud environment | |
| CN111221793A (en) | Data mining method, platform, computer equipment and storage medium | |
| CN112835632B (en) | Method and equipment for calling end capability and computer storage medium | |
| CN109302639B (en) | Bullet screen message distribution method, bullet screen message distribution device, terminal and storage medium | |
| CN112769876A (en) | Method, device, equipment and medium for acquiring equipment channel information | |
| CN111984849A (en) | Information query method, device, equipment and medium | |
| CN114584618A (en) | Information interaction method, device, equipment, storage medium and system | |
| CN112333282A (en) | Service providing method, device, medium and electronic equipment based on hybrid cloud | |
| CN110120963B (en) | Data processing method, device, equipment and machine readable medium | |
| CN113986995A (en) | Request distribution method and device, storage medium and electronic equipment | |
| CN109327726B (en) | Barrage message processing method and device, terminal and storage medium | |
| CN113765972A (en) | Data request response method, device, system, server and storage medium | |
| CN110209464B (en) | Nano-tube method, storage medium and management platform of virtual machine | |
| CN111258560B (en) | Data storage device, system and method | |
| US11546157B2 (en) | Adaptive identification systems and methods | |
| CN111142820B (en) | Remote control method, device and system based on multiple screens |
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 |