Service calling method and device and load balancing equipment

Abstract

Embodiments of the invention disclose a service calling method and device and load balancing equipment. The method is applied to the load balancing equipment, and data consistency is kept between different load balancing equipment through data synchronization. The method comprises the steps that when a service calling request submitted by a first service is obtained (wherein the first service and a second service are services registered in different registration centers), based on a link between load balancing equipment corresponding to the first service and load balancing equipment corresponding to the second service to be called, service routing information corresponding to an identifier of the second service is pulled from the registration center corresponding to the second service, and then the service routing information can be provided for the first service so as to allow the first service to access the second service based on the service routing information to obtain data corresponding to the service calling request. Through the service calling method, cross-registration-center and cross-region service calling can be realized, and the scheme of the invention is free of code invasion and relatively high in expandability.

Description

technical field [0001] This document relates to the field of computer technology, in particular to a service invocation method, device and load balancing equipment. Background technique [0002] After having the registration center, each service only needs to know the service identifier (such as the service name, etc.) when invoking other services, and the service call can be made in the registration center through the service identifier. [0003] For service registration, the logic of service registration and service cancellation needs to be written into the code of the business system (such as implanting the corresponding SDK (Software Development Kit, software development kit), etc.), when a service is started, the service's The information is written into the registration center. When a service is offline, the relevant information of the service is canceled. Different business systems usually require different programming languages ​​to implement the same set of logic. O...

AI Technical Summary

Problems solved by technology

For service discovery, the registration center needs to establish a push-pull model with the service (that is, it needs to inject corresponding processing logic (such as implanting the corresponding SDK, etc.)). Through this push-pull model, the service needs to cache the application metadata list locally, and needs to periodically or Re-obtain application metadata when needed, and services registered in different registration centers cannot complete service discovery processing, and the above processing also has a strong intrusion on the corresponding business, and the coupling is high

Images