Non-stub micro-service calling method and device

Abstract

The invention provides a stub-free micro-service calling method and device, and relates to the field of computers and finance, and the method comprises the steps: receiving a service calling request; when a service interface name in the service calling request and a corresponding method list exist in the latest method list cache, acquiring instance information of a service provider from a registration center; converting the service calling request into a conventional proxy request; sending the conventional agent class request to the service provider according to the instance information, and performing remote calling of the service. The problem of strong coupling of the service calling party and the service provider on the service stub is fundamentally solved, the service calling party can carry out service calling without loading the service stub, and the performance and stability of the calling party are improved.

Description

technical field [0001] The invention relates to the computer field and the financial field, in particular to a method and device for invoking a microservice without a stub. Background technique [0002] Due to the commonality of high-level programming languages, the existing microservice call model generally needs to be defined before calling, so most remote calls are completed based on service stubs. After the consumer loads the service stub, it calls the method in the service stub. The bottom layer of the distributed RPC framework is based on the service stub to construct the remote call proxy class, which encapsulates the remote call steps such as service discovery, request serialization, network transmission, and exception handling layer by layer, and realizes the remote call method in the service provided by the provider. [0003] However, due to the strong coupling relationship between the microservice invocation model and the service stub in this way, when the caller...

AI Technical Summary

Problems solved by technology

[0003] However, due to the strong coupling relationship between the microservice calling model and the service stub in this way, when the caller is a third-party application, it is inconvenient for the provider to provide the service stub, or when the caller and provider programming languages ​​are not compatible with each other, The service stub cannot be loaded, or after the provider updates the service stub, the caller cannot update the stub dynamically and synchronously in the memory at runtime, which causes the caller to fail to make microservice calls

Therefore, the strong coupling relationship between the provider and the caller creates great resistance to the transformation of the microservice architecture of the product

[0004] There is also the problem of incompatibility of deserialization types between the existing generalized call protocol and the conventional stub proxy class call protocol, so the generalized call protocol cannot be directly used through the existing microservice call model

Images