CN111866140B

CN111866140B - Fusion management device, management system, service calling method and medium

Info

Publication number: CN111866140B
Application number: CN202010704593.5A
Authority: CN
Inventors: 林梅贞
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-07-21
Filing date: 2020-07-21
Publication date: 2023-09-15
Anticipated expiration: 2040-07-21
Also published as: CN111866140A

Abstract

The embodiment of the application discloses fusion management equipment, a management system, a service calling method and a medium, and belongs to the technical field of computers. The fusion management equipment is configured with a fusion operation environment, wherein the fusion operation environment is used for operating combined service and micro service, the fusion management equipment further comprises a first registry, the first registry is used for receiving an address acquisition request of a first service to a second service, and the first service and the second service are different types of service; the first registry is further configured to obtain address information of the second service, and send the address information to the first service; the first service is used for receiving the address information and initiating a call request carrying the address information. The unified management of different types of services is realized, the problem that the different types of services cannot be called mutually is avoided, the functions are expanded, and the flexibility is improved.

Description

Fusion management device, management system, service calling method and medium

Technical Field

The embodiment of the application relates to the technical field of computers, in particular to fusion management equipment, a management system, a service calling method and a medium.

Background

With the development of computer technology, a micro-service architecture is proposed at present, which can divide an application program into one or more micro-services, each micro-service performs a function, and each micro-service is independent from each other, and each micro-service can be updated, deployed or extended independently. And the traditional service belongs to a combined service, and each traditional service combines a plurality of functions and can realize at least two functions. The operating environments of the micro service and the traditional service are different, so that the two types of services cannot be called mutually.

Disclosure of Invention

The embodiment of the application provides a fusion management device, a management system, a service calling method and a medium, which realize the mutual calling between a combined service and a micro service, and the technical scheme is as follows:

in one aspect, a converged management device is provided, the converged management device is configured with a converged running environment, the converged running environment is used for running combined services and micro services, and the converged management device further comprises a first registry;

the first registry is configured to receive an address acquisition request of a first service for a second service, where the first service and the second service are different types of services;

The first registry is further configured to obtain address information of the second service, and send the address information to the first service;

the first service is configured to receive the address information, initiate a call request carrying the address information, and call the second service corresponding to the address information.

Optionally, the fusion management device is further configured to issue a registration interface to a terminal, where the terminal is configured to display the registration interface, obtain the input registration information through the registration interface, and send the registration request to the first registry.

In another aspect, there is provided a management system including the fusion management device and the micro-service management device described in the above aspects;

the micro-service management device is configured with a micro-service running environment, the micro-service running environment is used for running micro-services, and the micro-service management device comprises a second registration center;

the first registry is synchronized with the micro-services registered by the second registry.

Optionally, the management system further comprises a plurality of node devices;

the fusion management device is further configured to issue services to the plurality of node devices, and allocate corresponding address information to the services issued on each node device, where the address information corresponding to the services issued on different node devices is different.

On the other hand, the service calling method is applied to the fusion management equipment, the fusion management equipment is configured with a fusion operation environment, the fusion operation environment is used for operating the combined service and the micro service, and the fusion management equipment further comprises a first registration center; the method comprises the following steps:

receiving an address acquisition request of a first service to a second service through the first registration center, wherein the first service and the second service are different types of services;

acquiring address information of the second service through the first registry, and sending the address information to the first service;

and receiving the address information through the first service, and initiating a call request carrying the address information, wherein the call request is used for calling the second service corresponding to the address information.

Optionally, the fusion management device further includes an interface gateway, the receiving, by the first service, the address information, and initiating a call request carrying the address information, including:

receiving the address information through the first service, and sending the call request to the interface gateway, wherein the call request also carries verification information;

And verifying the verification information through the interface gateway, and sending the call request to the second service corresponding to the address information under the condition that the verification is passed.

Optionally, obtaining, by the first registry, address information of the second service includes:

determining at least one available node device of the second service through the first registry, wherein the available node device refers to the published node device which can be called by the second service;

and determining address information corresponding to any available node equipment through the first registration center, wherein the address information is obtained by distributing the second service to the available node equipment.

Optionally, the determining, by the first registry, at least one available node device of the second service includes:

and determining, by the first registry, the corresponding at least one available node device according to at least one device identifier in the set of available nodes of the second service.

Optionally, before the obtaining, by the first registry, the address information of the second service, the method further includes:

sending detection requests to a plurality of node devices which have issued the second service, wherein the detection requests are used for requesting to detect whether the second service issued on the corresponding node device can be invoked or not;

Receiving detection results returned by each node device, and determining at least one available node device of the second service according to the received detection results;

a device identification of the at least one available node device is added to the set of available nodes of the second service.

Optionally, after receiving the detection result returned by each node device, the method further includes:

determining at least one unavailable node device of the second service according to the plurality of detection results;

the at least one unavailable node device is added to the set of unavailable nodes of the second service.

Optionally, after the adding the at least one unavailable node device to the unavailable node set of the second service, the method further comprises:

acquiring equipment identifiers meeting an available condition in the unavailable node set under the condition that the historical times of the equipment identifiers added to the unavailable node set do not exceed the reference times and the preservation time of the equipment identifiers in the unavailable node set after the detection exceeds the reference time when the number of the node devices in the available node set is smaller than the reference number;

And moving the node equipment corresponding to the equipment identifier meeting the available condition to the available node set.

Optionally, the second service is a micro service, and the receiving, by the first registry, an address acquisition request of the first service to the second service includes:

under the condition that the second service is not registered, sending the address acquisition request to a second registry through the first registry, and receiving address information of the second service returned by the second registry;

the second registration center is located in a micro-service management device, and the micro-service management device is configured with a micro-service running environment, wherein the micro-service running environment is used for running micro-services.

Optionally, the method further comprises:

receiving a registration request of any service through the first registration center, wherein the registration request carries registration information of the service;

and registering the service through the first registration center according to the registration information, wherein the service is a micro service or a combined service.

Optionally, after the registering the service according to the registration information by the first registry, the method further includes:

And distributing the service to a plurality of node devices, and respectively distributing corresponding address information for the service distributed on each node device, wherein the address information corresponding to the service distributed on different node devices is different.

Optionally, the service is a micro service, and after the registration request of any service is received through the first registration center, the method further includes:

sending a synchronous registration request to a second registration center through the first registration center, wherein the synchronous registration request carries the registration information, so that the second registration center registers the service according to the registration information;

Optionally, the method further comprises:

receiving a synchronous registration request sent by a second registration center through the first registration center, wherein the synchronous registration request carries registration information of any service to be registered;

registering the service through the first registration center according to the registration information;

Optionally, before the receiving, by the first registry, a registration request for any service in the converged running environment, the method further includes:

and issuing a registration interface to a terminal, wherein the terminal is used for displaying the registration interface, acquiring the input registration information through the registration interface and sending the registration request to the first registration center.

In another aspect, a computer-readable storage medium having stored therein at least one instruction that is loaded and executed by a processor to implement operations performed in a service invocation method as described in the above aspect is provided.

In another aspect, a computer program product or a computer program is provided, the computer program product or the computer program comprising computer instructions stored in a computer readable storage medium, the computer instructions being read from the computer readable storage medium by a processor of the computer device, the computer instructions being executed by the processor such that the computer device implements the operations performed in the service invocation method as described in the above aspect.

The technical scheme provided by the embodiment of the application has the beneficial effects that at least:

the fusion management equipment, the management system, the service calling method and the medium provided by the embodiment of the application have the advantages that the fusion operation environment is configured in the fusion management equipment, and the micro service and the combined service can be operated in the fusion operation environment, so that the two types of services are managed, and the unified management of different types of services is realized. In addition, the different types of services running in the running environment can be mutually called, so that the problem that the different types of services cannot be mutually called is avoided, functions are expanded, and flexibility is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a service management system according to an embodiment of the present application;

FIG. 2 is a schematic diagram of another service management system according to an embodiment of the present application;

FIG. 3 is a schematic diagram of another service management system according to an embodiment of the present application;

FIG. 4 is a flowchart of a service registration method according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a service registration process provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of another service registration process provided by an embodiment of the present application;

FIG. 7 is a flowchart of a service invocation method provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of a service invocation procedure provided by an embodiment of the present application;

FIG. 9 is a flow chart of a method for collection management provided by an embodiment of the present application;

fig. 10 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the following detailed description of the embodiments of the present application will be given with reference to the accompanying drawings.

It is to be understood that the terms "first," "second," and the like, as used herein, may be used to describe various concepts, but are not limited by these terms unless otherwise specified. These terms are only used to distinguish one concept from another. For example, a first service may be referred to as a second service and a second service may be referred to as a first service without departing from the scope of the application.

The terms "each," "plurality," "at least one," and the like, as used herein, include two or more, each referring to each of a corresponding plurality, at least one referring to one or more. For example, the plurality of node devices includes 20 node devices, each node device referring to each of the 20 node devices.

In order to facilitate understanding of the embodiments of the present application, keywords related to the embodiments of the present application are explained:

micro-services: a micro-service architecture, an application comprising a micro-service that communicates through a well-defined API (Application Programming Interface, application program interface). Each micro-service performs a function, and each micro-service is independent of the other, and each micro-service can be independently updated, deployed or expanded to meet the requirements of an application program for a specific function.

Combined service: and a service formed by combining a plurality of functions, wherein each combined service can realize at least two functions. For example, a composite service is an application that can perform multiple functions.

Fig. 1 is a schematic diagram of a management system according to an embodiment of the present application. Referring to fig. 1, the implementation environment includes: the fusion management device 101 and the micro service management device 102, the fusion management device 101 and the micro service management device 102 being connected through a network.

The converged management device 101 and the micro service management device 102 may be servers, which may be independent physical servers, may be a server cluster or a distributed system formed by a plurality of physical servers, and may also be cloud servers that provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content distribution networks), and basic cloud computing services such as big data and artificial intelligent platforms.

In the embodiment of the present application, the fusion management device 101 is configured with a fusion operation environment, where the fusion operation environment is used for operating a combined service and a micro service, so that management of the micro service and the combined service can be implemented, for example, registration, release or call of the micro service and the combined service can be performed; the micro service management apparatus 102 is configured with a micro service execution environment in which micro services are executed, and management of the micro services, for example, registration, distribution, or invocation of the micro services can be achieved.

The micro-service running environment comprises a Spring Cloud running environment, a Kubernetes+Istio running environment or other micro-service running environments.

Optionally, referring to fig. 2, the management system further includes a plurality of node devices 103, and the plurality of node devices 103 are connected to the fusion management device 101. The fusion management device 101 can issue the registered service to the node device 103.

Optionally, referring to fig. 3, the management system further comprises at least one terminal 104, the terminal 104 being connected to the fusion management device 101. The terminal 104 is configured to provide a registration interface, a configuration interface, or other interfaces for services to the user, so as to implement registration, configuration, or other operations of the services through man-machine interaction. Alternatively, the terminal 104 can provide an interface to the user through an application, web page in a browser, or other form.

The method provided by the embodiment of the application can be applied to various scenes.

For example, in a service invocation scenario.

When a user uses a function in an application program, if the user needs to combine another function, the service calling method provided by the embodiment of the application is adopted to call the service corresponding to the other function to be combined.

In the embodiment of the application, the fusion management equipment realizes unified management of the combined service and the micro service by registering, issuing and calling the combined service or the micro service. The registration process and the distribution process of the service are explained below.

Fig. 4 is a flowchart of a service registration method according to an embodiment of the present application. The embodiment of the application is applied to fusion management equipment and a terminal, and referring to fig. 4, the method comprises the following steps:

401. and the fusion management equipment transmits a registration interface to the terminal.

In the process of registering the service, the fusion management device needs to acquire the registration information of the service to be registered first, so that the fusion management device registers the service according to the registration information. Wherein the service to be registered is a micro service or a combined service.

In the embodiment of the application, the fusion management equipment distributes the registration interface to the terminal and enables the user to configure the registration information of the service through the registration interface displayed by the terminal. The terminal is any terminal connected with the converged management device through a network, and the terminal can be a portable, pocket-sized, handheld and other types of terminals, such as a smart phone, a tablet personal computer, a notebook computer, a desktop computer and the like.

402. The terminal displays a registration interface, acquires input registration information through the registration interface, and sends the registration information to a first registration center.

After receiving the registration interface issued by the fusion management device, the terminal displays the registration interface, so that the user inputs registration information in the registration interface. Optionally, the terminal is provided with a target application program, and a registration interface is displayed through the target application program; or the terminal displays a registration interface through a webpage in the browser; alternatively, the registration interface may be displayed in other ways.

The registration information includes at least a service identification, an IP address (Internet Protocol Address, network protocol address), a port, etc. of the service. Wherein, the service identifier is the name of the service, the ID (Identity) of the service, etc., each service has a unique service identifier; the IP address is the address of the equipment where the service is located; the ports are ports available when the service is invoked.

Optionally, if the service is a combined service, the registration information further includes an application identification of an application program to which the service is applied.

The terminal acquires the registration information input by the user through the registration interface, and sends a registration request to the first registration center, wherein the registration request carries the registration information. The first registry is a registry in the converged management device, and is capable of registering micro services and combined services.

In addition, in one possible implementation manner, the fusion management device can also issue other interfaces to the terminal, for example, issue a detection interface, through which a user can input detection information of the service, so as to facilitate subsequent detection of the service according to the detection information; or, issuing a service display interface through which the user can view each service registered by the first registry.

403. The fusion management device receives a registration request of any service through the first registration center.

In the embodiment of the application, the fusion management device is configured with a fusion operation environment, and the fusion operation environment is used for operating the combined service and the micro service, so that the combined service or the micro service can be registered through the first registration center. The first registration center receives the registration request and analyzes the registration request to obtain registration information carried in the registration request.

404. The fusion management device registers the service according to the registration information through the first registration center.

After receiving the registration request, the first registration center analyzes the registration request to obtain registration information in the registration request, and registers the service in the first registration center according to the registration information, namely, stores the registration information in the first registration center.

In one possible implementation manner, the registration request further carries verification information, before the first registry receives the registration request, security verification needs to be performed on the registration request, and in the case that verification is passed, the service is registered through the first registry according to the registration information.

For example, referring to fig. 5, by logging in the external system 501 through the application admission gateway 502, a user registers a service in the fusion management device 503 by inputting registration information through a registration interface displayed at the external system. The external system 501 is a terminal connected to the fusion management device 503, and the application admission gateway 502 is a gateway that verifies login information of a user when the user logs in to the external system 501, and can log in to the external system 501 to perform an operation when the verification is passed. In addition to service registration, the converged management device 503 can implement service authentication, service routing, load balancing, protocol conversion, and the like.

In addition, in one possible implementation manner, after the fusion management device registers the service, the registered service can be issued to the terminal, the terminal displays the registered service through the service display interface, and the user can view the registered service through the service display interface. And can realize the inquiry of various information of registered services.

405. The fusion management equipment distributes services to the plurality of node equipment, and distributes corresponding address information for the services distributed on each node equipment.

Optionally, the fusion management device stores device identifiers of a plurality of node devices, and after registering the service, obtains the device identifiers of the plurality of node devices, so as to issue the service to the node device corresponding to the device identifiers through the first registration center.

The fusion management equipment distributes corresponding address information for the service issued on each node equipment, and the address information corresponding to the service issued on different node equipment is different, so that the service can be invoked according to the address information when the service is invoked later.

The address information is any one of an IP address and a domain name, the IP address is the same as the IP address of the node device, and the domain name is a name corresponding to the IP address.

In one possible implementation, the IP address of the node device and the device identifier are stored together in the converged management device, and when address information is allocated, the IP address of the node device is first acquired, and then the IP address is converted into a corresponding domain name.

Optionally, the convergence management device sends the IP address of the service to other devices including DNS (Domain Name System ) service, the other devices convert the IP address into a corresponding domain name, and the converted domain name is returned to the convergence management device; or the fusion management equipment converts the IP address into a corresponding domain name through the DNS service of the fusion management equipment.

Optionally, a domain name is generated for the service by using a domain name generic method. That is, the domain name prefixes of the services published in the same node apparatus are the same.

In one possible implementation, if the registered service is a micro service, the converged management device can synchronously register the micro service to the micro service management device.

The fusion management device sends a synchronous registration request to a second registration center through the first registration center so that the second registration center registers the service according to the registration information. Wherein the second registry is a registry in the micro service management device.

The micro-service management equipment receives a synchronous registration request sent by the first registration center through the second registration center, and registers the service through the second registration center according to the registration information. Wherein the registration information of the service in the second registration center is the same as the registration information of the service in the first registration center, and the address information of the service in the micro service management apparatus is the same as the address information of the service in the converged management apparatus. Therefore, after receiving the synchronous registration request, the micro-service management device only needs to store the registration information and the address information of the service to the second registration center, and does not need to issue the service to the node device.

For example, referring to fig. 6, the first service is a service caller 601, the second service is a service provider 602, and after the first registry 603 issues the second service to the node device, the first registry 603 obtains address information of the second service, where the first registry 603 synchronizes the address information and the registration information of the second service to the second registry 604.

In the above embodiments, the service registration is described only by taking the case of receiving registration information through the registration interface. In another embodiment, the micro services registered in the micro service management device can be synchronously registered to the fusion management device using a grayscale plan. That is, when the service is a micro service, under the condition that the registration information in the fusion management device and the micro service management device can be synchronized, the fusion management device receives a synchronous registration request sent by the second registration center through the first registration center, and registers the service according to the registration information through the first registration center, wherein the synchronous registration request carries the registration information of any service to be registered. The method can realize synchronous registration of the micro-service to be registered in the fusion management device and the micro-service management device.

The grayscale plan refers to that if a micro service management device has been used before using a fusion management device, in which a part of micro services have been registered, the registered micro services can be synchronized to the fusion management device.

For example, referring to fig. 5, after the micro service is registered in the fusion management device 503, the micro service can be synchronously registered in the micro service framework (micro service management device) 504, and the micro service registered in the micro service framework 504 can also be synchronously registered in the fusion management device 503, so as to realize cross-environment deep fusion of the micro service.

According to the method provided by the embodiment of the application, any type of service can be registered through the registry, and different types of services are registered in the unified registry, so that unified management of different types of services can be realized through the registry. And, for the micro service, synchronization of registration in the fusion management device and registration in the micro service management device can also be achieved in the registration process.

After registering the service in the fusion management device, the registered service can be invoked, and a procedure for invoking the service will be described below.

Fig. 7 is a flowchart of a service calling method according to an embodiment of the present application. The embodiment of the application is applied to fusion management equipment, and referring to fig. 7, the method comprises the following steps:

701. an address acquisition request of a first service to a second service is received through a first registry.

In the embodiment of the application, because the micro-service and the combined service are operated in the fusion operation environment in the fusion management equipment, when the service is called, the interaction between the micro-service and the combined service can be realized, namely, the first service calls the second service, the first service and the second service are different types of services, namely, the first service is the micro-service, and the second service is the combined service; or the first service is a combined service and the second service is a micro service. The first service is a service calling party in the calling process, and the second service is a service provider in the calling process.

The address obtaining request is used for requesting to obtain address information of the second service, and the address information is a domain name or an IP address. The address acquisition request carries at least a service identification of the first service and a service identification of the second service. Wherein the service identity is the name, ID or other identity of the service. For example, the ID may be in the form of a p-ID or other format.

In one possible implementation, the first service is a service in an application program, when the first service of the application program is used and the second service needs to be called, the application program sends an address acquisition request for the second service to a first registry that registers the first service and the second service. For example, when a user pays by using an application program, the user needs to verify by face recognition, and at this time, the payment service needs to call the face recognition service to verify.

In another possible implementation manner, the first service is an application program, and when the application program is used, the application program needs to call the second service, and then sends an address acquisition request for the second service to the first registry.

Since the second service is registered through the first registry, registration information of the second service is stored in the first registry, and thus the address acquisition request is received through the first registry in the converged management device.

For example, referring to fig. 6, a service caller 601 queries a first registry 603 for address information of a service provider 602.

702. And acquiring the address information of the second service through the first registration center, and sending the address information to the first service.

Optionally, the first registry registers a second service, and since the second service has been issued to the plurality of node devices, each node device includes the second registration, the first registry stores a plurality of address information of the second service, each address information corresponding to the second service in one node device. The fusion management device selects any one address information from the plurality of address information and sends the selected address information to the first service.

Optionally, the converged management device adopts a load balancing manner to select one address information from the plurality of address information, so as to avoid that the plurality of services call the second service published on the same node device at the same time. When the address information is selected, determining whether the second service corresponding to the current address information is called by other services, if the second service corresponding to the address information is being called by other services, and the number of other services is large, at this time, address information with the number of other second services not called or less called can be selected so as to improve the calling speed.

Alternatively, the fusion management device may also acquire the address information through the micro service management device. For example, the service in the converged management device and the service in the micro service management device can be mutually called, the first registry does not register the second service, and the second registry registers the second service, and then the converged management device sends an address acquisition request to the second registry through the first registry, the micro service management device sends address information of the second service to the first registry through the second registry, and the converged management device receives the address information of the second service returned by the second registry through the first registry.

In another embodiment, if the second registry of the micro service management device does not register the second service, an information acquisition failure notification is returned to the first registry, the information acquisition failure notification indicating that the micro service management device has not queried for address information for the second service.

In the process of acquiring the address information, a basic fusion mode is adopted, so that the fusion management equipment can call the micro service registered by the micro service management equipment.

In another embodiment, if a basic fusion manner is adopted, in a case that the fusion management device can call a service in the micro service management device, and the micro service management device cannot call the service in the fusion management device, if the second registry of the micro service management device receives an address acquisition request for any micro service, if the micro service management device does not register the micro service, an information acquisition failure notification is returned, and a subsequent call process is not executed.

In another embodiment, if a deep fusion mode is adopted, not only the fusion management device can obtain the micro address information of any service registered in the micro service management device, but also the micro service management device can obtain the address information of any micro service registered in the fusion management device. For example, the service in the converged management device and the service in the micro service management device can be mutually invoked, if the second registry of the micro service management device receives an address acquisition request for any micro service, if the micro service management device does not register the micro service, the micro service management device can send the address acquisition request to the first registry through the second registry, if the first registry registers the service, the converged management device sends address information of the service to the second registry through the first registry.

Alternatively, in the deep fusion manner, the micro service management device can set whether to call a service in the fusion management device.

In another embodiment, if the fusion is managed, only the registration, release and call functions of the micro service are managed to the fusion management device, and at this time, no connection is established between the fusion management device and the micro service management device, so that the service in the fusion management device and the service in the micro service management device cannot be called mutually.

In one possible implementation, during the call, the call of the service may be affected due to the failure of the node device. Therefore, in order to ensure that the second service corresponding to the address information can be successfully invoked, the fusion management device selects the address information from the address information corresponding to the available device nodes, that is, the fusion management device determines at least one available node device of the second service through the first registry, and determines the address information corresponding to any available node device through the first registry.

In one possible implementation, the fusion management device determines, through the first registry, at least one available node device corresponding to at least one device identifier in the set of available nodes of the second service. Wherein the set of available nodes includes at least a device identification of at least one available node device.

Optionally, the available node set further includes address information corresponding to each device identifier, and the fusion management device selects one device identifier from at least one device identifier, where the address information corresponding to the device identifier is the address information of the selected second service. Or, in another address information set, address information corresponding to a plurality of device identifiers is included, and after at least one available node device is determined, address information corresponding to the device identifier of any available node device is selected from the address information set.

Wherein the available node device refers to the node device which can be called by the issued second service.

In order to determine available node equipment of the second service, detecting a plurality of node equipment of the second service is needed, and determining whether the node equipment is available according to a detection result to obtain the available node equipment of the second service so as to ensure that the second service corresponding to the acquired address information is a callable service.

In one possible implementation, after the converged management device issues the second service to the plurality of node devices, the plurality of node devices are periodically detected to determine a state of the node devices, and the corresponding at least one available node device is determined according to at least one device identifier in the available node set of the second service through the first registry.

In another possible implementation manner, after receiving the address acquisition request for the second service, detecting a plurality of node devices of the second service to determine a state of the node devices, and determining, by the first registry, at least one available node device according to at least one device identifier in the available node set of the second service.

For the two detection modes, the detection timings of the two detection modes are different, but the detection process of the node device is the same.

The fusion management equipment sends detection requests to a plurality of node equipment which has issued the second service, receives detection results returned by each node equipment, and determines at least one available node equipment of the second service according to the received detection results; a device identification of at least one available node device is added to the set of available nodes of the second service. The detection request is used for requesting to detect whether a second service issued on the corresponding node equipment is callable.

And for any node equipment, if the detection result returned by the node equipment is that the request is successful, the node equipment is indicated to be available node equipment, and the node equipment is added to the available node set.

In one possible implementation, the fusion management device determines at least one unavailable node device of the second service according to the plurality of detection results; at least one unavailable node device is added to the unavailable node set of the second service.

And for any node equipment, if the detection result returned by the node equipment is that the request fails, indicating that the node equipment is unavailable node equipment, and adding the node equipment to an unavailable node set.

In one possible implementation manner, the number of node devices in the available node set needs to reach a reference number, and under the condition that the number of node devices in the available node set is smaller than the reference number, acquiring device identifiers meeting the available conditions in the unavailable node set; and moving the node equipment corresponding to the equipment identification meeting the available condition to an available node set.

Since the more times the node device identification is added to the unavailable node set, the more times the node device fails, the node device is easier to fail, if the node device is used, the service call is more likely to be affected, and the fewer times the node device identification is added to the unavailable node set, the fewer times the node device fails, the node device can be used as an available device. In the detection process, the detection failure may be caused by reasons such as network connection, etc., at the time point when the detection request is sent, and for the node device which can recover to be normal after a period of time, the node device may have recovered to be normal after the storage duration exceeds the reference duration, so that the node device can be used as an available device. Therefore, the availability condition is that the historical times of adding the equipment identifier to the unavailable node set do not exceed the reference times, and the preservation time of the equipment identifier in the unavailable node set after the detection exceeds the reference time.

Optionally, after each addition of the device identifier to the unavailable node set, 1 is added to the number of times the node device is added to record the number of times the device identifier is added to the unavailable node set.

Wherein the reference number is any preset value, for example, the reference number is 2, 3 or other times; the preservation duration refers to the duration of the interval between the time point when the equipment identifier is added to the unavailable node set and the current time point in the detection; the reference time length is any preset time length or is set according to the called time length of the service. For example, the service is invoked once every 10 seconds on average, and the reference duration may be 10 seconds or a multiple of 10 seconds.

In addition, in one possible implementation manner, before the detection, the fusion management device can issue a detection configuration interface to the terminal, the terminal displays the detection configuration interface, and the user can input information such as a detection period, a detection address, a health code and the like in the detection configuration interface. The detection address refers to address information corresponding to the node equipment to be detected, the health code refers to information returned by the node equipment, if the detection result returned by the node equipment is the health code, the node equipment is indicated to be available, and if the detection result returned by the node equipment is not the health code, the node equipment is indicated to be unavailable. The health code is a default health code in the detection configuration interface or a health code input by a user.

703. And receiving the address information through the first service, and initiating a call request carrying the address information.

After receiving the returned address information, the first service initiates a call request to a second service corresponding to the address information so as to call the second service corresponding to the address information.

In one possible implementation, after the first service sends a call request to the second service, the second service receives the call request, and if the second service can be called by the first service, the second service returns a corresponding port to the first service, so that the first service makes a call to the second service through the port.

In one possible implementation manner, the converged management device further includes an interface gateway, when the first service calls the second service, verification needs to be performed through the interface gateway, and when verification passes, the first service is indicated to have authority to call the second service, and at this time, the second service can be called. Wherein the interface gateway is an API gateway.

The fusion management equipment receives the address information through the first service, and sends a call request to the interface gateway, wherein the call request also carries verification information; and verifying the verification information through the interface gateway, and sending a call request to the second service corresponding to the address information under the condition that the verification is passed. The verification information is used for verifying the call request.

Optionally, the verification information is encrypted information, the interface gateway decrypts after receiving the encrypted information, and if the decrypted information is accurate information, the verification is passed.

For example, referring to fig. 6, a service caller 601 sends a call request to an interface gateway 605.

In addition, if the first service and the second service are the same type of service, the calling mode is similar to the above process when the first service and the second service are both micro services, and when the first service and the second service are both combined services, the micro service management equipment is not involved in the calling process.

For example, referring to the schematic diagram shown in fig. 8, the flow indicated by the dashed line is the flow of the call in the related art, and the flow indicated by the solid line is the flow of the call in the embodiment of the present application. In the related art, a service caller (first service) 801 sends an address acquisition request to a service list 802 including an IP address of a called service, and sends the IP address to the service caller 801, and the service caller 801 calls a service provider (second service) 803 through the IP address to implement service call. In the embodiment of the present application, a service caller (first service) 801 sends an address acquisition request to a first registry 804, the first registry 804 includes a domain name address of a called service, the domain name is sent to the service caller 801, the service caller 801 sends a call request to an interface gateway 805, and after the interface gateway 805 verifies, the service call is implemented through a domain name call service provider (second service) 803.

It should be noted that, in the embodiment of the present application, only one micro-service management device is taken as an example for explanation, in another embodiment, a plurality of micro-service management devices can be included, different micro-service running environments are configured in different micro-service management devices, and the converged management device can interact with any micro-service management device. The micro-services registered in any micro-service management device can be synchronized to the fusion management device, and the micro-services registered in the fusion management device can be synchronized to any micro-service management device.

The method provided by the embodiment of the application configures the fusion operation environment in the fusion management equipment, and can operate the micro service and the combined service in the fusion operation environment, thereby managing the two types of services and realizing unified management of different types of services. In addition, the different types of services running in the running environment can be mutually called, so that the problem that the different types of services cannot be mutually called is avoided, functions are expanded, and flexibility is improved.

Fig. 9 is a flowchart of a set management method according to an embodiment of the present application. The embodiment of the application is applied to fusion management equipment, and referring to fig. 9, the method comprises the following steps:

901. A plurality of node devices for a published service are acquired.

902. A detection request is sent to a plurality of node devices, the detection request requesting detection of whether a service published on the node device is callable.

903. For any node device, judging whether the returned detection result is successful request, if the request is successful, adding the node device to an available node set, if the request fails, and the returned failure information is preset failure information, adding the node device to an unavailable node list, and if the returned failure information is not preset failure information, adding the node device to the available node set.

904. Judging whether the number of the node devices in the available node sets reaches the reference number, if so, not selecting the node devices from the unavailable node sets, if not, traversing each node device in the unavailable node sets, selecting the available node devices from the unavailable node sets, and adding the available node devices into the available node sets.

905. Judging whether the preservation time of the equipment identifier in the unavailable node set after the detection exceeds the reference time, if so, deleting the equipment identifier from the unavailable node set, judging whether the historical times of adding the equipment identifier into the unavailable node set does not exceed the reference times, and if so, adding the equipment identifier of the node equipment into the available node set.

By adopting the method, the health detection is carried out on the node equipment so as to ensure that the available node set can be selected, and the service is subsequently invoked according to the address information corresponding to the node equipment in the available node set.

Fig. 10 shows a block diagram of a terminal 1000 according to an exemplary embodiment of the present application. The terminal 1000 can be a portable mobile terminal such as: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion picture expert compression standard audio plane 3), an MP4 (Moving Picture Experts Group Audio Layer IV, motion picture expert compression standard audio plane 4) player, a notebook computer, or a desktop computer. Terminal 1000 can also be referred to by other names of user equipment, portable terminal, laptop terminal, desktop terminal, etc.

In general, terminal 1000 can include: a processor 1001 and a memory 1002.

The processor 1001 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 1001 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 1001 may also include a main processor, which is a processor for processing data in an awake state, also referred to as a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 1001 may be integrated with a GPU (Graphics Processing Unit, image processor) for taking care of rendering and drawing of content that the display screen needs to display. In some embodiments, the processor 1001 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.

Memory 1002 may include one or more computer-readable storage media, which may be non-transitory. Memory 1002 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 1002 is used to store at least one instruction for execution by processor 1001 to implement the service invocation method provided by the method embodiment of the present application.

In some embodiments, terminal 1000 can optionally further include: a peripheral interface 1003, and at least one peripheral. The processor 1001, the memory 1002, and the peripheral interface 1003 may be connected by a bus or signal line. The various peripheral devices may be connected to the peripheral device interface 1003 via a bus, signal wire, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 1004, a display 1005, a camera assembly 1006, audio circuitry 1007, and a power supply 1009.

Peripheral interface 1003 may be used to connect I/O (Input/Output) related at least one peripheral to processor 1001 and memory 1002. In some embodiments, processor 1001, memory 1002, and peripheral interface 1003 are integrated on the same chip or circuit board; in some other embodiments, either or both of the processor 1001, memory 1002, and peripheral interface 1003 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

Radio Frequency circuit 1004 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. Radio frequency circuitry 1004 communicates with a communication network and other communication devices via electromagnetic signals. The radio frequency circuit 1004 converts an electrical signal into an electromagnetic signal for transmission, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1004 includes: antenna systems, RF transceivers, one or more amplifiers, tuners, oscillators, digital signal processors, codec chipsets, subscriber identity module cards, and so forth. Radio frequency circuitry 1004 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the world wide web, metropolitan area networks, intranets, generation mobile communication networks (2G, 3G, 4G, and 5G), wireless local area networks, and/or WiFi (Wireless Fidelity ) networks. In some embodiments, the radio frequency circuitry 1004 may also include NFC (Near Field Communication ) related circuitry, which is not limiting of the application.

The display screen 1005 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display 1005 is a touch screen, the display 1005 also has the ability to capture touch signals at or above the surface of the display 1005. The touch signal may be input to the processor 1001 as a control signal for processing. At this time, the display 1005 may also be used to provide virtual buttons and/or virtual keyboards, also referred to as soft buttons and/or soft keyboards. In some embodiments, display 1005 may be one, disposed on the front panel of terminal 1000; in other embodiments, display 1005 may be provided in at least two, separately provided on different surfaces of terminal 1000 or in a folded configuration; in other embodiments, display 1005 may be a flexible display disposed on a curved surface or a folded surface of terminal 1000. Even more, the display 1005 may be arranged in a non-rectangular irregular pattern, i.e., a shaped screen. The display 1005 may be made of LCD (Liquid Crystal Display ), OLED (Organic Light-Emitting Diode) or other materials.

The camera assembly 1006 is used to capture images or video. Optionally, camera assembly 1006 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal and the rear camera is disposed on the rear surface of the terminal. In some embodiments, the at least two rear cameras are any one of a main camera, a depth camera, a wide-angle camera and a tele camera, so as to realize that the main camera and the depth camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize a panoramic shooting and Virtual Reality (VR) shooting function or other fusion shooting functions. In some embodiments, camera assembly 1006 may also include a flash. The flash lamp can be a single-color temperature flash lamp or a double-color temperature flash lamp. The dual-color temperature flash lamp refers to a combination of a warm light flash lamp and a cold light flash lamp, and can be used for light compensation under different color temperatures.

The audio circuit 1007 may include a microphone and a speaker. The microphone is used for collecting sound waves of users and environments, converting the sound waves into electric signals, and inputting the electric signals to the processor 1001 for processing, or inputting the electric signals to the radio frequency circuit 1004 for voice communication. For purposes of stereo acquisition or noise reduction, the microphone may be multiple, each located at a different portion of terminal 1000. The microphone may also be an array microphone or an omni-directional pickup microphone. The speaker is used to convert electrical signals from the processor 1001 or the radio frequency circuit 1004 into sound waves. The speaker may be a conventional thin film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, not only the electric signal can be converted into a sound wave audible to humans, but also the electric signal can be converted into a sound wave inaudible to humans for ranging and other purposes. In some embodiments, audio circuit 1007 may also include a headphone jack.

Power supply 1009 is used to power the various components in terminal 1000. The power source 1009 may be alternating current, direct current, disposable battery or rechargeable battery. When the power source 1009 includes a rechargeable battery, the rechargeable battery may be a wired rechargeable battery or a wireless rechargeable battery. The wired rechargeable battery is a battery charged through a wired line, and the wireless rechargeable battery is a battery charged through a wireless coil. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 1000 can further include one or more sensors 1010. The one or more sensors 1010 include, but are not limited to: acceleration sensor 1011, gyro sensor 1012, pressure sensor 1013, optical sensor 1015, and proximity sensor 1016.

The acceleration sensor 1011 can detect the magnitudes of accelerations on three coordinate axes of the coordinate system established with the terminal 1000. For example, the acceleration sensor 1011 may be used to detect components of gravitational acceleration in three coordinate axes. The processor 1001 may control the display screen 1005 to display a user interface in a landscape view or a portrait view according to the gravitational acceleration signal acquired by the acceleration sensor 1011. The acceleration sensor 1011 may also be used for the acquisition of motion data of a game or a user.

The gyro sensor 1012 may detect the body direction and the rotation angle of the terminal 1000, and the gyro sensor 1012 may collect the 3D motion of the user to the terminal 1000 in cooperation with the acceleration sensor 1011. The processor 1001 may implement the following functions according to the data collected by the gyro sensor 1012: motion sensing (e.g., changing UI according to a tilting operation by a user), image stabilization at shooting, game control, and inertial navigation.

Pressure sensor 1013 may be disposed on a side frame of terminal 1000 and/or on an underlying layer of display 1005. When the pressure sensor 1013 is provided at a side frame of the terminal 1000, a grip signal of the terminal 1000 by a user can be detected, and the processor 1001 performs right-and-left hand recognition or quick operation according to the grip signal collected by the pressure sensor 1013. When the pressure sensor 1013 is provided at the lower layer of the display screen 1005, the processor 1001 controls the operability control on the UI interface according to the pressure operation of the user on the display screen 1005. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

The optical sensor 1015 is used to collect ambient light intensity. In one embodiment, the processor 1001 may control the display brightness of the display screen 1005 based on the ambient light intensity collected by the optical sensor 1015. Specifically, when the intensity of the ambient light is high, the display brightness of the display screen 1005 is turned up; when the ambient light intensity is low, the display brightness of the display screen 1005 is turned down. In another embodiment, the processor 1001 may dynamically adjust the shooting parameters of the camera module 1006 according to the ambient light intensity collected by the optical sensor 1015.

Proximity sensor 1016, also referred to as a distance sensor, is typically located on the front panel of terminal 1000. Proximity sensor 1016 is used to collect the distance between the user and the front of terminal 1000. In one embodiment, when proximity sensor 1016 detects a gradual decrease in the distance between the user and the front face of terminal 1000, processor 1001 controls display 1005 to switch from the bright screen state to the off screen state; when proximity sensor 1016 detects a gradual increase in the distance between the user and the front of terminal 1000, processor 1001 controls display 1005 to switch from the off-screen state to the on-screen state.

Those skilled in the art will appreciate that the structure shown in fig. 10 is not limiting and that terminal 1000 can include more or fewer components than shown, or certain components can be combined, or a different arrangement of components can be employed.

Fig. 11 is a schematic structural diagram of a server according to an embodiment of the present application, where the server 1100 may have a relatively large difference due to configuration or performance, and may include one or more processors (Central Processing Units, CPU) 1101 and one or more memories 1102, where the memories 1102 store at least one instruction, and the at least one instruction is loaded and executed by the processor 1101 to implement the methods provided in the above-mentioned method embodiments. Of course, the server may also have a wired or wireless network interface, a keyboard, an input/output interface, and other components for implementing the functions of the device, which are not described herein.

The server 1100 may be used to perform the steps performed by the server in the service invocation method described above.

The embodiment of the application also provides computer equipment, which comprises a processor and a memory, wherein at least one instruction is stored in the memory, and the at least one instruction is loaded and executed by the processor so as to realize the service calling method of the embodiment.

The embodiment of the application also provides a computer readable storage medium, wherein at least one instruction is stored in the computer readable storage medium, and the at least one instruction is loaded and executed by a processor to realize the service calling method of the embodiment.

The present application also provides a computer program product or a computer program, which comprises computer instructions stored in a computer-readable storage medium, from which computer instructions are read by a processor of a computer device, the computer instructions being executed by the processor, so that the computer device performs the service invocation method of the above embodiments.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the above storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The foregoing is merely an alternative embodiment of the present application and is not intended to limit the embodiment of the present application, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the embodiment of the present application should be included in the protection scope of the present application.

Claims

1. The fusion management equipment is characterized by being configured with a fusion operation environment, wherein the fusion operation environment is used for operating combined service and micro service, the fusion management equipment further comprises a first registry, the combined service is a service formed by combining a plurality of functions, and the combined service is used for realizing at least two functions;

the first registry is configured to receive an address acquisition request of a first service to a second service, where the first service and the second service are different types of services, and the first service and the second service are any one of the combined service or the micro service;

2. The fusion management device of claim 1, wherein the fusion management device further comprises an interface gateway;

the first service is configured to send the call request to the interface gateway, where the call request further carries verification information;

the interface gateway is used for verifying the verification information;

the interface gateway is further configured to send the call request to the second service corresponding to the address information if the verification is passed.

3. The fusion management device of claim 1, wherein the fusion management device is configured to,

the first registry is configured to determine at least one available node device of the second service, where the available node device is a node device that can be invoked by the published second service;

the first registry is configured to determine address information corresponding to any available node device, where the address information is obtained by distributing the second service to the available node device.

4. The fusion management device of claim 3, wherein,

the first registry is configured to determine, according to at least one device identifier in the available node set of the second service, a corresponding at least one available node device.

5. The fusion management device of claim 4, wherein the fusion management module,

the fusion management device is configured to send a detection request to a plurality of node devices that have issued the second service, where the detection request is used to request to detect whether the second service issued on the corresponding node device is callable;

the fusion management device is further configured to receive a detection result returned by each node device, and determine at least one available node device of the second service according to the received multiple detection results;

the converged management device is further configured to add a device identification of the at least one available node device to the set of available nodes of the second service.

6. The fusion management device of claim 5, wherein the fusion management module,

the fusion management device is further configured to determine at least one unavailable node device of the second service according to the multiple detection results;

the converged management device is further configured to add the at least one unavailable node device to the set of unavailable nodes of the second service.

7. The fusion management device of claim 6, wherein the fusion management module,

the fusion management device is further configured to obtain, when the number of node devices in the available node set is less than the reference number, a device identifier that meets an available condition in the unavailable node set, where the available condition is that the number of times the device identifier is added to the unavailable node set does not exceed the reference number of times, and a save time of the device identifier in the unavailable node set after the current detection exceeds a reference time;

The fusion management device is further configured to move node devices corresponding to the device identifiers that meet the availability condition to the available node set.

8. The fusion management device of claim 1, wherein the second service is a micro service;

the first registry is further configured to send the address acquisition request to a second registry and receive address information of the second service returned by the second registry, where the second service is not registered;

9. The fusion management device of claim 1, wherein the fusion management device is configured to,

the first registry is further configured to receive a registration request of any service, where the registration request carries registration information of the service;

the first registration center is further configured to register the service according to the registration information, where the service is a micro service or a combined service.

10. The fusion management device of claim 9, wherein the fusion management module,

The fusion management device is further configured to issue the service to a plurality of node devices, and allocate corresponding address information to the service issued on each node device, where the address information corresponding to the service issued on different node devices is different.

11. The fusion management device of claim 9, wherein the service is a micro-service;

the first registry is further configured to send a synchronous registration request to a second registry, where the synchronous registration request carries the registration information, so that the second registry registers the service according to the registration information;

12. The fusion management device of claim 9, wherein the fusion management module,

the first registry is further configured to receive a synchronous registration request sent by the second registry, where the synchronous registration request carries registration information of any service to be registered;

the first registration center is further configured to register the service according to the registration information;

13. A management system, characterized in that it comprises a fusion management device according to any one of claims 1-12 and a micro-service management device;

14. The service calling method is characterized by being applied to fusion management equipment, wherein the fusion management equipment is configured with a fusion operation environment, the fusion operation environment is used for operating combined service and micro service, the fusion management equipment further comprises a first registry, the combined service is a service formed by combining a plurality of functions, and the combined service is used for realizing at least two functions; the method comprises the following steps:

receiving an address acquisition request of a first service to a second service through the first registration center, wherein the first service and the second service are different types of services, and the first service and the second service are any one of the combined service or the micro service;

15. The method of claim 14, wherein the converged management device further comprises an interface gateway, wherein the receiving the address information via the first service, initiating a call request carrying the address information, comprises:

16. The method of claim 14, wherein the obtaining, by the first registry, address information for the second service comprises:

17. The method of claim 16, wherein the determining, by the first registry, at least one available node device for the second service comprises:

18. The method of claim 14, wherein prior to the obtaining, by the first registry, address information for the second service, the method further comprises:

19. The method of claim 18, wherein after receiving the detection result returned by each node device, the method further comprises:

20. The method of claim 19, wherein after the adding the at least one unavailable node device to the set of unavailable nodes of the second service, the method further comprises:

21. The method of claim 14, wherein the second service is a micro service, and wherein receiving, by the first registry, an address acquisition request for the second service from the first service comprises:

22. The method of claim 14, wherein the method further comprises:

23. The method of claim 22, wherein after the registering the service by the first registry based on the registration information, the method further comprises:

24. The method of claim 22, wherein the service is a micro-service, and wherein after receiving a registration request for any service through the first registry, the method further comprises:

25. The method of claim 14, wherein the method further comprises:

26. The method of claim 22, wherein prior to receiving a registration request for any service by the first registry, the method further comprises:

27. A computer-readable storage medium having stored therein at least one instruction that is loaded and executed by a processor to implement operations performed in a service invocation method as recited in any one of claims 14-26.