CN114265605A

CN114265605A - Version rollback method and device for functional component of business system

Info

Publication number: CN114265605A
Application number: CN202111618915.5A
Authority: CN
Inventors: 马宁; 黄文宝; 刘波; 王燕; 陶春雨; 程广向; 陈长鹏; 孙晓峰; 刘成杰; 周文峰; 吴方正
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2021-12-27
Filing date: 2021-12-27
Publication date: 2022-04-01

Abstract

The invention discloses a version rollback method and device for a functional component of a business system, and relates to the technical field of security services. One embodiment of the method comprises: receiving a version rollback request, and determining a current functional component corresponding to the version rollback request and a current business system version number corresponding to the current functional component; determining a corresponding functional component in the version number of the last service system as a backspacing functional component according to the current functional component and the version number of the current service system; registering a rollback functional component in an enterprise service bus, and determining a target server node for deploying the rollback functional component; and updating the configuration information of the enterprise service bus in the target server node according to the registration information of the backspacing functional component in the enterprise service bus, and deploying the backspacing functional component in the target server node. The implementation mode improves the pertinence of the version rollback of the business system, simplifies the version rollback process, shortens the time consumed by the version rollback and improves the user experience.

Description

Version rollback method and device for functional component of business system

Technical Field

The invention relates to the technical field of security services, in particular to a version rollback method and device for a functional component of a business system.

Background

The establishment of a management system of service operation continuity is helpful for ensuring that important services can be quickly recovered after an interruption event occurs in the operation, reducing or eliminating the influence and loss caused by the interruption of the operation of the important services, and ensuring the continuous operation of the services.

In order to ensure that services can be continuously operated, the existing service system adopts a full version deployment mode, and when a certain subsystem or some subsystems have faults in the service operation process, the version of the whole service system is backed to the version of the previous service system, so that the continuous operation of the services is ensured.

The prior art has at least the following problems:

in the existing service system version rollback method, the whole service system version is rolled back, so that a plurality of associated subsystems need to be rolled back cooperatively, the system version rollback process is difficult, the influence on the whole service system is large, the time consumption is long, and the user experience is poor.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method and an apparatus for version rollback of a functional component of a business system, which can request to determine a part of functional components that generate a business fault, and only perform version rollback on the part of functional components, so as to improve the pertinence of the business system for version rollback, simplify the version rollback process, shorten the time consumed for version rollback, reduce the overall impact on the business system, and improve user experience.

To achieve the above object, according to an aspect of the embodiments of the present invention, there is provided a version rollback method for a functional component of a business system, including:

receiving a version rollback request, and determining a current functional component corresponding to the version rollback request and a current business system version number corresponding to the current functional component;

determining a corresponding functional component in the version number of the last service system as a backspacing functional component according to the current functional component and the version number of the current service system;

registering a rollback functional component in an enterprise service bus, and determining a target server node for deploying the rollback functional component;

and updating the configuration information of the enterprise service bus in the target server node according to the registration information of the backspacing functional component in the enterprise service bus, and deploying the backspacing functional component in the target server node.

Further, the version rollback request includes a service failure log, receives the version rollback request, and determines a current functional component corresponding to the version rollback request and a current service system version number corresponding to the current functional component, including:

receiving a version rollback request, and analyzing and processing a service fault log in the version rollback request;

and determining the current functional component generating the service fault and the corresponding current system version number according to the analysis processing result.

Further, according to the current functional component and the version number of the current service system, determining that the corresponding functional component in the version number of the previous service system is a fallback functional component includes:

acquiring a plurality of version information of a service system, wherein the version information comprises version numbers and functional component information;

and determining the functional component corresponding to the current functional component in the version number of the last service system as a backspacing functional component according to the version information, the current functional component and the version number of the current service system.

Further, the version rollback request further includes the number of failed services, and the step of determining the target server node to deploy the rollback function component further includes:

acquiring the number of server nodes in a server cluster;

and determining one or more server nodes from the server cluster as target server nodes according to the number of the fault services and the number of the server nodes, wherein the one or more server nodes are used for deploying the rollback functional component.

Further, after the step of determining the corresponding functional component in the previous service system version number as the fallback functional component according to the current functional component and the current service system version number, the method further includes:

determining the number of the backspacing functional components, and judging whether the number of the backspacing functional components exceeds a threshold value of the number of the functional components;

if not, registering the rollback function component in the enterprise service bus, and determining a target server node for deploying the rollback function component; deploying a rollback function component in a target server node;

and if so, returning the current business system version to the previous business system version.

Further, still include:

receiving service fault recovery information and determining a functional component to be upgraded;

and updating and upgrading the backspacing functional component corresponding to the functional component to be upgraded.

According to another aspect of the embodiments of the present invention, there is provided a version rollback apparatus for a functional component of a business system, including:

the receiving module is used for receiving the version rollback request and determining a current functional component corresponding to the version rollback request and a current business system version number corresponding to the current functional component;

the backspacing functional component determining module is used for determining the corresponding functional component in the version number of the last service system as the backspacing functional component according to the current functional component and the version number of the current service system;

the system comprises a registration module, a back-off function component and a back-off function component, wherein the registration module is used for registering the back-off function component in an enterprise service bus and determining a target server node for deploying the back-off function component;

and the rollback module is used for updating the enterprise service bus configuration information in the target server node according to the registration information of the rollback functional component in the enterprise service bus, and deploying the rollback functional component in the target server node.

Further, the version rollback request further includes a number of failed services, and the registration module is further configured to:

acquiring the number of server nodes in a server cluster;

Further, the system also comprises an update upgrading module, which is used for:

According to another aspect of an embodiment of the present invention, there is provided an electronic apparatus including:

one or more processors;

a storage device for storing one or more programs,

when executed by one or more processors, cause the one or more processors to implement a version rollback method for any of the business system functional components described above.

According to a further aspect of the embodiments of the present invention, there is provided a computer readable medium, on which a computer program is stored, which when executed by a processor, implements a version rollback method for a functional component of a business system as described in any one of the above.

To achieve the above object, according to still another aspect of an embodiment of the present invention, there is provided a computer program product.

A computer program product according to an embodiment of the present invention includes a computer program, and when the computer program is executed by a processor, the computer program implements a version rollback method for any business system functional component provided in the above embodiment of the present invention.

One embodiment of the above invention has the following advantages or benefits: because the version rollback request is received, the current functional component corresponding to the version rollback request and the version number of the current business system corresponding to the current functional component are determined; determining a corresponding functional component in the version number of the last service system as a backspacing functional component according to the current functional component and the version number of the current service system; registering a rollback functional component in an enterprise service bus, and determining a target server node for deploying the rollback functional component; according to the registration information of the rollback functional component in the enterprise service bus, the enterprise service bus configuration information in the target server node is updated, and the rollback functional component is deployed in the target server node, so that the technical problems that in the conventional business system version rollback method, because the version of the whole business system is mainly rolled back, a plurality of associated subsystems need to be rolled back cooperatively, the system version rollback flow is difficult, the influence on the whole business system is large, the consumed time is long, and the user experience is poor are solved, and further the partial functional components which generate business faults can be determined by the version rollback request, and only the partial functional components are subjected to version rollback, so that the pertinence of business system version rollback is improved, the version rollback flow is simplified, the time consumed by version rollback is shortened, and the overall influence on the business system is reduced, the technical effect of user experience is improved.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

FIG. 1 is a diagram illustrating a main flow of a version rollback method for a functional component of a business system according to an embodiment of the present invention;

FIG. 2 is a diagram illustrating a main flow of a version rollback method for a functional component of a business system according to another embodiment of the present invention;

FIG. 3 is a schematic diagram of the main modules of a version rollback apparatus for business system functional components provided according to an embodiment of the present invention;

FIG. 4 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

fig. 5 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

FIG. 1 is a diagram illustrating a main flow of a version rollback method for a functional component of a business system according to an embodiment of the present invention; as shown in fig. 1, a version rollback method for a functional component of a business system according to an embodiment of the present invention mainly includes:

step S101, receiving a version rollback request, and determining a current functional component corresponding to the version rollback request and a current business system version number corresponding to the current functional component.

Specifically, according to the embodiment of the present invention, the version rollback request includes a service failure log; the receiving the version rollback request and determining the current functional component corresponding to the version rollback request and the version number of the current business system corresponding to the current functional component includes:

According to the embodiment of the invention, the version rollback request can comprise service fault information, and the functional components which need to be subjected to version rollback due to the generation of faults are determined according to the service fault log indicated in the service fault information; and a functional component indicating that version rollback is required in information such as supervision requirements, actively discovered bugs and the like can be further included.

Through the setting, the current functional component with the fault is locked according to the service fault log of the version rollback request, and then the current service system version number of the current functional component is determined, so that which functional component of which system version needs to be rolled back is determined subsequently, and for functional components which do not have the fault (the functional components which can normally run do not carry out version rollback), the targeted version rollback is improved, and the system version rollback flow is simplified.

And step S102, determining the corresponding functional component in the version number of the last service system as a backspacing functional component according to the current functional component and the version number of the current service system.

Specifically, according to an embodiment of the present invention, the determining, according to the current functional component and the version number of the current service system, that the functional component corresponding to the version number of the previous service system is a fallback functional component includes:

In order to ensure that the service can continuously run, the service system usually adopts a full version deployment mode, and by acquiring a plurality of versions of information of the service system, the rollback functional component can be quickly determined, and the version rollback efficiency is improved.

And step S103, registering the rollback function component in the enterprise service bus, and determining a target server node for deploying the rollback function component.

Specifically, according to the embodiment of the present invention, the version rollback request further includes a number of failed services; the step of determining the target server node to deploy the fallback functional component further includes:

acquiring the number of server nodes in a server cluster;

When the number of the target server nodes of the deployment rollback functional component is determined, the total number of the server nodes in the server cluster and the number of the fault services are taken into consideration, so that the service system can be effectively ensured to execute service operation for a long time, and overload of a certain functional component is avoided.

The ESB is called Enterprise Service Bus (Enterprise Service Bus) and is a product of the combination of the traditional middleware technology and technologies such as XML, Web Service and the like. The ESB provides the most basic connection center in the network and is an essential element for constructing the nervous system of an enterprise. The emergence of the ESB changes the traditional software architecture, can provide a cheaper solution than the traditional middleware products, and at the same time, it can eliminate the technical difference between different applications, let different application servers operate in coordination, and realize the communication and integration between different services. Functionally, the ESB provides an event-driven and document-oriented processing model, as well as a distributed run-time management mechanism that supports content-based routing and filtering, has complex data transfer capabilities, and can provide a range of standard interfaces.

The order of the steps is not intended to limit the present invention. According to the embodiment of the invention, all versions of functional component information can be registered in the enterprise service bus, after the current functional component and the corresponding rollback functional component thereof are determined according to the version rollback request, only the server node needs to be determined, and then the component which is recorded in the enterprise service bus in the server node and executes the corresponding function is pointed to the rollback functional component from the original current functional component.

Further, according to the embodiment of the present invention, after the step of determining, according to the current functional component and the current service system version number, that the functional component corresponding to the last service system version number is the fallback functional component, the method further includes:

Through the setting and the combination of the threshold value of the number of the functional components, if the current functional components with faults in the current service system are more (namely, the corresponding rollback functional components are more), at this time, the service system can be subjected to integral rollback; if the threshold number of functional components is not exceeded, version rollback may be performed for a portion of the functional components. The previous version refers to a version released before the current version according to the version number. According to a specific implementation manner of the embodiment of the present invention, the threshold of the number of functional components may be determined according to actual situations, for example, if the business system includes n functional components, half of n may be used as the threshold of the number of functional components, and if the number of fallback functional components exceeds half of all functional components, the whole business system is version-backed.

And step S104, updating enterprise service bus configuration information in the target server node according to the registration information of the rollback function component in the enterprise service bus, and deploying the rollback function component in the target server node.

Specifically, according to the embodiment of the present invention, the enterprise service bus configuration information in the target server node is updated according to the registration information of the fallback functional component in the enterprise service bus, so that a connection relationship between the target server node and the fallback functional component can be established, and when the server receives a service that needs to be executed by the fallback functional component, the server can forward the service to the fallback functional component for performing corresponding function processing.

Further, according to an embodiment of the present invention, the method further includes:

Through the setting, for the condition of service failure recovery, namely the current functional component generating the failure finishes the maintenance work and can normally operate, at the moment, the rollback functional component is updated and upgraded.

According to the technical scheme of the embodiment of the invention, the version rollback request is received, and the current functional component corresponding to the version rollback request and the version number of the current business system corresponding to the current functional component are determined; determining a corresponding functional component in the version number of the last service system as a backspacing functional component according to the current functional component and the version number of the current service system; registering a rollback functional component in an enterprise service bus, and determining a target server node for deploying the rollback functional component; according to the registration information of the rollback functional component in the enterprise service bus, the enterprise service bus configuration information in the target server node is updated, and the rollback functional component is deployed in the target server node, so that the technical problems that in the conventional business system version rollback method, because the version of the whole business system is mainly rolled back, a plurality of associated subsystems need to be rolled back cooperatively, the system version rollback flow is difficult, the influence on the whole business system is large, the consumed time is long, and the user experience is poor are solved, and further the partial functional components which generate business faults can be determined by the version rollback request, and only the partial functional components are subjected to version rollback, so that the pertinence of business system version rollback is improved, the version rollback flow is simplified, the time consumed by version rollback is shortened, and the overall influence on the business system is reduced, the technical effect of user experience is improved.

FIG. 2 is a diagram illustrating a main flow of a version rollback method for a functional component of a business system according to another embodiment of the present invention; as shown in fig. 2, a version rollback method for a functional component of a business system according to an embodiment of the present invention mainly includes:

step S201, receiving a version rollback request, and analyzing and processing a service fault log in the version rollback request; and determining the current functional component generating the service fault and the corresponding current system version number according to the analysis processing result.

Step S202, acquiring a plurality of version information of the service system, wherein the version information comprises version numbers and functional component information; and determining the functional component corresponding to the current functional component in the version number of the last service system as a backspacing functional component according to the version information, the current functional component and the version number of the current service system.

Step S203, determining the number of the rollback functional components, and judging whether the number of the rollback functional components exceeds a functional component number threshold value. If not, namely the number of the backspacing functional components does not exceed the threshold value of the number of the functional components, executing the step S204; if yes, that is, the number of fallback functional components exceeds the threshold value of the number of functional components, step S207 is executed.

Through the setting and the combination of the threshold value of the number of the functional components, if the current functional components with faults in the current service system are more (namely, the corresponding rollback functional components are more), at this time, the service system can be subjected to integral rollback; if the threshold number of functional components is not exceeded, version rollback may be performed for a portion of the functional components.

And step S204, registering the rollback function component in the enterprise service bus, and acquiring the number of the server nodes in the server cluster.

Step S205, according to the number of the fault services and the number of the server nodes, one or more server nodes are determined from the server cluster as target server nodes for deploying the rollback function components.

Step S206, according to the registration information of the rollback function component in the enterprise service bus, updating the enterprise service bus configuration information in the target server node, and deploying the rollback function component in the target server node.

Step S207, rolling back the current service system version to the previous service system version as a whole.

The previous version refers to a version released before the current version according to the version number.

FIG. 3 is a schematic diagram of the main modules of a version rollback apparatus for business system functional components provided according to an embodiment of the present invention; as shown in fig. 3, a version rollback apparatus 300 for a functional component of a business system according to an embodiment of the present invention mainly includes:

the receiving module 301 is configured to receive a version rollback request, and determine a current functional component corresponding to the version rollback request and a current service system version number corresponding to the current functional component.

Specifically, according to the embodiment of the present invention, the version rollback request includes a service failure log; the receiving module 301 is further configured to:

A rollback function component determining module 302, configured to determine, according to the current function component and the current service system version number, that a function component corresponding to the previous service system version number is a rollback function component.

Specifically, according to an embodiment of the present invention, the fallback function component determining module 302 is further configured to:

And a registering module 303, configured to register the fallback functional component in the enterprise service bus, and determine a target server node where the fallback functional component is deployed.

Specifically, according to the embodiment of the present invention, the version rollback request further includes a number of failed services, and the registration module 303 is further configured to:

acquiring the number of server nodes in a server cluster;

Further, according to the embodiment of the present invention, the version rollback apparatus 300 of the service system functional component further includes a determining module, after the step of determining, according to the current functional component and the current service system version number, that the functional component corresponding to the previous service system version number is the rollback functional component, configured to:

And the rollback module 304 is configured to update the configuration information of the enterprise service bus in the target server node according to the registration information of the rollback functional component in the enterprise service bus, and deploy the rollback functional component in the target server node.

Further, according to the embodiment of the present invention, the version rollback apparatus 300 of the service system functional component further includes an update module, configured to:

one or more processors;

a storage device for storing one or more programs,

Fig. 4 illustrates an exemplary system architecture 400 to which a version rollback method of a business system functional component or a version rollback apparatus of a business system functional component of an embodiment of the present invention may be applied.

As shown in fig. 4, the system architecture 400 may include

terminal devices

401, 402, 403, a network 404, and a server 405 (this architecture is merely an example, and the components included in a particular architecture may be adapted according to application specific circumstances). The network 404 serves as a medium for providing communication links between the

terminal devices

401, 402, 403 and the server 405. Network 404 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

A user may use

terminal devices

401, 402, 403 to interact with a server 405 over a network 404 to receive or send messages or the like. The

terminal devices

401, 402, 403 may have installed thereon various communication client applications, such as a version-back type application, a web browser application, a search type application, a data processing type tool, etc. (by way of example only).

The

terminal devices

401, 402, 403 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 405 may be a server that provides various services, such as a server (for example only) that performs version rollback/data processing for a user with the

terminal device

401, 402, 403. The server may analyze and perform other processing on the received data such as the version rollback request, and feed back the processing result (e.g., the rollback function component, the target server node, just an example) to the terminal device.

It should be noted that the version rollback method for the business system functional component provided in the embodiment of the present invention is generally executed by the server 405, and accordingly, the version rollback apparatus for the business system functional component is generally disposed in the server 405.

It should be understood that the number of terminal devices, networks, and servers in fig. 4 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 5, a block diagram of a computer system 500 suitable for use with a terminal device or server implementing an embodiment of the invention is shown. The terminal device or the server shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 5, the computer system 500 includes a Central Processing Unit (CPU)501 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage section 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the system 500 are also stored. The CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.

The following components are connected to the I/O interface 505: an input portion 506 including a keyboard, a mouse, and the like; an output portion 507 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 508 including a hard disk and the like; and a communication section 509 including a network interface card such as a LAN card, a modem, or the like. The communication section 509 performs communication processing via a network such as the internet. The driver 510 is also connected to the I/O interface 505 as necessary. A removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 510 as necessary, so that a computer program read out therefrom is mounted into the storage section 508 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 509, and/or installed from the removable medium 511. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 501.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

A computer program product of an embodiment of the invention, comprising a computer program which, when executed by a processor, implements the method of any one of claims 1-8.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a receiving module, a fallback function component determining module, a registering module, and a fallback module. The names of these modules do not constitute a limitation to the module itself in some cases, for example, the receiving module may also be described as "a module for receiving a version rollback request, determining a current functional component corresponding to the version rollback request and a current business system version number corresponding to the current functional component".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: receiving a version rollback request, and determining a current functional component corresponding to the version rollback request and a current business system version number corresponding to the current functional component; determining a corresponding functional component in the version number of the last service system as a backspacing functional component according to the current functional component and the version number of the current service system; registering a rollback functional component in an enterprise service bus, and determining a target server node for deploying the rollback functional component; and updating the configuration information of the enterprise service bus in the target server node according to the registration information of the backspacing functional component in the enterprise service bus, and deploying the backspacing functional component in the target server node.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A version rollback method for a business system functional component is characterized by comprising the following steps:

determining the corresponding functional component in the version number of the last service system as a backspacing functional component according to the current functional component and the version number of the current service system;

registering the rollback function component in an enterprise service bus, and determining a target server node for deploying the rollback function component;

and updating enterprise service bus configuration information in the target server node according to the registration information of the rollback function component in the enterprise service bus, and deploying the rollback function component in the target server node.

2. The method according to claim 1, wherein the version rollback request includes a service failure log, and the receiving the version rollback request and determining the current functional component corresponding to the version rollback request and the current service system version number corresponding to the current functional component comprise:

receiving the version rollback request, and analyzing and processing a service fault log in the version rollback request;

3. The method for version rollback of a functional component in a business system according to claim 1, wherein the determining that the functional component corresponding to the previous business system version number is a rollback functional component according to the current functional component and the current business system version number comprises:

4. The version rollback method for a business system functional component of claim 1, wherein the version rollback request further includes a number of failed businesses, and wherein the step of determining the target server node to deploy the rollback functional component further comprises:

acquiring the number of server nodes in a server cluster;

and determining one or more server nodes from the server cluster as target server nodes according to the number of the fault services and the number of the server nodes, and deploying the rollback function component.

5. The method for version rollback of a functional component in a business system according to claim 4, wherein after the step of determining that the functional component corresponding to the previous business system version number is a rollback functional component according to the current functional component and the current business system version number, the method further comprises:

determining the number of the backspacing functional components, and judging whether the number of the backspacing functional components exceeds a functional component number threshold value;

if not, registering the rollback function component in an enterprise service bus, and determining a target server node for deploying the rollback function component; deploying the fallback functional component in the target server node;

6. The method for version rollback of a business system functional component of claim 1, further comprising:

7. A version rollback apparatus for a business system functional component, comprising:

a receiving module, configured to receive a version rollback request, and determine a current functional component corresponding to the version rollback request and a current service system version number corresponding to the current functional component;

a rollback function component determining module, configured to determine, according to the current function component and the current service system version number, a function component corresponding to a previous service system version number as a rollback function component;

the registration module is used for registering the rollback function component in an enterprise service bus and determining a target server node for deploying the rollback function component;

and the rollback module is used for updating enterprise service bus configuration information in the target server node according to the registration information of the rollback functional component in the enterprise service bus, and deploying the rollback functional component in the target server node.

8. The version rollback apparatus of a business system functional component of claim 7, wherein the version rollback request further comprises a number of failed businesses, and wherein the registration module is further configured to:

acquiring the number of server nodes in a server cluster;

9. The version rollback apparatus for business system functional components of claim 7, further comprising an update upgrade module configured to:

10. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-6.

11. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-6.

12. A computer program product comprising a computer program, characterized in that the computer program realizes the method according to any of claims 1-6 when executed by a processor.