CN107181675B - Service invocation method and device - Google Patents

Abstract

The invention provides a service invocation method and device. The service gateway receives the service invocation request and sends the service invocation request to the corresponding service provider; and the service gateway returns the response result returned by the service provider to the service invocation end. . Wherein, the service invocation request includes an invocation identifier that uniquely identifies the current invocation link, and the invocation identifier is passed between each service provider in the entire invocation link. Each service invocation request and invocation result need to be forwarded by the service gateway. Therefore, the service gateway can obtain invocation information corresponding to all service invocations. Therefore, the service invocation link corresponding to the invocation identifier is searched from the invocation information. This method only needs to set buried points on the service gateway for sampling, and does not need to set buried points on both the client and the server. Therefore, the development and deployment costs of the client and the server of the service are greatly reduced.

Description

Service invocation method and device

technical field

The invention belongs to the field of computers, and in particular relates to a service invocation method and device.

Background technique

At present, the system of Internet companies usually consists of a large number of subsystems that provide different functions using a microservice architecture. Microservices refer to the development of multiple independent and small services with complete business functions. Each service has its own processing and communication mechanism and can be deployed on a single or multiple servers.

There are a large number of microservices in the microservice architecture, and there are complex calling relationships between microservices. Therefore, it is difficult for developers to figure out the calling relationship between the various microservices included in the whole system. When a performance bottleneck occurs, it can be difficult to locate the faulty service component.

In response to the above problems, the traditional solution is to perform buried point sampling on the client and server of each microservice, and finally analyze all the sampled data to obtain the service call link of the system. The client and server of each microservice bring development and deployment pressure, and it is difficult for different microservice providers to coordinate a unified buried point sampling plan.

SUMMARY OF THE INVENTION

In view of this, the purpose of the present invention is to provide a service invocation method and device, so as to solve the difficulty of client and server development and deployment of microservices existing in traditional solutions, and it is difficult for different service providers to unify buried point sampling technical issues. The technical scheme of the present invention is as follows:

In a first aspect, the present application provides a service invocation method, which is applied in a service gateway, and the method includes:

Receive a service invocation request, where the service invocation request includes a service invocation terminal identifier, a service name and an invocation identifier, and the invocation identifier is used to uniquely identify a service invocation link corresponding to the service invocation request;

sending the service invocation request to the corresponding service provider according to the service name;

Receive the call result returned by the service provider, and send the call result to the service caller;

Acquire the invocation information corresponding to the service invocation request, so that the invocation analysis terminal analyzes the service invocation terminal identification, the service provider identification and the invocation identification in the invocation information to obtain a service invocation link corresponding to the invocation identification.

Optionally, the invocation information further includes invocation time information, and the invocation time information includes invocation time-consuming; the process of acquiring the invocation time-consuming includes:

recording the first timestamp of receiving the service invocation request, and recording the second timestamp of receiving the invocation result corresponding to the invocation request;

Calculate the time difference between the second time stamp and the first time stamp to obtain the calling time of each service.

Optionally, the receiving a service invocation request includes:

receiving the service invocation request sent by the client;

or,

Receive a service invocation request sent by the first service provider to invoke the second service provider.

In the second aspect, the present application also provides another service invocation method, which is applied to the service provider, and the method includes:

The first service provider receives the first call request forwarded by the service gateway, where the first call request includes a first service caller identifier, a first service name and a call identifier, and the call identifier is used to uniquely identify the service call request The corresponding service call link;

The first service provider parses the first invocation request to obtain the second service name to be invoked by the first invocation request, and the invocation identifier;

The first service provider generates a second call request according to the second service name, where the second call request includes a second service caller identifier, a second service name, and the call identifier;

The first service provider sends the second invocation request to the service gateway, so that the service gateway forwards the second invocation request to the second service provider, and the second service provider provides the service corresponding to the second service name; and, enabling the service gateway to obtain invocation information, and the invocation analysis terminal obtains the service invocation link corresponding to the invocation identifier according to the invocation information.

Optionally, the method further includes:

The first service provider receives the second invocation result returned by the second service provider through the service gateway, and the second invocation result is obtained by the second service provider in response to the second invocation request;

The first service provider responds to the first invocation request according to the second invocation result, generates a first invocation result, and forwards the first invocation result to initiating the first invocation request through the service gateway The first service caller of .

In a third aspect, the present application provides a service invocation apparatus, which is applied in a service gateway, and the apparatus includes:

a first receiving unit, configured to receive a service invocation request, where the service invocation request includes a service invocation terminal identifier, a service name and an invocation identifier, and the invocation identifier is used to uniquely identify a service invocation link corresponding to the service invocation request;

a first sending unit, configured to send the service invocation request to a corresponding service provider according to the service name;

a second receiving unit, configured to receive the calling result returned by the service provider;

a second sending unit, configured to send the calling result to the service calling end;

The acquiring unit is configured to acquire the invocation information corresponding to the service invocation request, so that the invocation analysis terminal analyzes the service invocation terminal identification, the service provider identification and the invocation identification in the invocation information to obtain the corresponding invocation identification. Service call link.

Optionally, the invocation information further includes invocation time information, and the invocation time information includes invocation time-consuming, and the acquiring unit includes:

a first recording subunit, configured to record the first timestamp of receiving the service invocation request;

a second recording subunit, configured to record the second timestamp of receiving the invocation result corresponding to the invocation request;

A calculation subunit, configured to calculate the time difference between the second time stamp and the first time stamp, and obtain the invocation time corresponding to each service.

Optionally, the first receiving unit is specifically configured to:

receiving the service invocation request sent by the client;

or,

Receive a service invocation request sent by the first service provider to invoke the second service provider.

In a fourth aspect, the present application provides a service invocation device, which is applied to a service provider, and the device includes:

The first receiving unit is configured to enable the first service provider to receive the first invocation request forwarded by the service gateway, where the first invocation request includes the first service invocation terminal identifier, the first service name and the invocation identifier, and the invocation identifier is to uniquely identify the service invocation link corresponding to the service invocation request;

a first parsing unit, configured to enable the first service provider to parse the first invocation request to obtain the second service name and the invocation identifier to be invoked by the first invocation request;

A request generating unit, configured to enable the first service provider to generate a second invocation request according to the second service name, where the second invocation request includes a second service invocation terminal identifier, a second service name and the invocation identifier ;

a first sending unit, configured to make the first service provider send the second invocation request to the service gateway, so that the service gateway forwards the second invocation request to the second service provider, The second service provider provides the service corresponding to the second service name; and the service gateway obtains invocation information, and the invocation analysis end obtains the service invocation chain corresponding to the invocation identifier according to the invocation information road.

Optionally, the device further includes:

a second receiving unit, configured to enable the first service provider to receive a second invocation result returned by the second service provider through the service gateway, and the second invocation result is responded by the second service provider The second invocation request is obtained;

A response unit, configured to make the first service provider respond to the first invocation request according to the second invocation result, generate a first invocation result, and forward the first invocation result to the initiator through the service gateway The first service calling end of the first calling request.

In the service invocation method provided in this embodiment, the service gateway receives the service invocation request, the service gateway sends the service invocation request to the corresponding service provider according to the service name, and the service invocation request includes the invocation identifier that uniquely identifies the current invocation link, and The call identifier is passed between each service provider in the entire call chain; each service call request and call result need to be forwarded through the gateway, so the service gateway can obtain call information corresponding to all service calls. The call information includes the service caller identifier, the service provider identifier, the call identifier, and the call time information. Therefore, searching for the service caller identifier and the service provider identifier corresponding to the call identifier from the call information can obtain the corresponding call identifier. Service call link. This method only needs to set buried points on the service gateway for sampling, and does not need to set buried points on both the client and the server. Therefore, the development and deployment costs of the client and server of each service are greatly reduced.

Description of drawings

In order to illustrate the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are For some embodiments of the present invention, for those of ordinary skill in the art, other drawings can also be obtained according to these drawings without creative efforts.

Figure 1 shows a schematic diagram of a typical microservice architecture;

2 shows a schematic diagram of a service invocation system according to an embodiment of the present invention;

3 shows a flowchart of a service invocation method according to an embodiment of the present invention;

FIG. 4 shows a flowchart of another service invocation method according to an embodiment of the present invention;

FIG. 5 shows a block diagram of an apparatus for invoking a service according to an embodiment of the present application;

FIG. 6 shows a block diagram of an acquisition unit according to an embodiment of the present application;

FIG. 7 shows a block diagram of another service invocation apparatus according to an embodiment of the present application.

Detailed ways

Before introducing the technical solution of the present invention in detail, first introduce the microservice architecture:

Microservices refer to the development of multiple independent and small services with complete business functions. Each service has its own processing and communication mechanism and can be deployed on a single or multiple servers. The ideas and concepts of the microservice architecture are as follows: decouple the system into smaller units; each unit has its own responsibilities; each unit is exposed through an application programming interface (API), and the outside world does not need to care about it All units are independent and can be developed, deployed, extended and monitored independently; each unit can interact with each other through the Remote Procedure Call Protocol (RPC).

In the microservice architecture, the client and the server need to interact with the service gateway device. As the entrance of the system, the service gateway is responsible for service request routing, composition, and protocol conversion. In addition, identity authentication of access clients, anti-message replay and anti-data tampering, service authentication of function calls, desensitization of response data, traffic and concurrency control, and even metering or billing based on API calls are also required.

As shown in Figure 1, a typical microservice architecture is shown. The microservice system includes six microservices: A, B, C, D, E, and F. For example, the microservice system contains 3 microservice routes: new user registration is implemented by microservices A, B, C and E, where the calling relationship between microservices is that A calls B, B calls C, and C calls E ; placing an order is implemented by microservices A, B, C and D; payment is implemented by microservices A, B, C, D and F.

In the microservice architecture, there is a complex calling relationship between microservices, which makes it difficult for system developers to figure out the calling relationship between microservices in the entire microservice system. When a performance bottleneck occurs in the entire calling chain, It's hard to pinpoint which node is the problem. In the service invocation method provided by this application, buried point sampling is set in the service gateway, the service gateway is responsible for service request routing, and each service invocation needs to go through the service gateway. Therefore, the service gateway can sample the invocation information of each service invocation, such as , call relationship, call time, etc. Then, analyze the call information collected by the service gateway.

In order to make the purposes, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments These are some embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

Please refer to FIG. 2, which shows a schematic diagram of a service invocation system according to an embodiment of the present invention. As shown in FIG. 2, the system includes a service invocation terminal 1, a service gateway 2, a service provider 3, a log collector 4, and an invocation analysis terminal. end 5.

The service invocation terminal 1 is used to send a service invocation request to the service gateway, and each service invocation request includes an invocation identifier for uniquely marking the current invocation link.

The service gateway 2 is used to route the service call to the correct service provider, and record the call information of this call, wherein the call information includes the call identifier, the service caller identifier, and the service provider identifier.

The service provider 3 is used to receive and process the first service invocation request. If the service provider needs to initiate a service invocation again, a second service invocation request is generated, and the second service invocation request carries the information in the first service invocation request. Included call identifier, the call identifier is passed in sequence until the last service provider of this call.

The log collector 4 is used to collect the call information sampled by the service gateway, and send the call information to the call analysis terminal 5 .

In a possible implementation manner of the present invention, the log collector 4 may be deployed in the device where the service gateway is located;

In another possible implementation manner of the present invention, the log collector 4 may be deployed in a device other than the service gateway. In this application scenario, the log collector 4 needs to know the address of the service gateway, and obtains the information from the service gateway. to get call information.

The invocation analysis terminal 5 analyzes the invocation information collected by the log collector, determines that all invocation requests including the same invocation identifier belong to the same invocation link, and obtains the service topology of the service system according to different invocation links. And, the call time corresponding to each call request is obtained, and the performance bottleneck of the service system is determined according to the call time. Wherein, the invocation time-consuming refers to the time required from initiating a service invocation to obtaining a response from the service.

Referring to FIG. 3 , a flowchart of a method for invoking a service according to an embodiment of the present invention is shown. The method is applied to a service gateway. As shown in FIG. 3 , the method may include:

S110, the service gateway receives the service invocation request.

The service gateway receives the service invocation request sent by the service invocation end, the service invocation request includes the service invocation end identification, the service name and the invocation identification, and the invocation identification is used to uniquely identify the invocation link corresponding to the service invocation request.

The service invocation end is the party that initiates the service invocation request, and the service invocation end identifier may be identification information that can uniquely identify the service invocation end, for example, a media access control (Medium Access Control, MAC) address.

In a possible implementation manner of the present invention, the service invoking end may be a client, that is, an application scenario in which the client initiates a service invocation request to the service gateway;

In another possible implementation manner of the present invention, the service invoking end may be a service provider, that is, when the service provider implements a certain service, it needs to call other services, so it needs to send services to other service providers call request.

Extending the example of the microservice architecture shown in Figure 1, when the client initiates a new user registration request, the client sends a "new user registration" service call request to the service gateway. In this application scenario, the service caller (ie , the party that sends the service invocation request) is the client; for example, the new user registration service is implemented by four microservices A-B-C-E. When microservice A calls microservice B, the service invoking end is the service provider of microservice A.

The call identifier is used to uniquely identify the identifier of the current call link, the call identifier is generated by the client that initiates the service call, and is continuously transmitted in the service call link that implements the service.

S120, the service gateway sends the service invocation request to the corresponding service provider according to the service name.

The service gateway finds the service provider that provides the service corresponding to the service name according to the service name included in the service invocation request, and sends the service invocation request to the service provider.

S130, the service gateway receives the call result returned by the service provider, and sends the call result to the service caller.

After the service provider receives the service call request, if it does not need to call other services, it will generate the call result in response to the service call request, and return the call result to the service gateway, and the service gateway will then return the received call result to the service call. end.

S140: The service gateway acquires invocation information corresponding to the service invocation request, so that the invocation analysis terminal obtains a service invocation link corresponding to the invocation identifier according to the invocation information, where the invocation information includes the service invocation terminal identifier, Service provider identification, the invocation identification and invocation time information.

Buried points are set in the service gateway to sample the entire service invocation process to obtain invocation information. The invocation information includes service invocation end identification, service provider identification, invocation identification and invocation time information.

The invocation analysis end analyzes the invocation information obtained by the service gateway to obtain invocation data corresponding to the invocation identifier, and finally obtains the entire service invocation link of this service invocation.

Optionally, the calling time-consuming of the current call can be obtained according to the calling time information included in the calling information, and the process of obtaining the calling time-consuming includes:

The service gateway records the first timestamp of receiving the invocation request, and records the second timestamp of receiving the invocation result corresponding to the invocation request, calculates the time difference between the second timestamp and the first timestamp, and obtains each service The invocation of the call is time consuming.

According to the call time corresponding to each call in the current call chain, the call time of the entire call chain is calculated, and the performance bottleneck of the service system can be analyzed according to the call time.

In the service tracking method provided by this embodiment, the service gateway receives the service invocation request, the service gateway sends the service invocation request to the corresponding service provider according to the service name, and the service invocation request includes the invocation identifier that uniquely identifies the current invocation link, and The call identifier is passed between each service provider in the entire call chain; each service call request and call result need to be forwarded through the gateway, so the service gateway can obtain call information corresponding to all service calls. The call information includes the service caller identifier, the service provider identifier, the call identifier, and the call time information. Therefore, searching for the service caller identifier and the service provider identifier corresponding to the call identifier from the call information can obtain the corresponding call identifier. Service call link. As can be seen from the above content, this method obtains the call information by sampling the service gateway, and finally realizes the call link tracking. In this way, it is only necessary to set buried points on the service gateway for sampling, and it is not necessary to set buried points on both the client and the server. , therefore, the development and deployment costs of the client and server side of each service are greatly reduced.

Please refer to FIG. 4, which shows a flowchart of another service invocation method according to an embodiment of the present invention. The method is applied to the system shown in FIG. 2. As shown in FIG. 4, the method includes the following steps:

S210, the client sends a first service invocation request to the service gateway.

The first service invocation request includes the client identifier, the first service name information, and the invocation identifier, where the invocation identifier is used to uniquely identify the current invocation link.

S220: The service gateway determines the corresponding first service provider according to the service name information, forwards the first service invocation request to the first service provider, and records invocation related information of the first service invocation request.

In an embodiment of the present application, the invocation-related information may include: service invocation terminal identification, service provider identification, invocation identification and invocation time information, for example, the time of receiving the invocation request and the time of receiving the corresponding invocation result.

S230, the first service provider receives the first service invocation request, and determines whether other services need to be invoked; if yes, execute S240-S280; if not, execute S290.

After receiving the first service invocation request, the first service provider parses the first service invocation request, and determines whether another service needs to be invoked in response to the first service invocation request.

If it is not necessary to call other services, directly respond to the first service calling request; if other services need to be called, continue to call other services.

S240, the first service provider generates a second service invocation request and sends it to the service gateway.

The second service invocation request carries the invocation identifier included in the first service invocation request, and includes the information of the first service provider and the second service name information.

If the first service provider needs to call other services when responding to the first service invocation request, it generates a second service invocation request for invoking the other service, and when generating the second service invocation request, the first service invocation request contains The invocation identifier is written into the second service invocation request. That is, the call identifier is passed on in the service call chain.

S250, the service gateway receives the second service invocation request, determines the second service provider corresponding to the second service name information, sends the second service invocation request to the second service provider, and records the second service invocation request call-related information.

S260, the second service provider responds to the second service invocation request, obtains the second invocation result, and sends the second invocation result to the service gateway.

S270, the service gateway returns the second invocation result to the first service provider, and records invocation-related information of the second invocation result.

S280, the first service provider obtains the first invocation result according to the second invocation result, and sends the first invocation result to the service gateway.

After executing S240-S280, execute S2100-S2120 in sequence.

S290, the first service provider responds to the first service invocation request, generates a first invocation result, and sends it to the service gateway.

After executing S290, execute S2100-S2120 in sequence;

S2100, the service gateway returns the first invocation result to the client, and records invocation-related information of the first invocation result.

S2110, the log collector collects the recorded invocation-related information from the service gateway.

S2120: Invoke the analysis end to analyze the data in the log collector, and obtain a service invocation link corresponding to the invocation identifier.

The calling analysis terminal processes the data in the log collector, obtains a calling request containing the same calling ID, and determines the calling relationship according to the service calling terminal ID and the service provider ID, so as to obtain the service calling link corresponding to the calling ID. Using this method, various service invocation links can be obtained, so as to obtain the service topology of the entire microservice structure.

While obtaining the invocation relationship, the invocation analysis end determines the invocation time between services according to the invocation time information collected by the log collector, that is, the time when the service gateway receives a certain invocation request and the invocation result corresponding to the invocation request. difference between the times.

Using the service topology and the call time between services, the performance bottlenecks in the entire microservice architecture can be analyzed.

The call analysis terminal can be implemented based on the text retrieval system. The details of the call link to be viewed by entering the filter conditions. For example, you can enter the time period to filter the time period of the call to be viewed, and retrieve all the log data from the log collector. Relevant information about service calls within this time period, such as service caller ID, service provider ID, and call delay.

In the service invocation method provided by this embodiment, a buried point is set in the service gateway to sample and record each invocation in the microservice architecture, wherein the service invocation request includes the invocation identifier of the current invocation link, and the invocation identifier is in It has been passed through the entire call chain. The log collector can collect the call-related information collected by the service gateway and provide it to the call analyzer. The call analyzer can analyze the call-related information to find the service caller identifier and service provider identifier corresponding to the call identifier to obtain the call identifier. Corresponding service invocation link. This method obtains the call information by sampling the service gateway, and finally realizes the call link tracking. In this way, it is only necessary to set buried points on the service gateway for sampling, and it is not necessary to set buried points on both the client and the server. The development and deployment costs of the client and server of each service are calculated.

For the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, Certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

Corresponding to the foregoing service invocation method embodiments, the present application further provides service invocation apparatus embodiments.

Referring to FIG. 5 , it shows a block diagram of an apparatus for invoking a service according to an embodiment of the present application, and the apparatus is applied in a service gateway. The apparatus includes: a first receiving unit 110, a first sending unit 120, a second receiving unit 130, a second sending unit 140 and an obtaining unit 150;

The first receiving unit 110 is configured to receive a service invocation request, where the service invocation request includes a service invocation terminal identifier, a service name and an invocation identifier, and the invocation identifier is used to uniquely identify a service invocation link corresponding to the service invocation request .

The service caller is the party that initiates the service call request, and the service caller identifier may be identification information that can uniquely identify the service caller, for example, a MAC address.

In a possible implementation manner of the present invention, the service invoking end may be a client, that is, an application scenario in which the client initiates a service invocation request to the service gateway;

In another possible implementation manner of the present invention, the service invoking end may be a service provider, that is, when the service provider implements a certain service, it needs to call other services, so it needs to send services to other service providers call request.

The first sending unit 120 is configured to send the service invocation request to a corresponding service provider according to the service name.

The service gateway finds the service provider that provides the service corresponding to the service name according to the service name included in the service invocation request, and sends the service invocation request to the service provider via the first sending unit.

The second receiving unit 130 is configured to receive the calling result returned by the service provider.

After receiving the service invocation request, the service provider generates invocation results in response to the service invocation request if it does not need to invoke other services, and returns the invocation results to the service gateway, which receives the invocation results through the second receiving unit.

The second sending unit 140 is configured to send the calling result to the service calling end.

The acquiring unit 150 is configured to acquire invocation information corresponding to the service invocation request, so that the invocation analysis end analyzes the invocation information to obtain a service invocation link corresponding to the invocation identifier.

Buried points are set in the service gateway to sample the entire service invocation process to obtain invocation information. The invocation information includes service invocation end identification, service provider identification, invocation identification and invocation time information.

Analyzing the call information obtained by the service gateway obtains call data corresponding to the call identifier, and finally obtains the entire service call link of this service call.

Optionally, the performance bottleneck of the service system may also be determined according to the invocation time-consuming, where the invocation time-consuming refers to the time elapsed from initiating a service invocation to obtaining the service response.

As shown in FIG. 6 , the acquiring unit 150 includes a first recording subunit 151 , a second recording subunit 152 and a calculating subunit 153 .

The first recording subunit 151 is configured to record the first timestamp when the service invocation request is received.

The second recording subunit 152 is configured to record the second timestamp of receiving the invocation result corresponding to the invocation request.

The calculation subunit 153 is configured to calculate the time difference between the second time stamp and the first time stamp to obtain the invocation time corresponding to each service.

In the service invocation device provided in this embodiment, the service gateway receives the service invocation request, the service gateway sends the service invocation request to the corresponding service provider according to the service name, and the service invocation request includes a call identifier that uniquely identifies the current call link, and The call identifier is passed between each service provider in the entire call chain; each service call request and call result need to be forwarded through the gateway, so the service gateway can obtain call information corresponding to all service calls. The call information includes the service caller identifier, the service provider identifier, the call identifier, and the call time information. Therefore, searching for the service caller identifier and the service provider identifier corresponding to the call identifier from the call information can obtain the corresponding call identifier. Service call link. The device only needs to set buried points on the service gateway for sampling, and does not need to set buried points on both the client and the server. Therefore, the development and deployment costs of the client and server of each service are greatly reduced.

Please refer to FIG. 7 , which shows a block diagram of another service invoking apparatus according to an embodiment of the present application. The apparatus is applied to a service provider. As shown in FIG. 7 , the apparatus may include: a first receiving unit 210 , a first parsing unit 210 unit 220 , a request generating unit 230 , a first sending unit 240 , a second receiving unit 250 and a response unit 260 .

The first receiving unit 210 is configured to enable the first service provider to receive the first invocation request forwarded by the service gateway.

The first invocation request includes a first service invocation terminal identifier, a first service name and an invocation identifier, and the invocation identifier is used to uniquely identify a service invocation link corresponding to the service invocation request.

The first parsing unit 220 is configured to make the first service provider parse the first invocation request to obtain the second service name and the invocation identifier to be invoked by the first invocation request.

After receiving the first service invocation request, the first service provider parses the first service invocation request, and determines the second service name to be invoked in response to the first service invocation request.

A request generating unit 230, configured to enable the first service provider to generate a second invocation request according to the second service name, where the second invocation request includes a second service invocation end identifier, a second service name and the invocation logo.

The call identifier included in the second call request generated by the first service caller is the same as the call identifier in the first call request.

a first sending unit 240, configured to make the first service provider send the second invocation request to the service gateway;

The service gateway forwards the second invocation request to the second service provider, and the second service provider provides the service corresponding to the second service name; The invocation information obtains a service invocation link corresponding to the invocation identifier.

The second receiving unit 250 is configured to enable the first service provider to receive, through the service gateway, a second invocation result returned by the second service provider, where the second invocation result is returned by the second service provider obtained in response to the second call request.

A response unit 260, configured to make the first service provider respond to the first invocation request according to the second invocation result, generate a first invocation result, and forward the first invocation result to the service gateway through the service gateway. A first service caller that initiates the first call request.

Call the analysis terminal to process the data in the log collector, obtain the call request containing the same call ID, and determine the call relationship according to the service caller ID and the service provider ID contained in each call request, so as to obtain the corresponding call ID. Service call link. Using this method, various service invocation links can be obtained, so as to obtain the service topology of the entire microservice structure.

While obtaining the invocation relationship, the invocation analysis end determines the invocation time between services according to the invocation time information collected by the log collector, that is, the time when the service gateway receives a certain invocation request and the invocation result corresponding to the invocation request. difference between the times.

Using the service topology and the call time between services, the performance bottlenecks in the entire microservice architecture can be analyzed.

The call analysis terminal can be implemented based on the text retrieval system. The details of the call link to be viewed by entering the filter conditions. For example, you can enter the time period to filter the time period of the call to be viewed, and retrieve all the log data from the log collector. Relevant information about service calls within this time period, such as service caller ID, service provider ID, and call delay.

In the service invocation device provided in this embodiment, a buried point is set in the service gateway to sample and record each invocation in the microservice architecture, wherein the service invocation request includes the invocation identifier of the current invocation link, and the invocation identifier is in It has been passed through the entire call chain. Therefore, the service invocation link corresponding to the invocation identification can be obtained by searching the service invocation terminal identification and the service provider identification corresponding to the invocation identification from the service gateway invocation information. The device only needs to set buried points on the service gateway for sampling, and does not need to set buried points on both the client and the server. Therefore, the development and deployment costs of the client and server of each service are greatly reduced.

It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. For the same and similar parts among the various embodiments, refer to each other Can. As for the apparatus type embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant part, please refer to the partial description of the method embodiment.

Finally, it should also be noted that in this document, relational terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply these entities or that there is any such actual relationship or sequence between operations. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

The above description of the disclosed embodiments enables any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The above are only the preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the principles of the present invention, several improvements and modifications can be made. It should be regarded as the protection scope of the present invention.

Claims (10)

1. A service calling method is applied to a service gateway, and comprises the following steps:

receiving a service calling request, wherein the service calling request comprises a service calling end identifier, a service name and a calling identifier, and the calling identifier is used for uniquely marking a service calling link corresponding to the service calling request;

sending the service calling request to a corresponding service provider according to the service name;

receiving a calling result returned by the service providing terminal, and sending the calling result to a service calling terminal;

and acquiring the calling information corresponding to the service calling request so that a calling analysis end analyzes the service calling end identification, the service providing end identification and the calling identification in the calling information to obtain a service calling link corresponding to the calling identification.

2. The method of claim 1, wherein the invocation information further includes invocation time information, the invocation time information including invocation time; the process of obtaining the call time consumption comprises the following steps:

recording a first time stamp of the received service calling request and a second time stamp of a calling result corresponding to the received calling request;

and calculating the time difference between the second time stamp and the first time stamp to obtain the calling time consumption of each service.

3. The method of claim 1, wherein receiving the service invocation request comprises:

receiving the service calling request sent by the client;

or,

and receiving a service calling request for calling the second service provider, which is sent by the first service provider.

4. A service calling method is applied to a service provider, and comprises the following steps:

a first service provider receives a first calling request forwarded by a service gateway, wherein the first calling request comprises a first service calling end identifier, a first service name and a calling identifier, and the calling identifier is used for uniquely marking a service calling link corresponding to the service calling request;

the first service providing terminal analyzes the first calling request to obtain a second service name required to be called by the first calling request and the calling identifier;

the first service providing terminal generates a second calling request according to the second service name, wherein the second calling request comprises a second service calling terminal identification, a second service name and the calling identification;

the first service provider sends the second calling request to the service gateway so that the service gateway forwards the second calling request to a second service provider, and the second service provider provides a service corresponding to the second service name; and enabling the service gateway to obtain calling information, and obtaining a service calling link corresponding to the calling identifier by a calling analysis end according to the calling information.

5. The method of claim 4, further comprising:

the first service provider receives a second calling result returned by the second service provider through the service gateway, and the second calling result is obtained by the second service provider responding to the second calling request;

and the first service providing terminal responds to the first calling request according to the second calling result to generate a first calling result, and forwards the first calling result to the first service calling terminal initiating the first calling request through the service gateway.

6. A service invocation device, applied in a service gateway, the device comprising:

the first receiving unit is used for receiving a service calling request, wherein the service calling request comprises a service calling end identifier, a service name and a calling identifier, and the calling identifier is used for uniquely marking a service calling link corresponding to the service calling request;

the first sending unit is used for sending the service calling request to a corresponding service provider according to the service name;

the second receiving unit is used for receiving a calling result returned by the service providing end;

the second sending unit is used for sending the calling result to a service calling end;

and the obtaining unit is used for obtaining the calling information corresponding to the service calling request so that the calling analysis end analyzes the service calling end identifier, the service providing end identifier and the calling identifier in the calling information to obtain a service calling link corresponding to the calling identifier.

7. The apparatus according to claim 6, wherein the call information further includes call time information, the call time information includes call elapsed time, and the obtaining unit includes:

the first recording subunit is used for recording a first timestamp of the received service calling request;

the second recording subunit is used for recording a second timestamp of the calling result corresponding to the received calling request;

and the calculating subunit is configured to calculate a time difference between the second timestamp and the first timestamp, so as to obtain a call time consumption corresponding to each service.

8. The apparatus of claim 6, wherein the first receiving unit is specifically configured to:

receiving the service calling request sent by the client;

or,

and receiving a service calling request for calling the second service provider, which is sent by the first service provider.

9. A service invoking device is applied to a service provider, and the device comprises:

the first receiving unit is used for enabling a first service providing end to receive a first calling request forwarded by a service gateway, wherein the first calling request comprises a first service calling end identifier, a first service name and a calling identifier, and the calling identifier is used for uniquely marking a service calling link corresponding to the service calling request;

a first parsing unit, configured to enable the first service providing end to parse the first invocation request to obtain a second service name to be invoked by the first invocation request and the invocation identifier;

a request generating unit, configured to enable the first service provider to generate a second call request according to the second service name, where the second call request includes a second service call end identifier, a second service name, and the call identifier;

a first sending unit, configured to enable the first service provider to send the second invocation request to the service gateway, so that the service gateway forwards the second invocation request to a second service provider, where the second service provider provides a service corresponding to the second service name; and enabling the service gateway to obtain calling information, and obtaining a service calling link corresponding to the calling identifier by a calling analysis end according to the calling information.

10. The apparatus of claim 9, further comprising:

a second receiving unit, configured to enable the first service provider to receive, through the service gateway, a second invocation result returned by the second service provider, where the second invocation result is obtained by the second service provider in response to the second invocation request;

and the response unit is used for enabling the first service providing end to respond to the first calling request according to the second calling result, generating a first calling result and forwarding the first calling result to the first service calling end initiating the first calling request through the service gateway.

Images