WO2021129008A1

WO2021129008A1 - Service invocation method, apparatus and device, and medium

Info

Publication number: WO2021129008A1
Application number: PCT/CN2020/117676
Authority: WO
Inventors: 水淼; 杨斌; 高永露; 雷平; 陈斌
Original assignee: 中国银联股份有限公司
Priority date: 2019-12-23
Filing date: 2020-09-25
Publication date: 2021-07-01
Also published as: CN111147567A

Abstract

Disclosed are a service invocation method, apparatus and device, and a medium. The service invocation method comprises: in the case that a disaster occurs in a main data center, stopping invoking a target service by means of the main data center, wherein the target service has multiple data centers that can be invoked, said multiple data centers are determined according to the service providing device information corresponding to the target service, the data center with the highest priority among said multiple data centers is the main data center, the other data centers are disaster recovery data centers, and the priorities of said multiple data centers are determined according to the preset priorities of the data centers of the target service; according to the priorities of the data centers, determining a first data center with the highest priority among the disaster recovery data centers; and sending a service invocation request to the first data center to invoke the target service. According to embodiments of the present application, the reliability of a target service can be improved, and the data loss of the target service can be avoided.

Description

Service invocation method, device, equipment and medium

Cross references to related applications

This application claims the priority of the Chinese patent application 201911339742.6 entitled "Service Invocation Method, Apparatus, Equipment, and Medium" filed on December 23, 2019, and the entire content of this application is incorporated herein by reference.

Technical field

This application relates to the field of communication technology, and in particular to a method, device, device, and medium for invoking a service.

Background technique

The distributed service invocation system in the related technology generally includes a registration center and multiple service providing devices, and each service providing device will register its device address on the registration center. The service invoking device can obtain the device address that supports the business service that needs to be invoked from the registration center, and according to the obtained device address, invoke the business service through the service providing device corresponding to the device address.

Since the distributed service invocation system in the related technology does not have disaster tolerance characteristics, in the event of a disaster in the service providing device called by the service invocation device, it may cause the suspension of the business service, reduce the reliability of the business service, and may also cause The data of the business service is lost.

Summary of the invention

The embodiments of the present application provide a service invocation method, device, equipment, and medium, which can improve the reliability of a target service and avoid data loss of the target service.

In the first aspect, an embodiment of the present application provides a method for invoking a service, and the method includes:

In the case of a disaster in the main data center, stop calling the target service through the main data center; the target service has multiple callable data centers, and the multiple callable data centers are determined according to the service providing equipment information corresponding to the target service. The data center with the highest priority among the data centers that can be called is the main data center, and the data centers other than the main data center among the data centers that can be called are the disaster recovery data centers. The priority of the multiple data centers is preset according to the preset The data center priority of the target service is determined;

According to the priority of the data center, determine the first data center with the highest priority among the disaster recovery data centers;

Send a service call request to the first data center to call the target service.

In the second aspect, an embodiment of the present application provides a method for invoking a service, and the method includes:

Obtain the first interactive operation data;

In response to the first interactive operation data, determine the changed operating state of the third data center and the changed operating state of the third data center;

According to the third data center and the operating state after the change, generate state change instructions;

Send a state change instruction to the registry, so that the registry sends a state change notification corresponding to the state change instruction to the service invoking device that invokes the target service through the third data center.

In the third aspect, an embodiment of the present application provides a service invoking device, which includes:

The first call control module is used to stop calling the target service through the main data center in the event of a disaster in the main data center; the target service has multiple callable data centers, and the multiple callable data centers correspond to the target service The service provision equipment information is determined, the data center with the highest priority among the multiple callable data centers is the main data center, and the other data centers of the multiple callable data centers except the main data center are the disaster recovery data centers, and multiple callable data centers are disaster recovery data centers. The priority of the data center is determined according to the preset data center priority of the target service;

The data center reselection module is used to determine the first data center with the highest priority among the disaster recovery data centers according to the priority of the data center;

The second call control module is used to send a service call request to the first data center to call the target service.

In a fourth aspect, an embodiment of the present application provides a service invoking device, which includes:

The first data acquisition module is used to acquire the first interactive operation data;

The first data processing module is configured to determine the changed operating state of the third data center and the changed operating state of the third data center in response to the first interactive operation data;

The first instruction generation module is used to generate a state change instruction according to the third data center and the operating state after the change;

The first instruction sending module is configured to send a state change instruction to the registry, so that the registry sends a state change notification corresponding to the state change instruction to the service invoking device that invokes the target service through the third data center.

In a fifth aspect, an embodiment of the present application provides a service invoking device, including: a processor and a memory storing computer program instructions;

The processor implements the service invoking method as described in the first aspect or the second aspect when the processor executes the computer program instructions.

In a sixth aspect, an embodiment of the present application provides a computer storage medium with computer program instructions stored on the computer storage medium, and when the computer program instructions are executed by a processor, the service invoking method as described in the first or second aspect is implemented.

In the embodiment of the present application, the target service has multiple callable data centers determined according to the service providing device information corresponding to the target service, and the priority of the multiple callable data centers is determined according to the preset data center priority of the target service. The highest data center is used as the main data center, and other data centers are used as the disaster recovery data center, so that the disaster recovery form can be formed through the main data center and the disaster recovery data center. Therefore, in the event of a disaster in the main data center, the The first data center with the highest priority in the disaster recovery data center calls the target service to quickly complete the disaster recovery switch to the target service, which can ensure the reliability of the target business and avoid data loss of the target business.

Description of the drawings

The features, advantages, and technical effects of the exemplary embodiments of the present application will be described below with reference to the accompanying drawings.

Figure 1 is a system architecture diagram of an example of a distributed service invocation system in related technologies;

Figure 2 is a system architecture diagram of an exemplary distributed service invocation system;

FIG. 3 is a schematic flowchart of an embodiment of the service invocation method of the present application;

FIG. 4 is a schematic flowchart of another embodiment of the service invocation method of the present application;

Fig. 5 is a diagram of a working state control interface according to an embodiment of the present application;

Fig. 6 is a schematic structural diagram of an embodiment of the service invoking device of the present application;

FIG. 7 is a schematic structural diagram of another embodiment of the service invoking apparatus of the present application;

Fig. 8 is a schematic structural diagram of an embodiment of the service invoking device of the present application.

Detailed ways

The implementation of the present application will be described in further detail below in conjunction with the accompanying drawings and embodiments. The detailed description and drawings of the following embodiments are used to exemplarily illustrate the principle of the present application, but cannot be used to limit the scope of the present application, that is, the present application is not limited to the described embodiments.

In the description of this application, it should be noted that relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities Or there is any such actual relationship or sequence between operations. Moreover, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes those that are not explicitly listed Other elements of, or also include elements inherent to this process, method, article or equipment. If there are no more restrictions, the element defined by the sentence "including..." does not exclude the existence of other same elements in the process, method, article or equipment that includes the element.

Fig. 1 is a system architecture diagram of an example of a distributed service invocation system in related technologies. As shown in Figure 1, the distributed service invocation system includes a registration center 101 and multiple service devices connected in communication with the registration center 101. The service device can be a server, and each service device is registered in the registration center 101. There is the device identification of the service device, the supported business service and the device address. When a service device receives a service invocation instruction for a business service, the service device becomes the service invocation device 102, and other service devices that support the business service become the service providing device 103.

In the distributed service invoking system shown in FIG. 1, the service invoking device 102 can send a subscription service request to the registration center 101, and the registration center 101 queries the service providing devices of all the service providing devices 103 that support the business service based on the subscription service request. After receiving the service providing device information, the service invoking device 102 selects one of the service providing devices 103 that support the business service to invoke the business service.

In the case of using the distributed service invocation system shown in Figure 1 to construct a disaster recovery system, two sets of distributed service invocation systems need to be set up, which not only makes the overall system cost higher, but also makes disaster recovery management more difficult. The speed of service disaster recovery switching is slow, which reduces the reliability of business services and may also cause data loss of business services.

In order to solve the problems of the prior art, the embodiments of the present application provide a service invocation method, device, equipment, and medium for a distributed service invocation system.

Figure 2 is a system architecture diagram of an exemplary distributed service invocation system. As shown in Figure 2, the distributed service invoking system includes a registration center 201 and a plurality of service devices connected in communication with the registration center 201. The service device may be a server, and the server may be a high-performance electronic calculator. , Used to store and process data. Each service device is registered in the registration center 201 with its device identification, supported business services and device addresses. When a service device receives a service invocation instruction for a business service, the service device becomes the service invocation device 202, and other service devices that support the business service become the service providing device 203.

Continuing to refer to FIG. 2, the distributed service calling system includes multiple data centers. Among them, the data center including the service providing device 203 is the callable data center 204, and the multiple service providing devices 203 are located in different callable data centers 204 respectively. The number of service providing devices 203 in different callable data centers 204 may be the same or different. Each service providing device 203 can support one business service or multiple business services.

Since multiple service providing devices 203 are located in different callable data centers 204, each service device also needs to register the data center identifier of the data center to which the service device belongs in the registration center 201.

In the distributed service invoking system shown in FIG. 2, the service invoking device 202 can send a subscription service request to the registration center 201, and the registration center 201 queries the service providing devices of all service providing devices 203 that support the business service based on the subscription service request. After receiving the service providing device information, the service invoking device 202 selects a callable business service from the callable data centers 204 that support the business service, and when a disaster occurs in the callable data center 204 that is used to call the business service, Select one of the other callable data centers 204 to call the business service, so as to implement the disaster recovery switching of the service call.

Continuing to refer to Figure 2, the distributed service invocation system also includes a service control device 205, which can communicate with the registration center 201 to control the operation of each data center.

Hereinafter, with reference to the distributed service invoking system shown in FIG. 2, the service invoking method provided by the embodiment of the present application will be described in detail.

Fig. 3 is a schematic flowchart of an embodiment of the service invocation method of the present application. Wherein, the service invoking method shown in FIG. 3 can be applied to the service invoking device 202 in FIG. 2. As shown in Figure 3, the service invocation method may include:

S310. In the case of a disaster in the main data center, stop calling the target service through the main data center; where the target service has multiple callable data centers, and the multiple callable data centers are determined according to the service providing equipment information corresponding to the target service. The data center with the highest priority among the multiple callable data centers is the main data center, and the data centers other than the main data center among the multiple callable data centers are disaster recovery data centers. The priority of the multiple callable data centers is based on The data center priority of the preset target service is determined;

S320: According to the priority of the data center, determine the first data center with the highest priority among the disaster recovery data centers;

S330. Send a service invocation request to the first data center to invoke the target service.

In the embodiment of the present application, specifically, the callable data center is a data center that has service provision equipment that supports the target service and is determined according to the service provision equipment information corresponding to the target service. The service providing device may be the service providing device 203 in FIG. 2.

In some embodiments of the present application, the service providing device information can be obtained from the registration center 201 in FIG. 2.

Optionally, before S310, the service invoking method may further include:

Send a subscription request for subscribing to the target service to the registry;

Receive service provision device information fed back by the registration center.

Specifically, after the service invocation device receives the service invocation instruction for the target service, it may respond to the service invocation instruction and send a subscription request to the registry to subscribe to the target service. After receiving the subscription request, the registry may register in the registered center. Among the service devices, according to the supported business services registered by each service device, determine the service providing device that supports the target service, and feedback the service providing device information corresponding to the service providing device to the service invoking device, so that the service invoking device can obtain The service provides device information.

In some embodiments of the present application, the service providing device information may include multiple service providing devices supporting the target business and the device information of each service providing device. The device information includes the data center identifier of the data center to which it belongs, so as to provide the device information according to the service. Determine the callable data center corresponding to the target service.

Optionally, after receiving the service providing device information fed back by the registration center and before S310, the service invoking method may further include:

Obtain the data center identifiers corresponding to multiple service providing devices in the service providing device information;

According to the obtained data center identifier, multiple callable data centers are determined.

Therefore, the data center identifier can be used to add the "data center" attribute to each service providing device, so that the service invoking device can provide these services according to the data center identifier of the data center to which each service providing device belongs in the service providing device information Devices are divided into their own data centers. Since these service-providing devices support target services, the data centers to which these service-providing devices belong are callable data centers.

In some embodiments of the present application, before S310, among multiple callable data centers, the main data center may be selected according to the priority of the multiple callable data centers, specifically, the priority of the multiple callable data centers Determined according to the preset data center priority of the target service.

Obtain the data center priority; among them, the data center priority is the priority for multiple data centers, and the multiple data centers include callable data centers;

According to the data center priority, determine the callable data center priority of multiple callable data centers;

According to the callable data center priority, among multiple callable data centers, determine the main data center.

In these embodiments, the distributed service invocation system as shown in Figure 2. The distributed service invocation system may include multiple data centers, because not every data center supports the target business, and not every one supports the target business. The data centers are currently in normal operation. Therefore, the multiple callable data centers determined according to the information of the service providing equipment are not necessarily all data centers that support the target business among the multiple data centers of the distributed service call system. However, because the operating status of the multiple data centers of the distributed service invocation system is dynamic, the data centers that can be invoked each time the target business is invoked may be different. Therefore, the service invocation device needs to be pre-configured with all data supporting the target business. The data center priority of the center. Therefore, after determining multiple callable data centers, you can use the data center priority to determine the callable data center priority, and according to the callable data center priority, select the highest priority data among the multiple callable data centers Center, as the main data center.

In some embodiments of the present application, after the main data center is determined, the service invoking device may send a service invocation request to the main data center to invoke the target service, thereby invoking the target service through the data center with the highest priority among the available data centers. .

In some embodiments of the present application, the specific method of S320 may include:

According to the priority of the callable data center, the first data center is determined in the disaster recovery data center.

Specifically, since the priority of the callable data center has been determined according to the priority of the data center, in the case of a disaster in the main data center, there is no need to re-determine the priority of the disaster recovery data center, as long as the callable data center priority has been determined. For the data center priority, select the data center with the second highest priority as the first data center with the highest priority in the disaster recovery data center.

In some embodiments of the present application, in the case of a disaster in the first data center, the data center with the second highest priority in the disaster recovery data center can also be determined, and a service invocation request can be sent to the data center with the second highest priority. To call the target service. In the case of a disaster in the data center with the second highest priority, and so on, we will not repeat them here.

Therefore, in this embodiment of the application, the service invoking device can use the "data center" attribute of the service providing device to automatically determine the main data center and disaster recovery data among the multiple available data centers according to the preset data center priority. The first data center in the center, so as to realize the automatic switching of disaster recovery.

In other embodiments of the present application, the service providing device information may include multiple service providing devices supporting the target business and the device information of each service providing device, and the device information may include the data center identification of the data center to which it belongs, device operation information, and The device address information is used to use the device information of the service providing device to invoke the target service through at least one service providing device in the data center selected by the service invoking device.

In the following, description is made by taking the data center selected by the service invoking device as the first data center as an example.

Optionally, the specific method of S330 may include:

Determine the first service providing device belonging to the first data center according to the data center identifiers corresponding to the multiple service providing devices in the service providing device information;

Determine the first target service providing device in the first service providing device according to the device operation information corresponding to the multiple service providing devices in the service providing device information and the preset device invocation rules;

Determine the first target device address corresponding to the first target service providing device according to the device address information corresponding to the multiple service providing devices in the service providing device information;

Through the address of the first target device, a service call request is sent to the first target service providing device to call the target service.

Specifically, in the case of a disaster in the primary data center, after the service invoking device determines the first data center in the disaster recovery data center, the data center identifiers corresponding to multiple service providing devices in the service providing device information can be used, Select the first service providing device with the data center identifier corresponding to the first data center, and then determine the device operation information of each first service providing device according to the device operation information corresponding to multiple service providing devices in the service providing device information, And using preset device invocation rules, such as load balancing rules, select the first target service provider device that can perform service invocation from the first service provider device, and select the device corresponding to multiple service provider devices in the service provider device information The address information is used to find the first target device address corresponding to the first target service providing device, so as to use the first target device address to send a service invocation request to the first target service providing device to call the target service.

In some embodiments of the present application, the service invoking device may use the notification sent by the main data center to determine that a disaster occurs in the main data center. In some other embodiments of the present application, the service invoking device may also use the notification sent by the registration center to determine that a disaster occurs in the main data center. In still other embodiments of the present application, the service invoking device may also use notifications sent by the main data center and the registration center to determine that a disaster occurs in the main data center.

In some embodiments of the present application, optionally, before S310, the service invoking method may further include:

Receive notifications of service exceptions;

In response to the service abnormality notification, determine the device operating status of at least one second service providing device supporting the target business in the main data center;

In a case where it is determined that the device operating state of at least one second service providing device is an abnormal operating state, it is determined that a disaster occurs in the main data center.

In some embodiments, the service abnormality notification may be a notification sent by the main data center. Specifically, the service exception notification may be a call request failure notification sent by the second service providing device supporting the target business in the main data center, and the second service providing device supporting the target business in the main data center is determined to feed back the call request failure notification In the case of, it can be determined that the equipment operating status of at least one second service providing equipment is an abnormal operating status, so that it can be determined that a disaster occurs in the primary data center.

In other embodiments, the service exception notification may also be a notification sent by the registration center. Specifically, the service abnormality notification may be a communication failure notification sent by the registration center to the service invoking device when the communication with the second service providing device supporting the target service fails, and the main data center's support target service is determined according to the communication failure notification. When all of the second service providing devices fail to communicate with the registration center, it can be determined that the device operating status of at least one second service providing device is an abnormal operating status, so that it can be determined that a disaster occurs in the main data center.

In some embodiments, the service abnormality notification can also be the notification sent by the main data center and the notification sent by the registration center. Therefore, the above two notifications can be used to comprehensively determine the device operating status of at least one second service providing device. Determine if there is a disaster in the main data center.

In some other embodiments of the present application, optionally, before S310, the service invoking method may further include:

Receive the data center removal notice sent by the registration center;

In response to the data center removal notification, determine the second data center to be removed among the multiple callable data centers;

In the case that the second data center is the main data center, it is determined that a disaster occurs in the main data center.

Specifically, the registration center confirms that the equipment operating status of the service providing equipment supporting the target business in any data center is abnormal, that is, when the service providing equipment supporting the target business in the data center is completely unavailable, the registration center will The service provision equipment that supports the target business in the data center is removed, that is, the data center is removed from the callable data center of the target business, and after removal, the service invocation device that is invoking the target service through the data center is sent to the service invocation device. The data center removal notification with the data center identifier of the data center, after receiving the data center removal notification, the service invoking device determines the second data center to be removed according to the data center identifier in the data center removal notification, And it is judged whether the second data center is the main data center. In the case of determining that the second data center is the main data center, it can be determined that a disaster occurs in the main data center.

In still other embodiments of the present application, optionally, before S310, the service invoking method may further include:

Receive status change notifications sent by the registry;

In response to the status change notification, determine the third data center that changes its operating status;

In the case where the third data center is the main data center and the operation state of the third data center is a stopped operation state after the change, it is determined that a disaster has occurred in the main data center.

Specifically, the registration center may receive the state change instruction from the service control device 205 in FIG. 2, and operate according to the data center identification of the third data center whose operating state is changed in the state change instruction and the changed operation of the third data center. Status, generate status change notifications, and send them to the service invoking device. After receiving the status change notification, the service invoking device determines the changed operating status of the third data center and the changed operating status of the third data center. First, it determines whether the third data center is the main data center, and then determines whether the third data center is When the main data center and the changed operating state of the third data center are out of service, it is determined that the service control device sets the main data center to the "not shut down state", thereby determining that a disaster occurs in the main data center.

Wherein, the specific method for the above-mentioned service control device 205 to generate the status change instruction will be described in detail below, and will not be repeated here.

In the embodiment of the present application, in the event of a disaster in the main data center, there are two modes of warm standby and cold standby. In the warm backup mode, you can directly use the service providing device information obtained from the registration center according to the subscription request to execute S320-330 when the service invoking device starts, so as to perform the disaster recovery switch of the target service in real time. In the cold standby mode, the service invoking device needs to perform the disaster recovery switch of the target service according to the device address of the started cold standby service provider device pushed by the registration center.

In some embodiments, optionally, in the cold standby mode, after S310, the service invoking method may further include:

In the case of receiving the target device address information sent by the registration center, a service call request is sent to the target service providing device corresponding to the target device address information to call the target service.

Among them, the target device address information refers to the device address information of the cold standby service providing device that has been started and completed.

In some embodiments of the present application, the service invoking method may further include:

In the case of receiving the main data center change notification sent by the registration center, among multiple callable data centers, determine the fourth data center indicated by the main data center change notification;

Update the fourth data center to the main data center;

Send a service call request to the fourth data center to call the target service.

Specifically, the registration center may receive the main data center change instruction from the service control device 205 in FIG. 2, and generate the data center identifier of the fourth data center that needs to be changed to the main data center in the main data center change instruction. The main data center change notification is sent to the service calling device. After receiving the main data center change notification, the service invoking device determines the fourth data center indicated by the main data center change notification according to the data center identifier in the main data center change notification, and uses the fourth data center as the new main data center , And send a service call request to the fourth data center to call the target service, thereby completing the manual switch to the main data center.

The specific method for the above-mentioned service control device 205 to generate the main data center change instruction will be described in detail below, and will not be repeated here.

Fig. 4 is a schematic flowchart of another embodiment of the service invocation method of the present application. Wherein, the service invocation method shown in FIG. 4 can be applied to the service control device 205 in FIG. 2. As shown in Figure 4, the service invocation method may include:

S410. Acquire first interactive operation data.

S420. In response to the first interactive operation data, determine the changed operating state of the third data center and the changed operating state of the third data center;

S430. Generate a state change instruction according to the third data center and the operating state after the change;

S440. Send a state change instruction to the registry, so that the registry sends a state change notification corresponding to the state change instruction to the service invoking device that invokes the target service through the third data center.

In the embodiment of the present application, the service control device can be used for manual switching and manual control of some special switching scenarios. For example, the first service providing device in the first data center requires a certain amount of preparation time and cannot switch over in real time, or A new main data center is set up without stopping the operating state of the main data center, so as to realize the unified and integrated management of all registered data centers and service providing equipment in the registration center.

Fig. 5 is a diagram of a working state control interface according to an embodiment of the present application. As shown in FIG. 5, the service control device 205 may be provided with a working state control interface, which is used to interact with the user, obtain the user's interactive operation data, and generate corresponding instructions according to the interactive operation data.

In some embodiments of the present application, S410 may specifically include:

Receiving a user's first input operation on the target state control button on the working state control interface; wherein the working state control interface includes a plurality of data centers registered on the registration center and a plurality of state control buttons corresponding to each data center;

In response to the first input operation, first interactive operation data for the target state control button is acquired.

Refer to Figure 5, the working status control interface diagram shows that there are two callable data centers, namely the Beijing data center and the Shanghai data center. The Beijing data center has 6 service providing equipment, and the Shanghai data center has 2 service providing equipment, Beijing The data center and the Shanghai data center respectively have three status control buttons 510, which are the "set default" control button, the "set enabled" control button and the "set off" control button. Among them, the "set enabled" control button And the "set to close" control button is used to change the running status of the corresponding callable data center. Among them, the "Set to Enabled" control button can set all the service providing equipment in the corresponding callable data center to the normal operating state, so that the callable data center is in the normal operating state; the "Set to Off" control button can set the corresponding All the service providing equipment in the callable data center is set to the out-of-operation state, so that the callable data center is in the out-of-operation state.

Specifically, the first input operation may be a click operation on the target state control button in the "set to enable" control button and the "set to close" control button. When the user clicks the target state control button, the service control device can obtain the target state control button. The first interactive operation data of the target state control button includes the data center and the operating state corresponding to the target state control button. The data center is regarded as the third data center, and the operating state is regarded as the changed operating state.

In some embodiments of the present application, S430 may specifically include generating a state change instruction according to the data center identifier of the third data center and the operating state after the change.

In these embodiments, when any callable data center is set to stop operation, the callable data center is removed from the registry, so that the registry can also send a data center removal notification to the service calling device to make The service calling device switches the data center that calls the target service.

Further, in the case that the above-mentioned callable data center that is set to be in the out of operation state is set to the normal operating state again, the registration center may also send the main data center status notification to the service invoking device to switch the service invoking device back to Call the target service through the callable data center.

Therefore, the manual switching method provided by the embodiment of the present application can meet part of the disaster recovery switching requirements, has very strong adaptability, and meets the needs of most service disaster recovery switching.

In some other embodiments of the present application, the service invoking method may further include:

Receiving a user's second input operation on the state control button on the working state control interface;

In response to the second input operation, acquiring second interactive operation data for the state control button;

According to the second interactive operation data, determine the fourth data center to be changed to the main data center;

According to the data center identification of the fourth data center, generate the main data center change instruction;

Send the main data center change instruction to the registration center, so that the registration center sends the main data center change notification corresponding to the data center change instruction to the service invoking device.

Continuing to refer to Figure 5, the second input operation is a click operation for the "set as default" control button. When the user clicks any "set as default" control button, the corresponding "set as default" control button can be determined The data center is used as the new main data center, that is, the data center corresponding to the "set as default" control button is used as the fourth data center to be changed, and the main data center change instruction is generated according to the data center identifier of the fourth data center.

In summary, the service invoking method provided by the embodiments of the present application can be applied to a distributed service invoking system, and its switching mode is flexible, adaptable, and versatile, and can meet individualized and constantly changing needs. At the same time, the complexity of the distributed service invocation system is low, which greatly improves the development efficiency of the distributed service invocation system and the ability to respond to changes in disaster recovery requirements.

Fig. 6 is a schematic structural diagram of an embodiment of the service invoking apparatus of the present application. Wherein, the service invoking apparatus shown in FIG. 6 can be applied to the service invoking device 202 in FIG. 2. As shown in FIG. 6, the service invoking apparatus 600 may include:

The first call control module 610 is used to stop calling the target service through the main data center in the event of a disaster in the main data center; wherein the target service has multiple callable data centers, and the multiple callable data centers correspond to the target service The service provision equipment information of the multiple callable data centers is determined, the data center with the highest priority among the multiple callable data centers is the main data center, and the data centers other than the main data center among the multiple callable data centers are the disaster recovery data centers. The priority of a callable data center is determined according to the preset data center priority of the target service;

The data center reselection module 620 is configured to determine the first data center with the highest priority among the disaster recovery data centers according to the priority of the data center;

The second call control module 630 is configured to send a service call request to the first data center to call the target service.

In the embodiment of the present application, specifically, the callable data center is a data center with service providing equipment that supports the target service, which is determined according to the service providing equipment information corresponding to the target service. The service providing device may be the service providing device 203 in FIG. 2.

Optionally, the service invoking apparatus 600 may further include:

The subscription request sending module is used to send a subscription request for subscribing to the target service to the registration center;

The device information receiving module is used to receive service providing device information fed back by the registration center.

In some embodiments of the present application, the service-providing device information includes multiple service-providing devices supporting the target business and the device information of each service-providing device, and the device information includes the data center identifier of the data center to which it belongs, so as to determine according to the service-providing device information The callable data center corresponding to the target service.

In some embodiments of the present application, the service invoking apparatus 600 may further include:

A center identification acquiring module, configured to acquire multiple data center identifications corresponding to the service providing equipment in the service providing equipment information;

The callable center determination module is used to determine multiple callable data centers according to the obtained data center identification.

The priority obtaining module is used to obtain the priority of the data center; among them, the priority of the data center is the priority for multiple data centers, and the multiple data centers include callable data centers;

The priority determination module is used to determine the callable data center priority of multiple callable data centers according to the data center priority;

The main center determination module is used to determine the main data center among multiple callable data centers according to the priority of the callable data center.

The third call control module is used to send a service call request to the main data center to call the target service.

In some embodiments of the present application, the data center reselection module 620 may be specifically used for:

In some embodiments of the present application, the second call control module 630 may be specifically used to:

The first notification receiving module is used to receive service exception notifications;

The first notification processing module is configured to determine the device operating status of at least one second service providing device supporting the target service in the main data center in response to the service abnormality notification;

The first disaster determination module is configured to determine that a disaster occurs in the main data center when it is determined that the equipment operating state of at least one second service providing equipment is an abnormal operating state.

Optionally, the service exception notification is a notification sent by the main data center and/or a notification sent by the registration center.

In some other embodiments of the present application, the service invoking apparatus 600 may further include:

The second notification receiving module is used to receive the data center removal notification sent by the registration center;

The second notification processing module is configured to determine the second data center to be removed among the multiple callable data centers in response to the data center removal notification;

The second disaster determination module is used to determine that a disaster occurs in the main data center when the second data center is the main data center.

In still other embodiments of the present application, the service invoking apparatus 600 may further include:

The third notification receiving module is used to receive the status change notification sent by the registration center;

The third notification processing module is used to determine the third data center that changes the operating status in response to the status change notification;

The third disaster determination module is used to determine that a disaster occurs in the primary data center when the third data center is the primary data center and the operating state after the change of the third data center is the out of operation state.

The fourth call control module is used to send a service call request to the target service providing device corresponding to the target device address information in the case of receiving the target device address information sent by the registration center to call the target service.

The fourth notification receiving module is used to determine the fourth data center indicated by the main data center change notification among the multiple callable data centers in the case of receiving the main data center change notification sent by the registration center;

The fourth notification processing module is used to update the fourth data center as the main data center;

The fifth call control module is used to send a service call request to the fourth data center to call the target service.

It should be noted that the service invoking apparatus 600 of the embodiment shown in FIG. 6 can realize all the functions and effects of the service invoking method of the embodiment shown in FIG. 3, and the principle is similar, so it will not be repeated here.

Fig. 7 is a schematic structural diagram of another embodiment of the service invoking apparatus of the present application. Wherein, the service invoking apparatus shown in FIG. 7 can be applied to the service control device 205 in FIG. 2. As shown in FIG. 7, the service invoking apparatus 700 may include:

The first data obtaining module 710 is configured to obtain first interactive operation data;

The first data processing module 720 is configured to determine the changed operating state of the third data center and the changed operating state of the third data center in response to the first interactive operation data;

The first instruction generation module 730 is configured to generate a state change instruction according to the third data center and the operating state after the change;

The first instruction sending module 740 is configured to send a state change instruction to the registration center, so that the registration center sends a state change notification corresponding to the state change instruction to the service invoking device that invokes the target service through the third data center.

In some embodiments of the present application, the first data acquisition module 710 is specifically configured to:

In some other embodiments of the present application, the service invoking apparatus 700 may further include:

The second data acquisition module is configured to receive a user's second input operation on the state control button on the working state control interface; in response to the second input operation, acquire the second interactive operation data for the state control button;

The second data processing module is configured to determine the fourth data center to be changed as the main data center according to the second interactive operation data;

The second instruction generation module is used to generate the main data center change instruction according to the data center identifier of the fourth data center;

The second instruction sending module is used to send the main data center change instruction to the registration center, so that the registration center sends the main data center change notification corresponding to the data center change instruction to the service invoking device.

It should be noted that the service invoking apparatus 700 of the embodiment shown in FIG. 7 can realize all the functions and effects of the service invoking method of the embodiment shown in FIG. 4, and the principle is similar, so it will not be repeated here.

Fig. 8 is a schematic structural diagram of an embodiment of the service invoking device of the present application. As shown in FIG. 8, the service invoking device may include a processor 801 and a memory 802 storing computer program instructions.

Specifically, the aforementioned processor 801 may include a central processing unit (CPU), or a specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

The memory 802 may include mass storage for data or instructions. For example and not limitation, the memory 802 may include a hard disk drive (Hard Disk Drive, HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a Universal Serial Bus (USB) drive, or two or more Multiple combinations of these. Where appropriate, the storage 802 may include removable or non-removable (or fixed) media. Where appropriate, the memory 802 may be inside or outside the integrated gateway disaster recovery device. In a particular embodiment, the memory 802 is a non-volatile solid-state memory. In a particular embodiment, the memory 802 includes read-only memory (ROM). Where appropriate, the ROM can be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically rewritable ROM (EAROM) or flash memory or A combination of two or more of these.

The processor 801 reads and executes computer program instructions stored in the memory 802 to implement any one of the service invoking methods in the foregoing embodiments.

In an example, the service invoking device may further include a communication interface 803 and a bus 810. Among them, as shown in FIG. 8, the processor 801, the memory 802, and the communication interface 803 are connected through a bus 810 and complete mutual communication.

The communication interface 803 is mainly used to implement communication between various modules, devices, units and/or devices in the embodiments of the present application.

The bus 810 includes hardware, software, or both, and couples the components of the service invoking device to each other. By way of example and not limitation, the bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industry standard architecture (EISA) bus, front side bus (FSB), hyper transfer (HT) interconnect, industry standard architecture (ISA) Bus, Infinite Bandwidth Interconnect, Low Pin Count (LPC) Bus, Memory Bus, Micro Channel Architecture (MCA) Bus, Peripheral Component Interconnect (PCI) Bus, PCI-Express (PCI-X) Bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association Local (VLB) bus or other suitable bus or a combination of two or more of these. Where appropriate, the bus 810 may include one or more buses. Although the embodiments of this application describe and show a specific bus, this application considers any suitable bus or interconnection.

The service invoking device implements the various functions of the service invoking method and device described in conjunction with FIG. 1 to FIG. 7, and will not be repeated here.

In addition, in combination with the service invoking method in the foregoing embodiment, the embodiment of the present application may provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any one of the service invoking methods in the foregoing embodiments is implemented. An example of the computer-readable storage medium may be a non-transitory computer-readable storage medium, including ROM, RAM, magnetic disk, or optical disk.

It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figure. For the sake of brevity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown. After understanding the spirit of the present application, those skilled in the art can make various changes, modifications and additions, or change the sequence between the steps.

The functional blocks shown in the above-mentioned structural block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, and so on. When implemented in software, the elements of this application are programs or code segments used to perform required tasks. The program or code segment may be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link through a data signal carried in a carrier wave. "Machine-readable medium" may include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and so on. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above steps, that is, the steps may be performed in the order mentioned in the embodiments, or may be different from the order in the embodiments, or several steps may be performed at the same time.

The above are only specific implementations of the present application. Those skilled in the art can clearly understand that for the convenience and conciseness of description, the specific working process of the above-described systems, modules and units can be referred to the foregoing method embodiments. The corresponding process in, I will not repeat it here. It should be understood that the scope of protection of this application is not limited to this, and any person skilled in the art can easily think of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should cover Within the scope of protection of this application.

Claims

A service invocation method, including:

In the case of a disaster in the main data center, stop calling the target service through the main data center; wherein the target service has a plurality of callable data centers, and the plurality of callable data centers corresponds to the target service Service provision equipment information is determined, the data center with the highest priority among the multiple callable data centers is the main data center, and the data centers other than the main data center among the multiple callable data centers are disaster recovery data Center, the priority of the multiple callable data centers is determined according to the preset data center priority of the target service;

Determine the first data center with the highest priority among the disaster recovery data centers according to the data center priority;

Send a service invocation request to the first data center to invoke the target service.
The method according to claim 1, wherein, in the case of a disaster in the main data center, before stopping invoking the target service through the main data center, the method further comprises:

Sending a subscription request for subscribing to the target service to the registry;

Receiving the service providing device information fed back by the registration center.
The method according to claim 2, wherein the service providing device information includes a plurality of service providing devices supporting the target business and the device information of each of the service providing devices, and the device information includes the information of the data center to which it belongs. Data center identification.
The method according to claim 3, wherein, in the case of a disaster in the main data center, before stopping invoking the target service through the main data center, the method further comprises:

Acquiring multiple data center identifiers corresponding to the service providing equipment in the service providing equipment information;

According to the obtained data center identifier, a plurality of the callable data centers are determined.
The method according to claim 2, wherein after the receiving the service providing device information fed back by the registration center, the method further comprises:

Acquiring the data center priority; wherein the data center priority is a priority for multiple data centers, and the multiple data centers include the callable data center;

Determine the callable data center priorities of the multiple callable data centers according to the data center priority;

According to the priority of the callable data center, the main data center is determined among the plurality of callable data centers.
5. The method according to claim 5, wherein the step of determining the primary data center among a plurality of the callable data centers according to the priority of the callable data center further comprises:

Send the service invocation request to the main data center to invoke the target service.
The method according to claim 5, wherein the determining the first data center with the highest priority among the disaster recovery data centers according to the priority of the data center comprises:

According to the callable data center priority, the first data center is determined in the disaster recovery data center.
The method according to claim 3, wherein the device information further includes device operation information and device address information.
The method according to claim 8, wherein the sending a service invocation request to the first data center to invoke the target service comprises:

Determine the first service providing device belonging to the first data center according to the data center identifiers corresponding to the multiple service providing devices in the service providing device information;

Determining a first target service providing device in the first service providing device according to device operation information corresponding to a plurality of the service providing devices in the service providing device information and preset device invocation rules;

Determining the first target device address corresponding to the first target service providing device according to the device address information corresponding to the multiple service providing devices in the service providing device information;

Send the service invocation request to the first target service providing device through the first target device address, so as to invoke the target service.
The method according to claim 1, wherein, in the case of a disaster in the main data center, before stopping invoking the target service through the main data center, the method further comprises:

Receive notifications of service exceptions;

In response to the service abnormality notification, determine the device operating status of at least one second service providing device in the main data center that supports the target service;

In a case where it is determined that the device operating state of at least one of the second service providing devices is an abnormal operating state, it is determined that a disaster occurs in the main data center.
The method according to claim 10, wherein the service abnormality notification is a notification sent by the main data center and/or a notification sent by a registration center.
The method according to claim 1, wherein, in the case of a disaster in the main data center, before stopping invoking the target service through the main data center, the method further comprises:

Receive the data center removal notice sent by the registration center;

In response to the data center removal notification, determining the second data center to be removed among the plurality of callable data centers;

In a case where the second data center is the main data center, it is determined that a disaster occurs in the main data center.
The method according to claim 1, wherein, in the case of a disaster in the main data center, before stopping invoking the target service through the main data center, the method further comprises:

Receive status change notifications sent by the registry;

In response to the status change notification, determine a third data center that changes its operating status;

In a case where the third data center is the main data center and the changed operation state of the third data center is a stopped operation state, it is determined that a disaster has occurred in the main data center.
The method according to claim 1, wherein, in the case of a disaster in the main data center, after stopping invoking the target service through the main data center, the method further comprises:

In the case of receiving the target device address information sent by the registration center, sending a service invocation request to the target service providing device corresponding to the target device address information to invoke the target service.
The method according to claim 1, further comprising:

In the case of receiving the main data center change notification sent by the registration center, among the multiple callable data centers, determine the fourth data center indicated by the main data center change notification;

Update the fourth data center as the main data center;

Send the service invocation request to the fourth data center to invoke the target service.
A service invocation method, including:

Obtain the first interactive operation data;

In response to the first interactive operation data, determining the changed operating state of the third data center and the changed operating state of the third data center;

Generating a state change instruction according to the third data center and the operating state after the change;

Sending the state change instruction to a registration center, so that the registration center sends a state change notification corresponding to the state change instruction to a service invoking device that invokes a target service through the third data center.
The method according to claim 16, wherein said obtaining the first interactive operation data comprises:

Receive a user's first input operation on the target state control button on the working state control interface; wherein, the working state control interface includes a plurality of data centers registered on the registration center and each data center corresponding Multiple status control buttons;

In response to the first input operation, first interactive operation data for the target state control button is acquired.
A service calling device includes:

The first call control module is used to stop calling the target service through the main data center in the case of a disaster in the main data center; wherein the target service has multiple callable data centers, and multiple callable data The center determines according to the service providing equipment information corresponding to the target service, the data center with the highest priority among the multiple callable data centers is the main data center, and among the multiple callable data centers, except for the main data center The other data centers in are disaster recovery data centers, and the priorities of the multiple callable data centers are determined according to the preset data center priorities of the target service;

A data center reselection module, configured to determine the first data center with the highest priority among the disaster recovery data centers according to the data center priority;

The second call control module is configured to send a service call request to the first data center to call the target service.
A service calling device includes:

The first data acquisition module is used to acquire the first interactive operation data;

The first data processing module is configured to determine the changed operating state of the third data center and the changed operating state of the third data center in response to the first interactive operation data;

The first instruction generation module is configured to generate a state change instruction according to the third data center and the operating state after the change;

The first instruction sending module is configured to send the state change instruction to the registration center, so that the registration center sends the state change notification corresponding to the state change instruction to the service invoking device that invokes the target service through the third data center .
A service calling device includes: a processor and a memory storing computer program instructions;

The processor implements the service invoking method according to any one of claims 1-15 or claims 16-17 when executing the computer program instructions.
A computer storage medium on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the service invoking method according to any one of claims 1-15 or claims 16-17 is implemented .