Component management system, method, device, electronic device and storage medium

Abstract

The present application provides a component management system, method, device, electronic device and storage medium. The component management system includes a common component library deployed in each business middle station, an index middleware deployed in each business middle station, and a cloud service compiler deployed in each business middle station. Each business middle station is deployed in a different cloud environment. Each business middle station is configured as follows: in response to a call request, the local target common component is located through the index middleware of the local middle station; if the cloud environment of the local middle station is consistent with the cloud environment of the target foreground application, the local target common component is used as a compatible target common component, and the compatible target common component is pushed to the target foreground application; if the cloud environment of the local middle station is different from the cloud environment of the target foreground application, the local target common component is compiled into a compatible target common component through the cloud service compiler of the local middle station, and the compatible target common component is pushed to the target foreground application. The present application can improve the reusability of common components.

Description

Technical Field

[0001] The present application relates to the field of cloud services, and specifically to a component management system, method, device, electronic device and storage medium. Background Art

[0002] As application service scenarios become more complex and fragmented, the number of components stored and managed by the business middle platform deployed in the cloud environment is increasing. In the prior art, the components of the same application service must be in the same cloud environment, which means that once the business middle platform of the application service is deployed in the cloud environment, the components stored in the business middle platform must be highly bound to the cloud service provider, resulting in low reusability of the components stored in the business middle platform. Summary of the invention

[0003] One purpose of the present application is to provide a component management system, method, device, electronic device and storage medium that can improve the reusability of components.

[0004] According to one aspect of an embodiment of the present application, a component management system is disclosed, wherein the component management system includes a common component library deployed in each business middle station, an index middleware deployed in each business middle station, and a cloud service compiler deployed in each business middle station, wherein each business middle station is deployed in a different cloud environment, and each business middle station is configured as follows:

[0005] In response to a call request from a target foreground application for a target public component, the local target public component stored in the public component library of the local middle station is located through the index middleware of the local middle station;

[0006] If the cloud environment of the local middle platform is consistent with the cloud environment of the target foreground application, the local target public component is used as a compatible target public component suitable for the cloud environment of the target foreground application, and the compatible target public component is pushed to the target foreground application;

[0007] If the cloud environment of the local middle station is different from the cloud environment of the target foreground application, the local target common component is compiled into the compatible target common component by the cloud service compiler of the local middle station, and the compatible target common component is pushed to the target foreground application.

[0008] According to one aspect of an embodiment of the present application, a component management method is disclosed, the method being applied to each business middle station in a component management system, the component management system comprising an index middleware deployed in each business middle station, a cloud service compiler deployed in each business middle station, and a public component library deployed in each business middle station, each business middle station being deployed in a different cloud environment, the method comprising:

[0009] In response to a call request from a target foreground application for a target public component, the local target public component stored in the public component library of the local middle station is located through the index middleware of the local middle station;

[0010] If the cloud environment of the local middle platform is consistent with the cloud environment of the target foreground application, the local target public component is used as a compatible target public component suitable for the cloud environment of the target foreground application, and the compatible target public component is pushed to the target foreground application;

[0011] If the cloud environment of the local middle station is different from the cloud environment of the target foreground application, the local target common component is compiled into the compatible target common component by the cloud service compiler of the local middle station, and the compatible target common component is pushed to the target foreground application.

[0012] According to one aspect of an embodiment of the present application, a component management device is disclosed, characterized in that the device is arranged in each business middle station in a component management system, the component management system includes an index middleware deployed in each business middle station, a cloud service compiler deployed in each business middle station, and a public component library deployed in each business middle station, each business middle station is deployed in a different cloud environment, and the device includes:

[0013] A local positioning module is configured to respond to a call request of a target foreground application for a target public component, and locate a local target public component stored in a public component library of the local middle station through an index middleware of the local middle station;

[0014] A first push module is configured to, if the cloud environment of the local middle station is consistent with the cloud environment of the target foreground application, use the local target public component as a compatible target public component applicable to the cloud environment of the target foreground application, and push the compatible target public component to the target foreground application;

[0015] The second push module is configured to compile the local target common component into the compatible target common component through the cloud service compiler of the local middle station if the cloud environment of the local middle station is different from the cloud environment of the target foreground application, and push the compatible target common component to the target foreground application.

[0016] According to one aspect of an embodiment of the present application, an electronic device is disclosed, comprising: a memory storing computer-readable instructions; and a processor reading the computer-readable instructions stored in the memory to execute any one of the methods described in the above claims.

[0017] According to one aspect of an embodiment of the present application, a computer-readable storage medium is disclosed, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes any one of the methods described in the above claims.

[0018] According to one aspect of the embodiments of the present application, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in the above various optional implementations.

[0019] The embodiment of the present application sets up a common component library for storing common components, an index middleware for locating common components, and a cloud service compiler for handling cloud environment compatibility in each business middle station, so that even a business middle station that is incompatible with the cloud environment can respond to the call request of the target foreground application for the target common component, and the business middle stations can avoid repeated management of common components, thereby improving the reusability of the common components.

[0020] Other features and advantages of the present application will become apparent from the following detailed description, or may be learned in part by the practice of the present application.

[0021] It should be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above and other objects, features and advantages of the present application will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0023] Figure 1 A flowchart of a component management method according to an embodiment of the present application is shown.

[0024] Figure 2 A schematic diagram of component management interaction according to an embodiment of the present application is shown.

[0025] Figure 3 A schematic diagram of component management interaction according to an embodiment of the present application is shown.

[0026] Figure 4 A schematic diagram of component management interaction according to an embodiment of the present application is shown.

[0027] Figure 5 A schematic diagram of component management interaction according to an embodiment of the present application is shown.

[0028] Figure 6A block diagram of a component management device according to an embodiment of the present application is shown.

[0029] Figure 7 A hardware diagram of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0030] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these example embodiments are provided so that the description of the present application will be more comprehensive and complete and the concepts of the example embodiments will be fully conveyed to those skilled in the art. The accompanying drawings are only schematic illustrations of the present application and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and thus their repeated description will be omitted.

[0031] In addition, the described features, structures or characteristics may be combined in one or more example embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the example embodiments of the present application. However, those skilled in the art will appreciate that the technical solution of the present application may be practiced while omitting one or more of the specific details, or other methods, components, steps, etc. may be adopted. In other cases, known structures, methods, implementations or operations are not shown or described in detail to avoid obscuring the present application and making the various aspects of the present application obscure.

[0032] Some of the blocks shown in the accompanying drawings are functional entities that do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0033] The present application provides a component management system, the main purpose of which is to manage components of a business middle platform deployed in a cloud environment to improve the reusability of common components therein.

[0034] The component management system provided in the present application includes a public component library, an index middleware and a cloud service compiler, wherein the public component library, the index middleware and the cloud service compiler are deployed in each business platform.

[0035] Figure 1 A component management method according to an embodiment of the present application is shown. The execution subject of the method is each business middle station in the component management system. The method includes:

[0036] Step S110, in response to a call request of a target foreground application for a target public component, locate the local target public component stored in the public component library of the local middle station through the index middleware of the local middle station;

[0037] Step S120: If the cloud environment of the local middle platform is consistent with the cloud environment of the target foreground application, the local target public component is used as a compatible target public component suitable for the cloud environment of the target foreground application, and the compatible target public component is pushed to the target foreground application;

[0038] Step S130: If the cloud environment of the local middle station is different from the cloud environment of the target foreground application, the local target public component is compiled into a compatible target public component by the cloud service compiler of the local middle station, and the compatible target public component is pushed to the target foreground application.

[0039] In the embodiment of the present application, the target common components requested to be called by the target foreground application may be distributed in the common component libraries of multiple business middle stations. In this case, each business middle station needs to push the local target common components stored in the common component library of the local middle station to the target foreground application, so that the target foreground application can obtain all the required target common components according to the local target common components of each business middle station.

[0040] In order to push the local target common component to the target foreground application, after the business middle station receives the call request for the target common component from the target foreground application, it locates the local target common component through the index middleware of the local middle station. It should be noted that the call request for the target common component from the target foreground application received by the business middle station can be sent directly by the target foreground application or sent via other business middle stations.

[0041] Before pushing the local target common components to the target foreground application, for compatibility reasons, the business middle station determines whether the cloud environment of the local middle station is consistent with the cloud environment of the target foreground application.

[0042] If they are consistent, it means that the local target common component is applicable to the cloud environment of the target foreground application and the two are compatible. Then the local target common component is used as the compatible target common component and the compatible target common component is pushed to the target foreground application.

[0043] If they are different, it means that the local target public component is not suitable for the cloud environment of the target foreground application, and the two are incompatible. Then, the local target public component is first compiled into a compatible target public component through the cloud service compiler of the local middle platform, and then the compatible target public component is pushed to the target foreground application.

[0044] Because the business middle station will process the local target public components for cloud environment compatibility through the cloud service compiler before pushing them to the target foreground application, even if the business middle station is incompatible with the cloud environment, it can respond to the target foreground application's call request for the target public components. Therefore, the business middle stations can avoid repeated management of public components, thereby improving the reusability of public components.

[0045] It can be seen that the embodiment of the present application sets up a common component library for storing common components, an index middleware for locating common components, and a cloud service compiler for handling cloud environment compatibility in each business middle station, so that even a business middle station that is incompatible with the cloud environment can respond to the call request of the target foreground application for the target common component, and the business middle stations can avoid repeated management of common components, thereby improving the reusability of common components.

[0046] In one embodiment, each common component library may store the following types of common components: service components, application components, and middleware.

[0047] In one embodiment, each index middleware stores the following information of each public component in the component management system: physical address, virtual machine version, cloud environment, component description information. Based on the stored information, the index middleware can address and locate the specified public component.

[0048] In one embodiment, the component management system further includes a cloud service compiler deployed in the target foreground application. The target foreground application is configured to send a call request for the target common component to each business middle station, and obtain compatible target common components through each business middle station. The compatible target common components are compiled and sorted according to the service sequence of the target common components through the local foreground cloud service compiler to obtain an application service for outputting services.

[0049] In this embodiment, the target foreground application sends a call request for the target common component to each business middle station, thereby obtaining the compatible target common component pushed by each business middle station.

[0050] Specifically, a cloud service compiler is deployed in the target foreground application. The cloud service compiler of the target foreground application is mainly used to compile compatible target public components to obtain application services for output services.

[0051] After receiving the service request initiated by the user, the target foreground application determines the common components required to respond to the service request and the corresponding service sequence, wherein the common components required to respond to the service request are the target common components.

[0052] Then the target foreground application generates a call request for the target common component, and sends the call request for the target common component to each business middle station. Then each business middle station responds to the call request for the target common component, locates the local target common component through the index middleware of the local middle station, and then processes the local target common component for cloud environment compatibility to obtain a compatible target common component, and then pushes the compatible target common component to the target foreground application.

[0053] After the target front-end application obtains the corresponding part of the compatible target common components from each business middle-end, it compiles and sorts the obtained compatible target common components according to the service sequence of the target common components through the local front-end cloud service compiler to obtain the application service for outputting services. The service output by the application service is mainly used to respond to the service request initiated by the user.

[0054] It should be noted that in this embodiment, a business middle station that does not store any target common components will also receive a call request for a target common component. In this case, after the business middle station that does not store any target common components receives a call request for a target common component, the local target common component cannot be located through the index middleware of the local middle station, and the business middle station does not need to push the target common component to the target foreground application.

[0055] Figure 2 A schematic diagram of component management interaction according to an embodiment of the present application is shown.

[0056] In this embodiment, there are three business middle stations, namely business middle station A, business middle station B and business middle station C. Different public components are stored in the public component library of each business middle station. The front-end application A and the business middle station A are deployed in the same cloud environment. A cloud service compiler is deployed in the front-end application A.

[0057] The user initiates a service request to the front-end application A through the channel touchpoint.

[0058] Based on the service request, the foreground application A determines that the common component a and the common component e are needed to respond to the service request. Therefore, the foreground application A requests each business middle station to call the common component a and the common component e.

[0059] In response to the received call request, business middle station A locates the public component a stored in the local middle station through the index middleware of the local middle station. Since business middle station A and front-end application A are deployed in the same cloud environment, business middle station A can directly push public component a to front-end application A, so that front-end application A obtains compatible public component a.

[0060] In response to the received call request, business middle station B locates the public component e stored in the local middle station through the index middleware of the local middle station. Since the cloud environment of business middle station B is inconsistent with the cloud environment of foreground application A, business middle station B compiles the public component e through the cloud server compiler of the local middle station, so that the compiled public component e is compatible with the cloud environment of foreground application A, and then pushes the compiled public component e to foreground application A, so that foreground application A obtains the compatible public component e.

[0061] In response to the received call request, the business middle station C cannot locate any common components required by the foreground application A stored in the local middle station through the index middleware of the local middle station. Therefore, the business middle station C does not push any common components to the foreground application A.

[0062] After the foreground application A obtains the compatible public component a and the compatible public component e, it compiles the compatible public component a and the compatible public component e according to the service sequence through the local foreground cloud service compiler, thereby providing services to users.

[0063] In one embodiment, the component management system also includes a cloud service compiler deployed in the target foreground application. The target foreground application is configured to send a call request for the target common component to the same environment business middle station in the same cloud environment as the local foreground, and obtain compatible target common components through the same environment business middle station. Through the cloud service compiler of the local foreground, the compatible target common components are compiled and sorted according to the service sequence of the target common components to obtain application services for output services. The same environment business middle station is also configured to respond to the call request for the target common component, locate the external target common component stored in the public component library of the external middle station through the index middleware of the local middle station. Send the call request for the external target common component to the different environment business middle station where the external target common component is located.

[0064] In this embodiment, the target foreground application sends a call request for the target common component to the same-environment business middle station, and then the same-environment business middle station sends the call request for the target common component to other different-environment business middle stations that store the target common components, and then the target foreground application obtains the compatible target common components pushed by the same-environment business middle station and the compatible target common components pushed by the different-environment business middle station.

[0065] Specifically, a cloud service compiler is deployed in the target foreground application. The cloud service compiler of the target foreground application is mainly used to compile compatible target public components to obtain application services for output services.

[0066] After receiving the service request initiated by the user, the target foreground application determines the corresponding target common component and the corresponding service sequence. Then the target foreground application generates a call request for the target common component, and then sends the call request for the target common component to the same environment business middle station. Among them, the same environment business middle station refers to the business middle station in the same cloud environment as the target foreground application.

[0067] After the same-environment business middle station receives the call request for the target common component, it responds to the call request for the target common component and locates the local target common component through the index middleware of the local middle station; then, the local target common component is processed for cloud environment compatibility to obtain a compatible target common component; and then, the compatible target common component is pushed to the target foreground application.

[0068] Moreover, after receiving the call request for the target common component, the same environment business middle station will also locate the external target common component stored in the common component library of the external middle station through the index middleware of the same environment business middle station in response to the call request for the target common component, that is, locate the external target common component stored outside the same environment business middle station. Then the same environment business middle station generates a call request for the external target common component, and sends the call request for the external target common component to the different environment business middle station where the external target common component is located.

[0069] Compared with the external target common components of the same environment business middle station, it is the local target common component relative to the heterogeneous environment business middle station. Therefore, after the heterogeneous environment business middle station receives the call request for its local target common component, it responds to the call request for its local target common component and locates its local target common component through the index middleware of the local middle station; then it performs cloud environment compatibility processing on its local target common component to obtain a compatible target common component; then it pushes the compatible target common component to the target foreground application.

[0070] In this way, the target foreground application can obtain the corresponding part of the compatible target common components from the same environment business middle station, and under the forwarding effect of the same environment business middle station on the call request, trigger the environment business middle station to push the corresponding part of the compatible target common components, and then obtain the corresponding part of the compatible target common components from the different environment business middle station. Then, the target foreground application compiles and sorts the obtained compatible target common components according to the service sequence of the target common components through the local foreground cloud service compiler, and obtains the application service for output service.

[0071] The advantage of this embodiment is that the call request is forwarded by the business middle station in the same environment, which avoids sending the call request to the business middle station where the target public component is not stored during the component call process, thereby reducing signaling consumption.

[0072] Figure 3 A schematic diagram of component management interaction according to an embodiment of the present application is shown.

[0073] In this embodiment, there are three business middle stations, namely business middle station A, business middle station B and business middle station C. Different public components are stored in the public component library of each business middle station. If the front-end application A and the business middle station A are deployed in the same cloud environment, the same-environment business middle station of the front-end application A is business middle station A, and the different-environment business middle stations are business middle stations B and C. A cloud service compiler is deployed in the front-end application A.

[0074] The user initiates a service request to the front-end application A through the channel touchpoint.

[0075] Based on the service request, the foreground application A determines that the public component a and the public component e are needed to respond to the service request. The foreground application A requests the business middle station A to call the public component a and the public component e.

[0076] In response to the received call request, business middle station A locates the public component a stored in the local middle station through the index middleware of the local middle station, and then business middle station A can directly push the public component a to the foreground application A, so that the foreground application A obtains the compatible public component a; and, business middle station A locates the public component e stored in business middle station B through the index middleware of the local middle station, and then informs business middle station B that the foreground application A requests to call the public component e.

[0077] In response to the received call request, business middle station B locates the public component e stored in the local middle station through the index middleware of the local middle station, and then compiles the public component e through the cloud server compiler of the local middle station, so that the compiled public component e is compatible with the cloud environment of the foreground application A, and then pushes the compiled public component e to the foreground application A, so that the foreground application A obtains the compatible public component e.

[0078] After the foreground application A obtains the compatible public component a and the compatible public component e, it compiles the compatible public component a and the compatible public component e according to the service sequence through the local foreground cloud service compiler, thereby providing services to users.

[0079] In one embodiment, the component management system also includes an index middleware deployed in the target foreground application and a cloud service compiler deployed in the target foreground application. The target foreground application is configured as follows: the target business middle station storing the target common components is located through the index middleware of the local foreground. The call requests for the target common components are sent to the corresponding target business middle stations respectively, and the compatible target common components are obtained through the target business middle station. Through the cloud service compiler of the local foreground, the compatible target common components are compiled and sorted according to the service sequence of the target common components to obtain the application service for outputting the service.

[0080] In this embodiment, the target foreground application sends a call request for the target common component to the target business middle station storing the target common component, thereby obtaining the compatible target common component pushed by the target business middle station.

[0081] Specifically, the index middleware and the cloud server compiler are deployed in the target foreground application. The cloud service compiler of the target foreground application is mainly used to compile compatible target public components to obtain application services for output services.

[0082] After receiving the service request initiated by the user, the target foreground application determines the corresponding target common component and the corresponding service sequence. Then the target foreground application generates a call request for the target common component, locates the target business middle station through the local foreground index middleware, and then only sends the call request for the target common component to the target business middle station.

[0083] After the target business middle station receives the call request for the target common component, it responds to the call request for the target common component and locates the local target common component through the index middleware of the local middle station; then it performs cloud environment compatibility processing on the local target common component to obtain a compatible target common component; and then it pushes the compatible target common component to the target foreground application.

[0084] After the target foreground application obtains the corresponding part of the compatible target common components from each target business middle platform, it compiles and sorts the obtained compatible target common components according to the service sequence of the target common components through the local foreground cloud service compiler to obtain the application service for output service.

[0085] The advantage of this embodiment is that, by deploying the index middleware in the target foreground application, the target foreground application can locate each target common component by itself, thereby improving the selection flexibility of the target foreground application in the process of calling the target common component.

[0086] Figure 4 A schematic diagram of component management interaction according to an embodiment of the present application is shown.

[0087] In this embodiment, there are three business middle stations, namely business middle station A, business middle station B and business middle station C. Different public components are stored in the public component library of each business middle station. The front-end application A and the business middle station A are deployed in the same cloud environment. The index middleware and the cloud service compiler are deployed in the front-end application A.

[0088] The user initiates a service request to the front-end application A through the channel touchpoint.

[0089] Based on the service request, the foreground application A determines that the public component a and the public component e are needed to respond to the service request. Therefore, the foreground application A locates the public component a stored in the business middle station A and the public component e stored in the business middle station B through the local foreground index middleware. Then the foreground application requests the business middle station A to call the public component a and the public component e, and requests the business middle station B to call the public component a and the public component e.

[0090] In response to the received call request, the business middle station A locates the public component a stored in the local middle station through the index middleware of the local middle station, and then the business middle station A can directly push the public component a to the foreground application A, so that the foreground application A obtains the compatible public component a.

[0091] In response to the received call request, business middle station B locates the public component e stored in the local middle station through the index middleware of the local middle station, and then compiles the public component e through the cloud server compiler of the local middle station, so that the compiled public component e is compatible with the cloud environment of the foreground application A, and then pushes the compiled public component e to the foreground application A, so that the foreground application A obtains the compatible public component e.

[0092] After the foreground application A obtains the compatible public component a and the compatible public component e, it compiles the compatible public component a and the compatible public component e according to the service sequence through the local foreground cloud service compiler, thereby providing services to users.

[0093] Figure 5 A schematic diagram of component management interaction according to an embodiment of the present application is shown.

[0094] This embodiment and Figure 4 The main difference between the illustrated embodiments is that after the foreground application A locates the target common component through the local foreground index middleware, it specifically requests the business middle platform storing the target common component to call the corresponding target common component.

[0095] Specifically, different from Figure 4 In the illustrated embodiment, the foreground application A requests the business middle station A to call the common component a and the common component e, and requests the business middle station B to call the common component a and the common component e. Figure 5In the illustrated embodiment, the foreground application A requests the business middle station A to call the common component a, and requests the business middle station B to call the common component e.

[0096] Figure 6 A component management device according to an embodiment of the present application is shown, the device is arranged in each business middle station in the component management system, the component management system includes index middleware deployed in each business middle station, cloud service compiler deployed in each business middle station, and public component library deployed in each business middle station, each business middle station is deployed in a different cloud environment, and the device includes:

[0097] The local positioning module 210 is configured to respond to a call request of a target foreground application for a target public component, and locate the local target public component stored in the public component library of the local middle station through the index middleware of the local middle station;

[0098] The first push module 220 is configured to, if the cloud environment of the local middle station is consistent with the cloud environment of the target foreground application, use the local target common component as a compatible target common component applicable to the cloud environment of the target foreground application, and push the compatible target common component to the target foreground application;

[0099] The second push module 230 is configured to compile the local target common component into the compatible target common component through the cloud service compiler of the local middle station if the cloud environment of the local middle station is different from the cloud environment of the target foreground application, and push the compatible target common component to the target foreground application.

[0100] Reference below Figure 7 The electronic device 30 according to the embodiment of the present application is described. Figure 7 The electronic device 30 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0101] like Figure 7 As shown, the electronic device 30 is in the form of a general computing device. The components of the electronic device 30 may include but are not limited to: at least one processing unit 310, at least one storage unit 320, and a bus 330 connecting different system components (including the storage unit 320 and the processing unit 310).

[0102] The storage unit stores program codes, which can be executed by the processing unit 310, so that the processing unit 310 performs the steps according to various exemplary embodiments of the present invention described in the description of the exemplary method described above in this specification. For example, the processing unit 310 can perform the following steps: Figure 1 The steps shown in .

[0103] The storage unit 320 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 3201 and / or a cache memory unit 3202 , and may further include a read-only memory unit (ROM) 3203 .

[0104] The storage unit 320 may also include a program / utility 3204 having a set (at least one) of program modules 3205, such program modules 3205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0105] Bus 330 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0106] The electronic device 30 may also communicate with one or more external devices 400 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 30, and / or may communicate with any device that enables the electronic device 30 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 350. The input / output (I / O) interface 350 is connected to a display unit 340. Furthermore, the electronic device 30 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 360. As shown, the network adapter 360 communicates with other modules of the electronic device 30 via a bus 330. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 30, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0107] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0108] In an exemplary embodiment of the present application, a computer-readable storage medium is further provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the method described in the above method embodiment.

[0109] According to one embodiment of the present application, a program product for implementing the method in the above method embodiment is also provided, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited to this. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0110] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0111] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0112] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0113] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as JAVA, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0114] It should be noted that, although several modules or units of the equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into being embodied by multiple modules or units.

[0115] In addition, although the steps of the method in the present application are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0116] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the implementation methods of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation methods of the present application.

[0117] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the appended claims.

Claims

1. A component management system, characterized in that: The component management system includes a public component library deployed in each business platform, an index middleware deployed in each business platform, and a cloud service compiler deployed in each business platform. Each business platform is deployed in a different cloud environment. Each business platform is configured as follows: In response to a call request from a target foreground application for a target public component, the local target public component stored in the public component library of the local middle station is located through the index middleware of the local middle station; If the cloud environment of the local middle platform is consistent with the cloud environment of the target foreground application, the local target public component is used as a compatible target public component suitable for the cloud environment of the target foreground application, and the compatible target public component is pushed to the target foreground application; If the cloud environment of the local middle station is different from the cloud environment of the target foreground application, the local target public component is compiled into the compatible target public component by the cloud service compiler of the local middle station, and the compatible target public component is pushed to the target foreground application; The component management system also includes a cloud service compiler deployed in the target foreground application, and the target foreground application is configured to: send a call request for the target common component to each business middle station, and obtain the compatible target common component through each business middle station; through the local foreground cloud service compiler, compile and sort the compatible target common component according to the service sequence of the target common component to obtain an application service for output service.

2. The component management system according to claim 1, characterized in that: The component management system further includes a cloud service compiler deployed in the target foreground application, and the target foreground application is configured as follows: Sending a call request for the target public component to a business middle station in the same cloud environment as the local front end, and obtaining the compatible target public component through the business middle station in the same cloud environment; Compiling and sorting the compatible target common components according to the service sequence of the target common components through a local front-end cloud service compiler to obtain an application service for outputting services; The same environment business middle platform is also configured as: In response to a call request for the target public component, locating the external target public component stored in the public component library of the external middle station through the index middleware of the local middle station; The call request for the external target common component is sent to the heterogeneous environment business middle station where the external target common component is located.

3. The component management system according to claim 1, characterized in that: The component management system further includes an index middleware deployed in the target foreground application and a cloud service compiler deployed in the target foreground application. The target foreground application is configured as follows: Locate the target business middle platform storing the target common component through the index middleware of the local front end; Sending the call requests for the target common components to the corresponding target business middle stations respectively, and obtaining the compatible target common components through the target business middle stations; The compatible target common components are compiled and sorted according to the service sequence of the target common components by a local foreground cloud service compiler to obtain an application service for outputting services.

4. The component management system according to claim 1 or 3, characterized in that: Each index middleware stores the following information of each public component in the component management system: physical address, virtual machine version, cloud environment, and component description information.

5. A component management method, characterized in that: The method is applied to each business middle station in a component management system, the component management system includes index middleware deployed in each business middle station, cloud service compiler deployed in each business middle station, and public component library deployed in each business middle station, each business middle station is deployed in a different cloud environment, and the method includes: In response to a call request from a target foreground application for a target public component, the local target public component stored in the public component library of the local middle station is located through the index middleware of the local middle station; If the cloud environment of the local middle platform is consistent with the cloud environment of the target foreground application, the local target public component is used as a compatible target public component suitable for the cloud environment of the target foreground application, and the compatible target public component is pushed to the target foreground application; If the cloud environment of the local middle station is different from the cloud environment of the target foreground application, the local target common component is compiled into the compatible target common component through the cloud service compiler of the local middle station, and the compatible target common component is pushed to the target foreground application; the target foreground application is triggered to compile and sort the compatible target common component according to the service sequence of the target common component through the cloud service compiler of the local foreground, and obtain the application service for output service.

6. A component management device, characterized in that: The device is arranged in each business middle station in the component management system, and the component management system includes index middleware deployed in each business middle station, cloud service compiler deployed in each business middle station, and public component library deployed in each business middle station, and each business middle station is respectively deployed in different cloud environments, and the device includes: A local positioning module is configured to respond to a call request of a target foreground application for a target public component, and locate a local target public component stored in a public component library of the local middle station through an index middleware of the local middle station; A first push module is configured to, if the cloud environment of the local middle station is consistent with the cloud environment of the target foreground application, use the local target public component as a compatible target public component applicable to the cloud environment of the target foreground application, and push the compatible target public component to the target foreground application; The second push module is configured to compile the local target common components into the compatible target common components through the cloud service compiler of the local middle station and push the compatible target common components to the target foreground application if the cloud environment of the local middle station is different from the cloud environment of the target foreground application; trigger the target foreground application to compile and sort the compatible target common components according to the service sequence of the target common components through the cloud service compiler of the local foreground to obtain the application service for output service.

7. An electronic device, characterized in that: include: a memory storing computer-readable instructions; The processor reads the computer readable instructions stored in the memory to execute the method according to claim 5.

8. A computer-readable storage medium, characterized in that: Computer readable instructions are stored thereon, and when the computer readable instructions are executed by a processor of a computer, the computer is caused to execute the method of claim 5 .

Images