CN111930541A - Dynamic calling method and system for GRPC (Global positioning System) service - Google Patents
Dynamic calling method and system for GRPC (Global positioning System) service Download PDFInfo
- Publication number
- CN111930541A CN111930541A CN202010828287.2A CN202010828287A CN111930541A CN 111930541 A CN111930541 A CN 111930541A CN 202010828287 A CN202010828287 A CN 202010828287A CN 111930541 A CN111930541 A CN 111930541A
- Authority
- CN
- China
- Prior art keywords
- request
- grpc
- service
- grpc service
- calling
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- 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/549—Remote execution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a dynamic calling method and a system of GRPC service, wherein the method comprises the following steps: registering GRPC service, initializing GRPC service, calling GRPC service request, initiating GRPC service request, and returning request data based on GRPC service request. The calling method provided by the invention does not need to generate client code calling by importing proto any more, but can directly initiate calling; in addition, when the service is changed, the calling can be realized directly through the adjustment of the registration API, the client code does not need to be regenerated according to the modified proto in the prior art, and the client code is re-introduced, so that the research and development efficiency is effectively improved.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a GRPC service dynamic calling method and a GRPC service dynamic calling system.
Background
GRPC was developed by google and is a language neutral, platform neutral, open source remote procedure call system.
GRPC is a high-performance, open-source and generic RPC framework, mobile and HTTP/2-oriented design. C, Java and Go language versions are currently provided.
In a GRPC, a client application can directly invoke the method of a server application on another, different machine as well as invoking a local object, enabling distributed applications and services to be created more easily. Like many RPC systems, GRPC is also based on the following concept: a service is defined that specifies methods (including parameters and return types) that it can be invoked remotely. This interface is implemented at the server and runs a GRPC server to handle client calls. Having a stub at the client can be like a server. The stub needs to generate a client code according to a protobuf protocol file. That is, one service depends on a plurality of GRPC services, and stub codes of a plurality of services need to be introduced, which brings code intrusiveness to the service itself and lowers the efficiency of development. Meanwhile, if the dependent GRPC service is changed, the caller needs to re-import the service stub code, resulting in low research and development efficiency.
Disclosure of Invention
In view of the above, the present invention provides a dynamic GRPC service invocation method, which can implement direct invocation without importing stub codes when increasing GRPC service invocation, and can dynamically modify a GRPC invocation mode by re-registering when modifying a method or a parameter for a GRPC service, thereby implementing dynamic invocation and effectively improving research and development efficiency.
The invention provides a dynamic calling method of GRPC service, which comprises the following steps:
registering GRPC service;
initializing GRPC service;
calling a GRPC service request;
initiating the GRPC service request;
and returning request data based on the GRPC service request.
Preferably, the registering GRPC service includes:
the name of the GRPC service, the protobbuf protocol file, the calling address and the connection number are registered.
Preferably, the initializing GRPC service includes:
analyzing the protobbuf protocol file to obtain a user-defined schema data structure, wherein the schema data structure comprises: a list of request methods, and a data structure of request parameters and return parameters for each method;
the connection pool of the GRPC service is initialized.
Preferably, the invoking GRPC service request includes:
calling the name of the GRPC service request, the API, the request parameters in Json format, and the timeout time of the request.
Preferably, the initiating the GRPC service request includes:
serializing the request parameters in the Json format into a byte array based on the schema data structure;
polling and acquiring a connection from the connection pool, and initiating a request by taking a byte array as a request parameter according to the schema data structure;
deserializing the byte array return parameters into Json format data based on the schema data structure;
a return parameter, GrpcResponse, is constructed.
A GRPC service dynamic invocation system, comprising:
the registration module is used for registering GRPC service;
the initialization module is used for initializing GRPC service;
the calling module is used for calling the GRPC service request;
the initiating module is used for initiating the GRPC service request;
and the return module is used for returning request data based on the GRPC service request.
Preferably, the registration module is specifically configured to:
the name of the GRPC service, the protobbuf protocol file, the calling address and the connection number are registered.
Preferably, the initialization module is specifically configured to:
analyzing the protobbuf protocol file to obtain a user-defined schema data structure, wherein the schema data structure comprises: a list of request methods, and a data structure of request parameters and return parameters for each method;
the connection pool of the GRPC service is initialized.
Preferably, the calling module is specifically configured to:
calling the name of the GRPC service request, the API, the request parameters in Json format, and the timeout time of the request.
Preferably, the initiating module is specifically configured to:
serializing the request parameters in the Json format into a byte array based on the schema data structure;
polling and acquiring a connection from the connection pool, and initiating a request by taking a byte array as a request parameter according to the schema data structure;
deserializing the byte array return parameters into Json format data based on the schema data structure;
a return parameter, GrpcResponse, is constructed.
In summary, the present invention discloses a dynamic GRPC service invocation method, which includes registering GRPC service, initializing GRPC service, invoking GRPC service request, initiating GRPC service request, and returning request data based on GRPC service request. The calling method provided by the invention does not need to generate client code calling by importing proto any more, but can directly initiate calling; in addition, when the service is changed, the calling can be realized directly through the adjustment of the registration API, the client code does not need to be regenerated according to the modified proto in the prior art, and the client code is re-introduced, so that the research and development efficiency is effectively improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart of an embodiment 1 of a dynamic GRPC service invocation method disclosed in the present invention;
FIG. 2 is a flowchart of an embodiment 2 of a dynamic GRPC service invocation method disclosed in the present invention;
fig. 3 is a schematic structural diagram of an embodiment 1 of a dynamic GRPC service invocation system disclosed in the present invention;
fig. 4 is a schematic structural diagram of an embodiment 2 of a dynamic GRPC service invocation system disclosed in the present invention;
FIG. 5 is a diagram of the related UML classes disclosed in the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, which is a flowchart of embodiment 1 of a dynamic GRPC service invocation method disclosed in the present invention, the method may include the following steps:
s101, registering GRPC service;
first, a registration API (Application Programming Interface) is provided to register a GRPC service.
For example, when dynamic GRPC for the enabler service needs to be implemented, the caller registers the GRPC enabler service through the registerClient method.
S102, initializing GRPC service;
the framework then internally initializes the GRPC service. For example, the framework internally initializes the GRPC enable service.
S103, calling a GRPC service request;
the caller then constructs a GRPC service request through custom. For example, the caller constructs a GRPC request through custom to get the video-on-demand method.
S104, initiating a GRPC service request;
the caller then initiates a GRPC request through execute. For example, the caller initiates a GRPC request to get the video-on-demand method through execute.
And S105, returning request data based on the GRPC service request.
And finally, returning corresponding request data according to the initiated GRPC service request.
To sum up, in the above embodiments, the GRPC service is registered first, then the GRPC service is initialized, the GRPC service request is called, the GRPC service request is initiated, and the request data is returned based on the GRPC service request. The provided calling method does not need to generate a client code call by importing proto any more, but can directly initiate the call; in addition, when the service is changed, the calling can be realized directly through the adjustment of the registration API, the client code does not need to be regenerated according to the modified proto in the prior art, and the client code is re-introduced, so that the research and development efficiency is effectively improved.
As shown in fig. 2, which is a flowchart of embodiment 2 of a dynamic GRPC service invocation method disclosed in the present invention, the method may include the following steps:
s201, registering the name of GRPC service, protobbuf protocol file, calling address and connection number;
first, a registration API (Application Programming Interface) is provided to register a GRPC service.
Specifically, when registering the GRPC service, a name (service identifier) of the GRPC service (for service modification and invocation), a protobbuf protocol file, an invocation address, and a connection number are registered.
For example, when the dynamic GRPC of the startup service needs to be implemented, the caller registers the GRPC startup service through the register client method, that is, the caller registers the name of the GRPC startup service, the protocol file of the GRPC startup service, the call address of the GRPC startup service, and the connection number of the GRPC startup service through the register client method.
S202, resolving the protobbuf protocol file to obtain a user-defined schema data structure, wherein the schema data structure comprises: a list of request methods, and a data structure of request parameters and return parameters for each method;
the framework then internally initializes the GRPC service.
Specifically, when the GRPC service is initialized, the protobuf protocol file is firstly parsed to obtain a custom schema data structure, where the structure includes a request method list and a data structure of request parameters and return parameters of each method.
S203, initializing a connection pool of GRPC service;
meanwhile, initializing a connection pool of the GRPC service. For example, when dynamic GRPC for the enable service needs to be implemented, a connection pool of the GRPC enable service is initialized.
S204, calling the name of the GRPC service request, API, request parameters in Json format and overtime time of the request;
the caller then constructs a GRPC service request through custom.
Specifically, the caller constructs the name of the GRPC service request, API, request parameters in Json format, and timeout time of the request through custom.
For example, when a dynamic GRPC for the start-up service needs to be implemented, the caller constructs, through the custom, the name of a request for the GRPC start-up service, an API for the acquisition start-up video method of the GRPC start-up service, request parameters in the Json format, and timeout time of the request.
S205, serializing the request parameters in the Json format into byte arrays based on the schema data structure;
the caller then initiates a GRPC request through execute.
Specifically, firstly, serialization is performed, that is, request parameters in the Json format are serialized into byte arrays according to the schema data structure.
S206, polling and acquiring a connection from the connection pool, and initiating a request by taking a byte array as a request parameter according to the schema data structure;
then, polling and acquiring a connection from the connection pool, and initiating a request by taking a byte array as a request parameter according to a schema data structure;
s207, deserializing the byte array return parameters into Json format data based on the schema data structure;
and then, performing deserialization, namely deserializing the byte array return parameters into Json format data according to the schema data structure.
S208, constructing a return parameter GrpcResponse;
then, a return parameter, GrpcResponse, is constructed.
And S209, returning request data based on the GRPC service request.
And finally, returning corresponding request data according to the initiated GRPC service request.
In summary, the dynamic GRPC service invocation method provided by the present invention does not need to import stub codes to implement direct invocation when GRPC service invocation is added; meanwhile, when the method or the parameters of the GRPC service are modified, the GRPC calling mode can be dynamically modified through a re-registration mode, and dynamic calling is realized.
As shown in fig. 3, which is a schematic structural diagram of embodiment 1 of a dynamic GRPC service invocation system disclosed in the present invention, the system may include:
a registration module 301, configured to register a GRPC service;
first, a registration API (Application Programming Interface) is provided to register a GRPC service.
For example, when dynamic GRPC for the enabler service needs to be implemented, the caller registers the GRPC enabler service through the registerClient method.
An initialization module 302, configured to initialize a GRPC service;
the framework then internally initializes the GRPC service. For example, the framework internally initializes the GRPC enable service.
A calling module 303, configured to call a GRPC service request;
the caller then constructs a GRPC service request through custom. For example, the caller constructs a GRPC request through custom to get the video-on-demand method.
An initiating module 304, configured to initiate a GRPC service request;
the caller then initiates a GRPC request through execute. For example, the caller initiates a GRPC request to get the video-on-demand method through execute.
A return module 305 for returning the request data based on the GRPC service request.
And finally, returning corresponding request data according to the initiated GRPC service request.
To sum up, in the above embodiments, the GRPC service is registered first, then the GRPC service is initialized, the GRPC service request is called, the GRPC service request is initiated, and the request data is returned based on the GRPC service request. The provided calling method does not need to generate a client code call by importing proto any more, but can directly initiate the call; in addition, when the service is changed, the calling can be realized directly through the adjustment of the registration API, the client code does not need to be regenerated according to the modified proto in the prior art, and the client code is re-introduced, so that the research and development efficiency is effectively improved.
As shown in fig. 4, which is a schematic structural diagram of embodiment 2 of a dynamic GRPC service invocation system disclosed in the present invention, the system may include:
a registration module 401, configured to register a name of a GRPC service, a protobbuf protocol file, a call address, and a connection number;
first, a registration API (Application Programming Interface) is provided to register a GRPC service.
Specifically, when registering the GRPC service, a name (service identifier) of the GRPC service (for service modification and invocation), a protobbuf protocol file, an invocation address, and a connection number are registered. As shown in fig. 5, a related UML class diagram is provided for the present invention.
For example, when the dynamic GRPC of the startup service needs to be implemented, the caller registers the GRPC startup service through the register client method, that is, the caller registers the name of the GRPC startup service, the protocol file of the GRPC startup service, the call address of the GRPC startup service, and the connection number of the GRPC startup service through the register client method.
An initialization module 402, configured to parse a protobbuf protocol file to obtain a custom schema data structure, where the schema data structure includes: a list of request methods, and a data structure of request parameters and return parameters for each method;
the framework then internally initializes the GRPC service.
Specifically, when the GRPC service is initialized, the protobuf protocol file is firstly parsed to obtain a custom schema data structure, where the structure includes a request method list and a data structure of request parameters and return parameters of each method.
An initializing module 402, configured to initialize a connection pool of a GRPC service;
meanwhile, initializing a connection pool of the GRPC service. For example, when dynamic GRPC for the enable service needs to be implemented, a connection pool of the GRPC enable service is initialized.
A calling module 403, configured to call a name of the GRPC service request, an API, a request parameter in a Json format, and timeout time of the request;
the caller then constructs a GRPC service request through custom.
Specifically, the caller constructs the name of the GRPC service request, API, request parameters in Json format, and timeout time of the request through custom.
For example, when a dynamic GRPC for the start-up service needs to be implemented, the caller constructs, through the custom, the name of a request for the GRPC start-up service, an API for the acquisition start-up video method of the GRPC start-up service, request parameters in the Json format, and timeout time of the request.
An initiating module 404, configured to serialize the request parameters in the Json format into a byte array based on the schema data structure;
the caller then initiates a GRPC request through execute.
Specifically, firstly, serialization is performed, that is, request parameters in the Json format are serialized into byte arrays according to the schema data structure.
The initiating module 404 is further configured to poll the connection pool to obtain a connection, and initiate a request with a byte array as a request parameter according to the schema data structure;
then, polling and acquiring a connection from the connection pool, and initiating a request by taking a byte array as a request parameter according to a schema data structure;
the initiating module 404 is further configured to deserialize the byte array return parameters into Json format data based on the schema data structure;
and then, performing deserialization, namely deserializing the byte array return parameters into Json format data according to the schema data structure.
The initiating module 404 is further configured to construct a return parameter, GrpcResponse.
Then, a return parameter, GrpcResponse, is constructed.
A return module 405, configured to return the request data based on the GRPC service request.
And finally, returning corresponding request data according to the initiated GRPC service request.
In summary, the dynamic GRPC service invocation system provided by the present invention does not need to import stub codes to implement direct invocation when increasing GRPC service invocation; meanwhile, when the method or the parameters of the GRPC service are modified, the GRPC calling mode can be dynamically modified through a re-registration mode, and dynamic calling is realized.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The previous description of the disclosed embodiments is provided to enable 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 applied to 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.
Claims (10)
1. A dynamic calling method for GRPC service is characterized by comprising the following steps:
registering GRPC service;
initializing GRPC service;
calling a GRPC service request;
initiating the GRPC service request;
and returning request data based on the GRPC service request.
2. The method of claim 1, wherein registering for GRPC services comprises:
the name of the GRPC service, the protobbuf protocol file, the calling address and the connection number are registered.
3. The method of claim 2, wherein initializing the GRPC service comprises:
analyzing the protobbuf protocol file to obtain a user-defined schema data structure, wherein the schema data structure comprises: a list of request methods, and a data structure of request parameters and return parameters for each method;
the connection pool of the GRPC service is initialized.
4. The method of claim 3, wherein invoking the GRPC service request comprises:
calling the name of the GRPC service request, the API, the request parameters in Json format, and the timeout time of the request.
5. The method of claim 4, wherein the initiating the GRPC service request comprises:
serializing the request parameters in the Json format into a byte array based on the schema data structure;
polling and acquiring a connection from the connection pool, and initiating a request by taking a byte array as a request parameter according to the schema data structure;
deserializing the byte array return parameters into Json format data based on the schema data structure;
a return parameter, GrpcResponse, is constructed.
6. A GRPC service dynamic invocation system, comprising:
the registration module is used for registering GRPC service;
the initialization module is used for initializing GRPC service;
the calling module is used for calling the GRPC service request;
the initiating module is used for initiating the GRPC service request;
and the return module is used for returning request data based on the GRPC service request.
7. The system of claim 6, wherein the registration module is specifically configured to:
the name of the GRPC service, the protobbuf protocol file, the calling address and the connection number are registered.
8. The system of claim 7, wherein the initialization module is specifically configured to:
analyzing the protobbuf protocol file to obtain a user-defined schema data structure, wherein the schema data structure comprises: a list of request methods, and a data structure of request parameters and return parameters for each method;
the connection pool of the GRPC service is initialized.
9. The system of claim 8, wherein the calling module is specifically configured to:
calling the name of the GRPC service request, the API, the request parameters in Json format, and the timeout time of the request.
10. The system of claim 9, wherein the initiation module is specifically configured to:
serializing the request parameters in the Json format into a byte array based on the schema data structure;
polling and acquiring a connection from the connection pool, and initiating a request by taking a byte array as a request parameter according to the schema data structure;
deserializing the byte array return parameters into Json format data based on the schema data structure;
a return parameter, GrpcResponse, is constructed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010828287.2A CN111930541A (en) | 2020-08-17 | 2020-08-17 | Dynamic calling method and system for GRPC (Global positioning System) service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010828287.2A CN111930541A (en) | 2020-08-17 | 2020-08-17 | Dynamic calling method and system for GRPC (Global positioning System) service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111930541A true CN111930541A (en) | 2020-11-13 |
Family
ID=73304413
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010828287.2A Pending CN111930541A (en) | 2020-08-17 | 2020-08-17 | Dynamic calling method and system for GRPC (Global positioning System) service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111930541A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113515319A (en) * | 2021-04-20 | 2021-10-19 | 北京科东电力控制系统有限责任公司 | Method for client to dynamically call server through GRPC |
| CN115509513A (en) * | 2022-11-16 | 2022-12-23 | 深圳市明源云采购科技有限公司 | GRPC service layer code generation method, device, equipment and storage medium |
| EP4145795A1 (en) * | 2021-09-03 | 2023-03-08 | Juniper Networks, Inc. | Runtime extensible application programming interface server |
| US11799737B1 (en) | 2021-06-30 | 2023-10-24 | Juniper Networks, Inc. | Topology-based graphical user interface for network management systems |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170339002A1 (en) * | 2016-05-23 | 2017-11-23 | Arista Networks, Inc. | Method and system for using an openconfig architecture on network elements |
| WO2018116933A1 (en) * | 2016-12-22 | 2018-06-28 | 日本電信電話株式会社 | Rpc conversion process system and rpc conversion method |
| CN108509282A (en) * | 2018-02-08 | 2018-09-07 | 厦门快商通信息技术有限公司 | Across the language call service administering methods of rpc based on golang reflection technologies |
| US20190102423A1 (en) * | 2017-09-29 | 2019-04-04 | Oracle International Corporation | System and method for providing an interface for a blockchain cloud service |
| US20200034272A1 (en) * | 2018-07-28 | 2020-01-30 | International Business Machines Corporation | Handling request data with type safety in a remote service |
| WO2020041187A1 (en) * | 2018-08-20 | 2020-02-27 | Jpmorgan Chase Bank, N.A. | System and method for service-to-service authentication |
| US20200183657A1 (en) * | 2018-12-05 | 2020-06-11 | Electronics And Telecommunications Research Institute | Apparatus and method for executing function |
-
2020
- 2020-08-17 CN CN202010828287.2A patent/CN111930541A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170339002A1 (en) * | 2016-05-23 | 2017-11-23 | Arista Networks, Inc. | Method and system for using an openconfig architecture on network elements |
| WO2018116933A1 (en) * | 2016-12-22 | 2018-06-28 | 日本電信電話株式会社 | Rpc conversion process system and rpc conversion method |
| US20190102423A1 (en) * | 2017-09-29 | 2019-04-04 | Oracle International Corporation | System and method for providing an interface for a blockchain cloud service |
| CN108509282A (en) * | 2018-02-08 | 2018-09-07 | 厦门快商通信息技术有限公司 | Across the language call service administering methods of rpc based on golang reflection technologies |
| US20200034272A1 (en) * | 2018-07-28 | 2020-01-30 | International Business Machines Corporation | Handling request data with type safety in a remote service |
| WO2020041187A1 (en) * | 2018-08-20 | 2020-02-27 | Jpmorgan Chase Bank, N.A. | System and method for service-to-service authentication |
| US20200183657A1 (en) * | 2018-12-05 | 2020-06-11 | Electronics And Telecommunications Research Institute | Apparatus and method for executing function |
Non-Patent Citations (3)
| Title |
|---|
| GITLEE: "Protobuf Schema动态解析", pages 0001, Retrieved from the Internet <URL:https://blog.csdn.net/llll20000/article/details/79304059> * |
| GOLANG中国: "基于gRPC的注册发现与负载均衡的原理和实战", pages 0001 - 189, Retrieved from the Internet <URL:https://phpmianshi.com/?id=1599> * |
| 镇天雷帝: "C++之序列化", pages 0004, Retrieved from the Internet <URL:https://blog.csdn.net/qq_41980769/article/details/107250278> * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113515319A (en) * | 2021-04-20 | 2021-10-19 | 北京科东电力控制系统有限责任公司 | Method for client to dynamically call server through GRPC |
| CN113515319B (en) * | 2021-04-20 | 2023-08-08 | 北京科东电力控制系统有限责任公司 | Method for dynamically calling server by client through GRPC |
| US11799737B1 (en) | 2021-06-30 | 2023-10-24 | Juniper Networks, Inc. | Topology-based graphical user interface for network management systems |
| EP4145795A1 (en) * | 2021-09-03 | 2023-03-08 | Juniper Networks, Inc. | Runtime extensible application programming interface server |
| CN115509513A (en) * | 2022-11-16 | 2022-12-23 | 深圳市明源云采购科技有限公司 | GRPC service layer code generation method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111930541A (en) | Dynamic calling method and system for GRPC (Global positioning System) service | |
| CN110191164B (en) | Distributed service access system and method | |
| CN106919509B (en) | Client generation method and device and electronic equipment | |
| CN110198247B (en) | Interface test method and system | |
| CN110187902B (en) | Project transformation method, device, equipment and storage medium based on spring boot | |
| CN112114979A (en) | Remote procedure call method and device | |
| CN112565443A (en) | Internet of things data analysis method, device, equipment and storage medium | |
| CN111010438B (en) | Remote procedure calling method, device, server and storage medium | |
| WO2020238344A1 (en) | Rapid sdk integration method and apparatus based on block chain, device and device and storage medium | |
| CN109587272B (en) | Method and device for optimizing microservice and electronic equipment | |
| CN105955833B (en) | Engine calling method and device | |
| CN109522139B (en) | Data table service generation and calling method, device, equipment and storage medium | |
| AU2015369925A1 (en) | Computer readable storage media for dynamic service deployment and methods and systems for utilizing same | |
| US20120210306A1 (en) | System and Method for Application Testing | |
| CN113821352A (en) | Remote service calling method and device | |
| CN101021786A (en) | Method for calling universal structure | |
| CN109634752B (en) | Client request processing method and system based on page gateway | |
| CN111988398A (en) | Data acquisition method, API gateway and medium | |
| CN114222003A (en) | Service calling method, system, device, equipment and storage medium | |
| CN114301970B (en) | Service calling method, device, electronic equipment and storage medium | |
| CN108769249B (en) | iOS high-performance high-expansion network device, implementation method, server and medium | |
| CN111309407A (en) | Processing method and device for integrated third-party library | |
| WO2018121652A1 (en) | Method and device for connecting wireless access point through application in user equipment | |
| CN115811481A (en) | Interactive service testing method and device, computer equipment and storage medium | |
| CN113645259B (en) | Micro-service elastic expansion method, system and related equipment |
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 |