CN114553943B - A cloud platform business layer unified information rollback method, device, terminal and medium - Google Patents

Abstract

The invention relates to a unified information rollback method, device, terminal and medium of a cloud platform business layer. In the present invention, after the service caller initiates the target business operation, it calls the external interface of the microservice that the target business operation depends on layer by layer to prepare the corresponding target resource; if the call to the external interface succeeds in preparing the target resource, the prepared target resource The resource information is archived; if the call to the external interface fails to prepare the target resource, the resource information of the corresponding target resource is queried according to the target business operation; the rollback interface for performing the rollback operation is queried from the service registration center of the microservice according to the content of the resource information; Use the rollback interface to roll back the acquisition of the corresponding content from the corresponding resource information. The present invention utilizes the resource information of the archived target business operation to obtain the rollback interface for realizing the rollback, and unifies the rollback of each microservice that the target business operation depends on through each rollback interface, and the code implementation is simple and convenient for maintenance and expansion.

Description

A cloud platform business layer unified information rollback method, device, terminal and medium

technical field

The present invention relates to the technical field of unified information rollback of microservice business layer, in particular to a method, device, terminal and medium of unified information rollback of cloud platform business layer.

Background technique

With the development of the Internet, the scale of website applications continues to expand and demand surges, and the system architecture is therefore constantly evolving, upgrading, and iterating. At present, the previous monolithic architecture has developed into a microservice architecture. With the rise of the cloud native boom, the software architecture of cloud native applications is generally a microservice architecture.

The microservice architecture is a way or approach to develop a single application using a set of small services. Each service is built based on a single business capability, runs in its own process, and communicates using a lightweight mechanism, usually HTTP API, and can pass Automated deployment mechanism to deploy independently. These services are managed and maintained by a unified service registry.

Although each service has its own single business capability, it does not mean that there is no need for business logic interaction between services. Once there is business logic interaction, there will inevitably be a scenario where the interaction fails, and after the failure, in some scenarios, it will face the problem that the previous successful operation needs to be rolled back and canceled. For cloud platforms, this scenario occurs especially frequently. For example, to create a cloud host on the cloud platform, you need to prepare network resources and storage resources before creating it; in the cloud host management service, you need to call the HTTP interface of the network resource management service and storage resource management service to prepare in advance network resources and storage resources. However, if the network resources and storage resources are prepared successfully, the creation of the cloud host fails. At this time, it is necessary to roll back and cancel the previously prepared network and storage resources to ensure the consistency of system information and avoid Generate garbage data in the system.

In the case of not using distributed transaction control, the rollback design generally involves the interaction between various dependent microservices, and the caller writes business code in its own business layer to call the resource rollback interface of related dependent microservices to perform the rollback. Roll control, so that every time an error occurs, business code needs to be written separately for additional processing, which will undoubtedly cause code redundancy and duplication, which is not conducive to later maintenance and expansion.

Contents of the invention

In order to solve the above-mentioned technical problems or at least partly solve the above-mentioned technical problems, the present invention provides a unified information rollback method, device, terminal and medium of a cloud platform business layer.

In the first aspect, the present invention provides a unified information rollback method for the business layer of the cloud platform, including:

After the service caller initiates the target business operation, it calls the external interface of the microservice that the target business operation depends on layer by layer to prepare the corresponding target resources;

If the external interface is called to prepare the target resource successfully, the resource information of the prepared target resource will be archived. The data structure of the resource information includes: resource ID, service caller IP, microservice IP to which the resource belongs, operation type and operation parameters ;

If it fails to call the external interface to prepare the target resource, query the resource information of the corresponding target resource according to the target business operation; query the rollback interface for performing the rollback operation from the service registration center of the microservice according to the content of the resource information; use the rollback interface to Get the corresponding content from the corresponding resource information to roll back.

Furthermore, when defining the interface of each microservice, configure the corresponding interface type for the interface. The interface type includes: internal interface and external interface; further configure the operation type implemented by the external interface for the external interface, where the operation type includes: create , Delete, Modify and Query.

Furthermore, when initiating a target business operation, configure the corresponding operation ID for the target business operation; when archiving the prepared resource information of the target resource, map the resource information corresponding to the target business operation to the operation ID of the target business operation .

Furthermore, when querying the resource information of the corresponding target resource according to the target business operation, the operation ID of the target business operation is obtained, and the corresponding resource information is queried according to the operation ID.

Further, the rollback interface for querying and executing the rollback operation from the service registration center of the microservice according to the content of the resource information includes:

Analyze the data structure of each archived resource information of the target business operation to obtain each target operation type and the microservice IP to which the corresponding target resource belongs;

Determine the corresponding target reverse operation type according to the target operation type in the resource information by using the pre-configured correspondence table between the operation type and the reverse operation type;

Use each target reverse operation type and the microservice IP to which the corresponding target resource belongs, and query each corresponding rollback interface from the service registry.

Furthermore, when each microservice is registered to the service registration center, the external interface information is reported to the service registration center, wherein the external interface information includes: interface name, interface type, operation type and operation parameters.

Furthermore, when using the rollback interface to roll back the acquisition of the corresponding content from the corresponding resource information, the corresponding content is acquired from the resource information according to the operation type of the rollback interface.

In a second aspect, the present invention provides a device for implementing a unified information rollback method of the cloud platform business layer, including: a failure detection module, the failure detection module detects whether the call target business operation relies on the microservice external interface to prepare the target resource successfully;

A resource information archiving module, the resource information archiving module archives the resource information of the prepared target resource according to a preset data structure when the target resource is successfully prepared;

A resource information matching module, the resource information matching module queries corresponding resource information according to the target business matching when the target resource required for the target business operation fails;

A resource information analysis module, the resource information analysis module analyzes the resource information to obtain the content of the resource information;

A rollback interface matching module, the rollback interface matching module queries the corresponding rollback interface from the service registration center that configures each microservice by using the content of the resource information;

A rollback execution module, the rollback execution module uses the rollback interface and the corresponding content in the corresponding resource information to perform rollback.

In the third aspect, the present invention provides a terminal for realizing the unified information rollback method of the business layer of the cloud platform, including: a processing unit, a bus unit, a storage unit, a display unit, and an input unit, the bus unit is connected to the processing unit, storage unit, a display unit, and an input unit, the storage unit stores at least one instruction, and the processing unit reads and executes the instruction to implement the method for rolling back unified information of the cloud platform business layer.

In a fourth aspect, the present invention provides a storage medium for implementing a unified information rollback method for the cloud platform business layer, wherein the storage medium for implementing the unified information rollback method for the cloud platform business layer stores at least one instruction, and reads and executes the instruction Realize the unified information rollback method of the cloud platform business layer.

Compared with the prior art, the technical solution provided by the embodiments of the present invention has the following advantages:

In the present invention, when the target resource is successfully prepared for the target business operation, the resource information of the successfully prepared target resource is archived, and the resource information includes the resource ID of the target resource, the service caller IP, the microservice IP to which the target resource belongs, and the operation type and operating parameters. Once the preparation of the target resource fails, query the corresponding resource information archive according to the target business operation. The resource information archive contains the resource information of all target resources that have been prepared before the failure occurs, and is the object of rollback. In the present invention, the operation type in the resource information is used to determine the corresponding reverse operation type, and the reverse operation type is the operation type for realizing the rollback interface for resource rollback recorded in the resource information. Query the rollback interface for performing rollback from the service registry through the microservice IP to which the target resource belongs and the reverse operation type in the resource information, and use the rollback interface to roll back the target resource recorded in the resource information. In this way, the rollback operation of each microservice that the target business operation depends on can be unified by using a unified method, the code is simple to implement, and it is convenient for later maintenance and expansion.

In this application, when defining the operation interface of the microservice, configure the operation type of the external interface, define the operation type of the external interface, and provide the interface information including the operation type when registering with the service registration center, for subsequent operations based on the resource information The type and the corresponding reverse operation type provide the basis for the subsequent query of the external interface from the service registry to obtain the corresponding rollback interface based on the operation type.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description serve to explain the principles of the invention.

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, In other words, other drawings can also be obtained from these drawings without paying creative labor.

Fig. 1 is the flow chart of a kind of cloud platform business layer unified information rollback method provided by the embodiment of the present invention;

2 is a flow chart of a rollback interface for querying and performing a rollback operation from a service registration center of a microservice according to the content of resource information provided by an embodiment of the present invention;

FIG. 3 is a schematic diagram of a device for implementing a method for rolling back unified information of a cloud platform business layer provided by an embodiment of the present invention;

FIG. 4 is a schematic diagram of a terminal implementing a method for rolling back unified information of a service layer of a cloud platform provided by an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

It should be noted that, in this document, the terms "comprising", "comprising" or any other variation thereof are intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

Example 1

The embodiment of the present invention provides a cloud platform business layer unified information rollback method. In order to implement this method, when defining the interface of each micro service, configure the corresponding interface type for the interface. The interface type includes: internal interface and external interface; further For the external interface, configure the operation type implemented by the external interface, where the operation type includes: create, delete, modify, and query. When registering each microservice to the service registration center, report the external interface information to the service registration center, where the external interface information includes: interface name, interface type, operation type and operation parameters; the operation type and microservice IP through the external interface The corresponding external interface can be found from the service registry of the microservice.

Referring to shown in Figure 1, the unified information rollback method of the cloud platform business layer includes:

S100, after the service caller initiates the target business operation, call the external interface of the microservice that the target business operation depends on layer by layer to prepare the corresponding target resources; in the specific implementation process, when the service caller initiates the target business operation, the target business operation Configure the corresponding operation ID.

S200. Detect whether calling the external interface of the microservice on which the target business operation depends is successful in preparing the target resource. If yes, execute S300; otherwise, execute S400.

S300, if calling the external interface to prepare the target resource is successful, then archive the resource information of the prepared target resource, the data structure of the resource information includes: resource ID, service caller IP, microservice IP to which the resource belongs, operation type and Operating parameters; in the specific implementation process, build a unified rollback controller for each microservice rollback, use the rollback controller to archive the resource information of the prepared target resource, and when archiving, target business operation The corresponding resource information is mapped to the operation ID of the target business operation.

S400, if calling the external interface to prepare the target resource fails, query the resource information of the corresponding target resource according to the target business operation; when querying the resource information of the corresponding target resource according to the target business operation, obtain the operation ID of the target business operation, and ID query corresponding resource information. In the specific implementation process, when the target business operation fails to prepare the target resource, the rollback controller is notified to roll back the target business operation. The notification includes the operation ID of the target business operation, and the rollback controller uses the operation ID of the target business operation to query the corresponding Resource information for the target resource for . The resource information queried by using the operation ID is the resource information of all target resources that have been prepared before the failure occurs.

S500. Query the rollback interface for executing the rollback operation from the service registration center of the microservice according to the content of the resource information; in the specific implementation process, refer to FIG. 2 , query from the service registration center of the microservice according to the content of the resource information The rollback interfaces for performing rollback operations include:

S501. Analyze the data structure of each archived resource information of the target business operation to obtain each target operation type and the microservice IP to which the corresponding target resource belongs. Specifically, the rollback controller parses the data structure of each archived resource information of the target business operation to obtain each target operation type and the microservice IP to which the corresponding target resource belongs.

S502. Using a pre-configured correspondence table between operation types and reverse operation types to determine a corresponding target reverse operation type according to the target operation type in the resource information. Specifically, the rollback controller determines the corresponding target reverse operation type according to the target operation type in the resource information by using the pre-configured correspondence table between the operation type and the reverse operation type.

Specifically, when the record operation type in the correspondence table is creation, the corresponding reverse operation type is delete; when the operation type is modification, the corresponding reverse operation type is modification. When the operation type is delete, if the corresponding reverse operation type is create, the resource created by using the create type to the external interface is actually a new resource compared with the deleted resource, so this application does not respond to the delete operation. Scrolling, that is, the reverse operation type that does not set create as delete in the corresponding relationship table.

S503. Using each target reverse operation type and the microservice IP to which the corresponding target resource belongs, query each corresponding rollback interface from the service registration center. When each microservice is registered to the service registration center, the external interface information is reported to the service registration center, wherein the external interface information includes: interface name, interface type, operation type and operation parameters; therefore, the rollback controller passes the external interface The operation type and microservice IP can find the corresponding external interface from the service registration center of the microservice.

S600. Use a rollback interface to roll back the acquisition of corresponding content from corresponding resource information. During the specific implementation process, when the rollback controller uses the rollback interface to roll back the corresponding content obtained from the corresponding resource information, it obtains the corresponding content from the resource information according to the operation type of the rollback interface. For example: when the operation type of the rollback interface is delete (the operation type in the corresponding resource information is create), obtain the resource ID from the corresponding resource information, and delete the resource mapped to the resource ID to complete the corresponding resource in the resource information rollback cancellation. When the operation type of the rollback interface is modification (the operation type in the corresponding resource information is modification), obtain the resource ID and operation parameters from the corresponding resource information, and reversely modify the operation parameters in the resource mapped by the resource ID. Complete the rollback cancellation of the resource corresponding to the resource information.

In the specific implementation process, the present invention records the corresponding operation log after the target business operation is rolled back successfully.

Example 2

Referring to FIG. 3 , an embodiment of the present invention provides a device for implementing a unified information rollback method of the cloud platform business layer, including: a failure detection module, the failure detection module detects that the calling target business operation depends on the microservice external interface preparation target whether the resource was successful;

A resource information archiving module, the resource information archiving module archives the resource information of the prepared target resource according to a preset data structure when the target resource is successfully prepared;

A resource information matching module, the resource information matching module queries corresponding resource information according to the target business matching when the target resource required for the target business operation fails;

A resource information analysis module, the resource information analysis module analyzes the resource information to obtain the content of the resource information;

A rollback interface matching module, the rollback interface matching module queries the corresponding rollback interface from the service registration center that configures each microservice by using the content of the resource information;

A rollback execution module, the rollback execution module uses the rollback interface and the corresponding content in the corresponding resource information to perform rollback;

A log module, the log module records the log of the rollback process of each target business operation.

Example 3

As shown in FIG. 4 , an embodiment of the present invention provides a terminal for implementing a unified information rollback method of a cloud platform business layer, including: a processing unit, a bus unit, a storage unit, a display unit, and an input unit, and the bus unit is connected to the A processing unit, a storage unit, a display unit, and an input unit, the storage unit stores at least one instruction, and the processing unit reads and executes the instruction to implement the method for rolling back unified information of the cloud platform business layer.

Example 4

The embodiment of the present invention provides a storage medium for realizing the unified information rollback method of the cloud platform business layer. The storage medium for realizing the unified information rollback method of the cloud platform business layer stores at least one instruction, reads and executes the instruction to realize the The unified information rollback method of the cloud platform business layer described above.

In the present invention, when the target resource is successfully prepared for the target business operation, the resource information of the successfully prepared target resource is archived, and the resource information includes the resource ID of the target resource, the service caller IP, the microservice IP to which the target resource belongs, and the operation type and operating parameters. Once the preparation of the target resource fails, query the corresponding resource information archive according to the target business operation. The resource information archive contains the resource information of all target resources that have been prepared before the failure occurs, and is the object of rollback. In the present invention, the operation type in the resource information is used to determine the corresponding reverse operation type, and the reverse operation type is the operation type for realizing the rollback interface for resource rollback recorded in the resource information. Query the rollback interface for performing rollback from the service registry through the microservice IP to which the target resource belongs and the reverse operation type in the resource information, and use the rollback interface to roll back the target resource recorded in the resource information. In this way, a unified rollback controller is used to unify the rollback operations of various microservices that the target business operation depends on, the code is simple to implement, and it is convenient for later maintenance and expansion.

In this application, when defining the operation interface of the microservice, configure the operation type of the external interface, define the operation type of the external interface, and provide the interface information including the operation type when registering with the service registration center, for subsequent operations based on the resource information The type and the corresponding reverse operation type provide the basis for the subsequent query of the external interface from the service registry to obtain the corresponding rollback interface based on the operation type.

In the embodiments provided in the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

The above descriptions are only specific embodiments of the present invention, so that those skilled in the art can understand or implement the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Accordingly, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims (9)

1. A cloud platform business layer unified information rollback method, is characterized in that, comprises: After the service caller initiates the target business operation, it calls the external interface of the microservice that the target business operation depends on layer by layer to prepare the corresponding target resources; If the external interface is called to prepare the target resource successfully, the resource information of the prepared target resource will be archived. The data structure of the resource information includes: resource ID, service caller IP, microservice IP to which the resource belongs, operation type and operation parameters ; If it fails to call the external interface to prepare the target resource, query the resource information of the corresponding target resource according to the target business operation; query the rollback interface for performing the rollback operation from the service registration center of the microservice according to the content of the resource information: parse the target business operation The data structure of each archived resource information obtains each target operation type and the microservice IP to which the corresponding target resource belongs, and uses the pre-configured correspondence table between the operation type and the reverse operation type to determine the corresponding target operation type according to the resource information. Target reverse operation type, use each target reverse operation type and the microservice IP to which the corresponding target resource belongs, and query each corresponding rollback interface from the service registry; The rollback interface performs rollback based on resource information. 2. cloud platform business layer unified information rollback method according to claim 1, is characterized in that, when defining the interface of each microservice, for interface configuration corresponding interface type, interface type comprises: internal interface and external interface; Further configure the operation type implemented by the external interface for the external interface, where the operation type includes: create, delete, modify, and query. 3. The cloud platform business layer unified information rollback method according to claim 1, characterized in that, when the target business operation is initiated, a corresponding operation ID is configured for the target business operation; the resource information of the prepared target resource is archived , map the resource information corresponding to the target business operation to the operation ID of the target business operation. 4. The cloud platform business layer unified information rollback method according to claim 3, characterized in that, when querying the resource information of the corresponding target resource according to the target business operation, obtain the operation ID of the target business operation, and query according to the operation ID Corresponding resource information. 5. The cloud platform business layer unified information rollback method according to claim 1, characterized in that, when each microservice is registered to the service registration center, the external interface information is reported to the service registration center, wherein the external interface information includes : Interface name, interface type, operation type, and operation parameters. 6. The cloud platform business layer unified information rollback method according to claim 1, wherein when the rollback interface performs rollback based on resource information, the corresponding content is obtained from the resource information according to the operation type of the rollback interface. 7. A device for realizing the unified information rollback method of the cloud platform business layer, characterized in that it includes: a failure detection module, and the failure detection module detects whether the micro-service external interface that calls the target business operation relies on to prepare the target resource successfully; A resource information archiving module, the resource information archiving module archives the resource information of the prepared target resource according to a preset data structure when the target resource is successfully prepared; A resource information matching module, when the resource information matching module fails to prepare the target resource required for the target business operation, query the corresponding resource information according to the target business matching; A resource information analysis module, the resource information analysis module analyzes the resource information to obtain the content of the resource information; The rollback interface matching module, the rollback interface matching module uses the content of the resource information to query the corresponding rollback interface from the service registration center that configures each microservice, including: analyzing the data structure of each archived resource information of the target business operation to obtain Each target operation type and the microservice IP to which the corresponding target resource belongs, use the pre-configured correspondence table between the operation type and the reverse operation type to determine the corresponding target reverse operation type according to the target operation type in the resource information, and use each target The type of reverse operation and the microservice IP to which the corresponding target resource belongs, and each corresponding rollback interface is queried from the service registry; A rollback execution module, the rollback execution module uses the rollback interface and the corresponding content in the corresponding resource information to perform rollback. 8. A terminal for realizing the unified information rollback method of the cloud platform business layer, characterized in that it includes: a processing unit, a bus unit, a storage unit, a display unit and an input unit, and the bus unit is connected to the processing unit and the storage unit , a display unit and an input unit, the storage unit stores at least one instruction, and the processing unit reads and executes the instruction to implement the cloud platform business layer unified information rollback method according to any one of claims 1-6. 9. A storage medium that realizes the unified information rollback method of the cloud platform business layer, is characterized in that, the storage medium that realizes the unified information rollback method of the cloud platform business layer stores at least one instruction, and the processor reads and executes the described The instruction realizes the unified information rollback method of the cloud platform business layer as described in any one of claims 1-6.