[go: up one dir, main page]

CN114237684A - Component management system, method, apparatus, electronic device, and storage medium - Google Patents

Component management system, method, apparatus, electronic device, and storage medium Download PDF

Info

Publication number
CN114237684A
CN114237684A CN202111552624.0A CN202111552624A CN114237684A CN 114237684 A CN114237684 A CN 114237684A CN 202111552624 A CN202111552624 A CN 202111552624A CN 114237684 A CN114237684 A CN 114237684A
Authority
CN
China
Prior art keywords
target
component
local
service
foreground application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202111552624.0A
Other languages
Chinese (zh)
Other versions
CN114237684B (en
Inventor
俞科峰
仝建刚
李嫚
张利平
胡颖茂
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN202111552624.0A priority Critical patent/CN114237684B/en
Publication of CN114237684A publication Critical patent/CN114237684A/en
Application granted granted Critical
Publication of CN114237684B publication Critical patent/CN114237684B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/41—Compilation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/76—Adapting program code to run in a different environment; Porting

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

本申请提供了一种组件管理系统、方法、装置、电子设备及存储介质，组件管理系统包括部署于各业务中台的公用组件库，部署于各业务中台的索引中间件，部署于各业务中台的云服务编译器，各业务中台分别部署于不同的云环境，各业务中台配置为：响应于调用请求，通过本地中台的索引中间件定位本地目标公用组件；若本地中台的云环境与目标前台应用的云环境一致，则将本地目标公用组件作为兼容目标公用组件，并将兼容目标公用组件推送至目标前台应用；若本地中台的云环境与目标前台应用的云环境相异，则通过本地中台的云服务编译器将本地目标公用组件编译为兼容目标公用组件，并将兼容目标公用组件推送至目标前台应用。本申请能够提高公用组件的复用性。

Figure 202111552624

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

Figure 202111552624

Description

Component management system, method, device, electronic device and storage medium
Technical Field
The application relates to the field of cloud services, in particular to a component management system, a component management method, a component management device, electronic equipment and a storage medium.
Background
With the complication and fragmentation of application service scenarios, more and more components are stored and managed by the platform in the business deployed in the cloud environment. In the prior art, components of the same application service must be in the same cloud environment, which results in that once a business platform of the application service is deployed in the cloud environment, the components stored by the business platform must be highly bundled with a cloud service provider, thereby resulting in low reusability of the components stored by the business platform.
Disclosure of Invention
An object of the present application is to provide a component management system, method, apparatus, electronic device, and storage medium, which can improve reusability of components.
According to an aspect of the embodiments of the present application, a component management system is disclosed, where the component management system includes a common component library deployed in each business center station, an index middleware deployed in each business center station, and a cloud service compiler deployed in each business center station, where each business center station is deployed in different cloud environments, and each business center station is configured to:
responding to a calling request of a target foreground application for a target common component, and positioning a local target common component of a common component library stored in a local middle station through an 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, taking the local target common component as a compatible target common component suitable for the cloud environment of the target foreground application, and pushing the compatible target common component 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, compiling the local target common component into the compatible target common component through a cloud service compiler of the local middle station, and pushing the compatible target common component to the target foreground application.
According to an aspect of an embodiment of the present application, a component management method is disclosed, where the method is applied to each business center station in a component management system, the component management system includes an index middleware deployed in each business center station, a cloud service compiler deployed in each business center station, and a common component library deployed in each business center station, and each business center station is deployed in different cloud environments, respectively, where the method includes:
responding to a calling request of a target foreground application for a target common component, and positioning a local target common component of a common component library stored in a local middle station through an 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, taking the local target common component as a compatible target common component suitable for the cloud environment of the target foreground application, and pushing the compatible target common component 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, compiling the local target common component into the compatible target common component through a cloud service compiler of the local middle station, and pushing the compatible target common component to the target foreground application.
According to an aspect of the embodiments of the present application, a component management apparatus is disclosed, wherein the apparatus is disposed in each business center station in a component management system, the component management system includes an index middleware deployed in each business center station, a cloud service compiler deployed in each business center station, and a common component library deployed in each business center station, and each business center station is deployed in different cloud environments, and the apparatus includes:
the local positioning module is configured to respond to a calling request of a target foreground application for a target common component, and position the local target common component stored in a common component library of a local middle station through an index middleware of the local middle station;
the first pushing module is configured to take the local target common component as a compatible target common component suitable for the cloud environment of the target foreground application and push the compatible target common component to the target foreground application if the cloud environment of the local middle station is consistent with the cloud environment of the target foreground application;
and the second pushing module is configured to compile the local target common component into the compatible target common component through a cloud service compiler of the local middle station and push the compatible target common component 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.
According to an aspect of an embodiment of the present application, an electronic device is disclosed, including: a memory storing computer readable instructions; a processor reading computer readable instructions stored by the memory to perform the method of any of the preceding claims.
According to an aspect of embodiments of the present application, a computer-readable storage medium is disclosed, having computer-readable instructions stored thereon, which, when executed by a processor of a computer, cause the computer to perform the method of any of the preceding claims.
According to an aspect of embodiments herein, there is provided a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the method provided in the various alternative implementations described above.
According to the embodiment of the application, the common component library for storing the common components, the index middleware for positioning the common components and the cloud service compiler for processing cloud environment compatibility are arranged in each service center station, so that even if the service center stations with incompatible cloud environments can respond to the calling request of the target front station application for the target common components, the common components can be prevented from being repeatedly managed among the service center stations, and the reusability of the common components is improved.
Other features and advantages of the present application will be apparent from the following detailed description, or may be learned by practice of the application.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
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.
FIG. 1 shows a flow diagram of a component management method according to one embodiment of the present application.
FIG. 2 illustrates a component management interaction diagram according to one embodiment of the present application.
FIG. 3 illustrates a component management interaction diagram according to one embodiment of the present application.
FIG. 4 illustrates a component management interaction diagram according to one embodiment of the present application.
FIG. 5 illustrates a component management interaction diagram according to one embodiment of the present application.
FIG. 6 shows a block diagram of a component management apparatus according to one embodiment of the present application.
FIG. 7 illustrates an electronic device hardware diagram according to one embodiment of the present application.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these example embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The drawings are merely schematic illustrations of the present application and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. In the following description, numerous specific details are provided to give a thorough understanding of example embodiments of the present application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, steps, and so forth. In other instances, well-known structures, methods, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.
Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The application provides a component management system, which mainly aims to manage components of a service center deployed in a cloud environment so as to improve the reusability of common components in the service center.
The component management system provided by the application comprises a public component library, index middleware and a cloud service compiler. The public component library, the index middleware and the cloud service compiler are deployed in each service middle desk.
Fig. 1 illustrates a component management method according to an embodiment of the present application, where an execution subject of the method is each business middleware in a component management system, and the method includes:
step S110, responding to a calling request of a target foreground application for a target common component, and positioning a local target common component of a common component library stored in a local middle station through an index middleware of the local middle station;
step S120, if the cloud environment of the local middle station is consistent with the cloud environment of the target foreground application, taking the local target common component as a compatible target common component suitable for the cloud environment of the target foreground application, and pushing the compatible target common component to the target foreground application;
step S130, if the cloud environment of the local middle station is different from the cloud environment of the target foreground application, compiling the local target common component into a compatible target common component through a cloud service compiler of the local middle station, and pushing the compatible target common component to the target foreground application.
In the embodiment of the application, the target common component requested to be called by the target foreground application may be distributed in a common component library of a plurality of service middleboxes. In this case, each service center station needs to push the local target common component stored in the local common component library of the service center 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 the service center stations.
In consideration of pushing the local target common component to the target foreground application, after receiving a call request of the target foreground application for the target common component, the service middle station positions the local target common component through the index middleware of the local middle station. The call request of the target foreground application to the target common component, which is received by the service center station, may be directly sent by the target foreground application, or may be sent through relay of another service center station.
Before pushing the local target common component to the target foreground application, the service center judges whether the cloud environment of the local center is consistent with the cloud environment of the target foreground application or not in consideration of compatibility.
If the local target common components are consistent with the target foreground application, the local target common components are suitable for the cloud environment of the target foreground application, and the local target common components and the target foreground application are compatible. The local target common component is taken as a compatible target common component and the compatible target common component is pushed to the target foreground application.
If the difference is positive, the local target common component is not suitable for the cloud environment of the target foreground application, and the local target common component and the target foreground application are not compatible. The cloud service compiler of the local middle desk compiles the local target common component into a compatible target common component, and then pushes the compatible target common component to the target foreground application.
The cloud service compiler performs cloud environment compatibility processing on the local target common component before the business middle station pushes the local target common component to the target foreground application, so that the business middle station which is incompatible with the cloud environment can respond to a calling request of the target foreground application for the target common component, repeated management of the common component can be avoided among the business middle stations, and reusability of the common component is improved.
Therefore, according to the embodiment of the application, the common component library for storing the common components, the index middleware for positioning the common components and the cloud service compiler for processing cloud environment compatibility are arranged in each service center, so that even if the service center stations which are incompatible with the cloud environment can respond to the calling request of the target foreground application for the target common components, the common components can be prevented from being repeatedly managed among the service center stations, and the reusability of the common components is improved.
In one embodiment, each common component library may have stored therein common components of the following types: service components, application components, and middleware.
In one embodiment, each index middleware stores the following information for each common component in the component management system: physical address, virtual machine version, cloud environment, component description information. Based on this stored information, the indexing middleware can address the location to the specified common component.
In an embodiment, the component management system further comprises a cloud service compiler deployed at the target foreground application. The target foreground application is configured to: and sending the calling request aiming at the target common component to each service center, and acquiring the compatible target common component through each service center. And compiling and sequencing the compatible target common components according to the service sequence of the target common components by a cloud service compiler of the local foreground to obtain application service for outputting service.
In this embodiment, the target foreground application sends a call request for the target common component to each service center station, so as to obtain a compatible target common component pushed by each service center station.
Specifically, a cloud service compiler is deployed in a target foreground application. The cloud service compiler of the target foreground application is mainly used for compiling the compatible target common component to obtain the application service for outputting the service.
After receiving a service request initiated by a user, a target foreground application determines common components and corresponding service sequences required for responding to the service request. Wherein the common component required to respond to the service request is the target common component.
And then the target foreground application generates a call request aiming at the target common component and sends the call request aiming at the target common component to each service middle station. Each service center station responds to the call request aiming at the target common component and positions the local target common component through the index middleware of the local center station; further performing cloud environment compatibility processing on the local target common component to obtain a compatible target common component; and then pushing the compatible target common component to the target foreground application.
And after the target foreground application obtains the compatible target common components of the corresponding parts from each service center, compiling and sequencing the obtained compatible target common components through a cloud service compiler of the local foreground according to the service sequence of the target common components to obtain application services for outputting the services. The service output by the application service is mainly used for responding to a service request initiated by a user.
It should be noted that, in this embodiment, the service center station that does not store any target common component also receives a call request for the target common component. In this case, after the service center station which does not store any target common component receives the call request for the target common component, the index middleware of the local center station cannot locate the local target common component, and the service center station does not need to push the target common component to the target front station application.
FIG. 2 illustrates a component management interaction diagram according to an embodiment of the present application.
In this embodiment, there are 3 service middlings, which are respectively a service middling station a, a service middling station B, and a service middling station C. Different common components are stored in the common component library of each service center station. The foreground application A and the service center station A are deployed in the same cloud environment. A cloud service compiler is deployed in the foreground application a.
The user initiates a service request to the foreground application a through the channel contact.
The foreground application A determines that the common component a and the common component e are required to respond to the service request according to the service request. The foreground application a requests the service middleboxes to call the common component a and the common component e.
The service center station a locates the common component a stored in the local center station through the indexing middleware of the local center station in response to the received call request. Because the business middle station A and the foreground application A are deployed in the same cloud environment, the business middle station A can directly push the common component a to the foreground application A, so that the foreground application A obtains the compatible common component a.
The service center station B locates, in response to the received call request, the common component e stored in the local center station through the indexing middleware of the local center station. Because the cloud environment of the service center station B is inconsistent with the cloud environment of the foreground application A, the service center station B compiles the public component e through a cloud server compiler of the local center station, so that the compiled public component e is compatible with the cloud environment of the foreground application A, and then the compiled public component e is pushed to the foreground application A, so that the foreground application A obtains the compatible public component e.
The service center station C responds to the received call request, and the index middleware of the local center station locates no public component required by the foreground application A stored in the local center station, so that the service center station C does not push any public component to the foreground application A.
After the foreground application A obtains the compatible common component a and the compatible common component e, the compatible common component a and the compatible common component e are compiled according to the service sequence through a cloud service compiler of the local foreground, and therefore service is provided for the user.
In an embodiment, the component management system further comprises a cloud service compiler deployed at the target foreground application. The target foreground application is configured to: and sending the call request aiming at the target common component to a same-environment service center station in the same cloud environment with the local foreground, and acquiring the compatible target common component through the same-environment service center station. And compiling and sequencing the compatible target common components according to the service sequence of the target common components by a cloud service compiler of the local foreground to obtain application service for outputting service. The co-ambient service middlebox is further configured to: in response to a call request for a target common component, an external target common component of a common component library stored in an external intermediate station is located by the indexing middleware of the local intermediate station. And sending the call request aiming at the external target common component to the heterogeneous environment service central station where the external target common component is positioned.
In this embodiment, the target foreground application sends a call request for the target common component to the same-environment service center station, and then the same-environment service center station sends the call request for the target common component to other different-environment service center stations storing the target common component, and then the target foreground application obtains the compatible target common component pushed by the same-environment service center station and the compatible target common component pushed by the different-environment service center stations.
Specifically, a cloud service compiler is deployed in a target foreground application. The cloud service compiler of the target foreground application is mainly used for compiling the compatible target common component to obtain the application service for outputting the service.
And after receiving the service request initiated by the user, the target foreground application determines the corresponding target common component and the corresponding service sequence. And then the target foreground application generates a call request aiming at the target common component, and then sends the call request aiming at the target common component to the same-environment service middle station. The same-environment service center station refers to a service center station in the same cloud environment as the target foreground application.
After receiving a calling request aiming at a target public component, the same-environment service middle station responds to the calling request aiming at the target public component and positions the local target public component through an index middleware of the local middle station; further performing cloud environment compatibility processing on the local target common component to obtain a compatible target common component; and then pushing the compatible target common component to the target foreground application.
And after receiving the call request aiming at the target public component, the same-environment service middle station responds to the call request aiming at the target public component and also positions the external target public component of the public component library stored in the external middle station through the index middleware of the same-environment service middle station, namely positions the external target public component stored outside the same-environment service middle station. And then the same environment service middle station generates a call request aiming at the external target common component, and sends the call request aiming at the external target common component to the different environment service middle station where the external target common component is positioned.
The external target common component relative to the same environment service middle station is the local target common component relative to the different environment service middle station. Therefore, after receiving the call request aiming at the local target public component, the heterogeneous environment service middle station responds to the call request aiming at the local target public component and positions the local target public component through the index middleware of the local middle station; further carrying out cloud environment compatibility processing on the local target public component to obtain a compatible target public component; and then pushing the compatible target common component to the target foreground application.
Therefore, the target foreground application can obtain the compatible target common component of the corresponding part from the same-environment service center station, and under the forwarding action of the same-environment service center station on the call request, the target foreground application triggers the compatible target common component of the corresponding part pushed by the environment service center station, so as to obtain the compatible target common component of the corresponding part from the different-environment service center station. And the target foreground application compiles and sequences the obtained compatible target common components according to the service sequence of the target common components by a cloud service compiler of the local foreground to obtain application service for outputting service.
The embodiment has the advantages that the calling request is transferred by the service center station in the same environment, the calling request is prevented from being sent to the service center station which does not store the target public component in the component calling process, and the signaling consumption is reduced.
FIG. 3 illustrates a component management interaction diagram according to an embodiment of the present application.
In this embodiment, there are 3 service middlings, which are respectively a service middling station a, a service middling station B, and a service middling station C. Different common components are stored in the common component library of each service center station. The foreground application A and the service center station A are deployed in the same cloud environment, the same-environment service center station of the foreground application A is the service center station A, and the different-environment service center stations are the service center stations B and C. A cloud service compiler is deployed in the foreground application a.
The user initiates a service request to the foreground application a through the channel contact.
The foreground application A determines that the common component a and the common component e are required to respond to the service request according to the service request. Foreground application a requests service station a to call common component a and common component e.
The service center station A responds to the received call request, positions the public component a stored in the local center station through the index middleware of the local center station, and then the service center 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 the service center station A locates the public component e stored in the service center station B through the index middleware of the local center station, and further informs the service center station B that the foreground application A requests to call the public component e.
And the service middle station B responds to the received call request, positions 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 to ensure 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 to ensure that the foreground application A obtains the compatible public component e.
After the foreground application A obtains the compatible common component a and the compatible common component e, the compatible common component a and the compatible common component e are compiled according to the service sequence through a cloud service compiler of the local foreground, and therefore service is provided for the user.
In an embodiment, 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 to: and positioning the target service middle station storing the target common component through the index middleware of the local foreground. And respectively sending the calling requests aiming at the target common components to corresponding target service intermediate stations, and acquiring compatible target common components through the target service intermediate stations. And compiling and sequencing the compatible target common components according to the service sequence of the target common components by a cloud service compiler of the local foreground to obtain application service for outputting service.
In this embodiment, the target foreground application sends a call request for the target common component to the target service center station in which the target common component is stored, so as to obtain a compatible target common component pushed by the target service center station.
Specifically, index middleware and a cloud server compiler are deployed in the target foreground application. The cloud service compiler of the target foreground application is mainly used for compiling the compatible target common component to obtain the application service for outputting the service.
And after receiving the service request initiated by the user, the target foreground application determines the corresponding target common component and the corresponding service sequence. And then the target foreground application generates a call request aiming at the target common component, positions the target service middle station through the index middleware of the local foreground, and then only sends the call request aiming at the target common component to the target service middle station.
After receiving a calling request aiming at a target public component, a target service intermediate station responds to the calling request aiming at the target public component and positions the local target public component through an index middleware of the local intermediate station; further performing cloud environment compatibility processing on the local target common component to obtain a compatible target common component; and then pushing the compatible target common component to the target foreground application.
And after the target foreground application obtains the compatible target common components of the corresponding parts from each target service center, compiling and sequencing the obtained compatible target common components through a cloud service compiler of the local foreground according to the service sequence of the target common components to obtain application services for outputting the services.
The embodiment has the advantages that the index middleware is deployed in the target foreground application, so that the target foreground application can automatically position each target common component, and the selection flexibility of the target foreground application in the process of calling the target common component is improved.
FIG. 4 illustrates a component management interaction diagram according to an embodiment of the present application.
In this embodiment, there are 3 service middlings, which are respectively a service middling station a, a service middling station B, and a service middling station C. Different common components are stored in the common component library of each service center station. The foreground application A and the service center station A are deployed in the same cloud environment. The foreground application A is provided with index middleware and a cloud service compiler.
The user initiates a service request to the foreground application a through the channel contact.
The foreground application A determines that the common component a and the common component e are required to respond to the service request according to the service request. The foreground application a locates the common component a stored in the business platform a and the common component e stored in the business platform B through the indexing middleware of the local foreground. The foreground application then requests the service center station a to call the common component a and the common component e, and requests the service center station B to call the common component a and the common component e.
The service center station A responds to the received call request, positions the public component a stored in the local center station through the index middleware of the local center station, and then the service center 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 the service middle station B responds to the received call request, positions 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 to ensure 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 to ensure that the foreground application A obtains the compatible public component e.
After the foreground application A obtains the compatible common component a and the compatible common component e, the compatible common component a and the compatible common component e are compiled according to the service sequence through a cloud service compiler of the local foreground, and therefore service is provided for the user.
FIG. 5 illustrates a component management interaction diagram according to an embodiment of the present application.
The difference between this embodiment and the embodiment shown in fig. 4 is mainly that, after the foreground application a locates the target common component through the indexing middleware of the local foreground, the foreground application a specifically requests the service foreground storing the target common component to call the corresponding target common component.
Specifically, it is different from the embodiment shown in fig. 4 that the foreground application a requests the service center station a to call the common component a and the common component e, and requests the service center station B to call the common component a and the common component e. In the embodiment shown in fig. 5, the foreground application a requests the service station a to invoke the common component a and requests the service station B to invoke the common component e.
Fig. 6 shows a component management apparatus according to an embodiment of the present application, the apparatus is disposed at each business center station in a component management system, the component management system includes an index middleware deployed at each business center station, a cloud service compiler deployed at each business center station, and a common component library deployed at each business center station, and each business center station is deployed in different cloud environments, the apparatus includes:
a local positioning module 210 configured to position, by an index middleware of a local middle station, a local target common component of a common component library stored in the local middle station in response to a call request for the target common component by a target foreground application;
a first pushing module 220, configured to, if the cloud environment of the local middle station is consistent with the cloud environment of the target foreground application, take 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;
the second pushing module 230 is configured to compile the local target common component into the compatible target common component through a 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.
An electronic device 30 according to an embodiment of the present application is described below with reference to fig. 7. The electronic device 30 shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 7, the electronic device 30 is in the form of a general purpose computing device. The components of the electronic device 30 may include, but are not limited to: the at least one processing unit 310, the at least one memory unit 320, and a bus 330 that couples various system components including the memory unit 320 and the processing unit 310.
Wherein the storage unit stores program code executable by the processing unit 310 to cause the processing unit 310 to perform steps according to various exemplary embodiments of the present invention described in the description part of the above exemplary methods of the present specification. For example, the processing unit 310 may perform the various steps as shown in fig. 1.
The storage unit 320 may include readable media in the form of volatile storage units, 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.
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 thereof, may comprise an implementation of a network environment.
Bus 330 may be 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.
The electronic device 30 may also communicate with one or more external devices 400 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 30, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 30 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 350. An input/output (I/O) interface 350 is connected to the display unit 340. Also, the electronic device 30 may 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 the network adapter 360. As shown, the network adapter 360 communicates with the other modules of the electronic device 30 via the bus 330. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with 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, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments 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 disk, a removable hard disk, etc.) or on a network, and includes several instructions to make a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) execute the method according to the embodiments of the present application.
In an exemplary embodiment of the present application, there is also provided a computer-readable storage medium having stored thereon computer-readable instructions which, when executed by a processor of a computer, cause the computer to perform the method described in the above method embodiment section.
According to an embodiment of the present application, there is also provided a program product for implementing the method in the above method embodiment, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a 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.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A 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 (a non-exhaustive list) of the readable storage medium include: an electrical connection having 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with 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 readable signal medium may also be any readable medium that is not a 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 readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as JAVA, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the 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 kind 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).
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods herein are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments 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 disk, a removable 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 embodiments of the present application.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

Claims (9)

1.一种组件管理系统，其特征在于，所述组件管理系统包括部署于各业务中台的公用组件库，部署于各业务中台的索引中间件，部署于各业务中台的云服务编译器，各业务中台分别部署于不同的云环境，各业务中台配置为：1. A component management system, characterized in that the component management system comprises a public component library deployed in each business middle platform, an index middleware deployed in each business middle platform, and a cloud service compilation deployed in each business middle platform Each business middle station is deployed in different cloud environments, and the configuration of each business middle station is as follows: 响应于目标前台应用针对目标公用组件的调用请求，通过本地中台的索引中间件定位存储于本地中台的公用组件库的本地目标公用组件；In response to the calling request of the target foreground application for the target public component, locate the local target public component stored in the public component library of the local middle platform through the index middleware of the local middle platform; 若本地中台的云环境与所述目标前台应用的云环境一致，则将所述本地目标公用组件作为适用于所述目标前台应用的云环境的兼容目标公用组件，并将所述兼容目标公用组件推送至所述目标前台应用；If the cloud environment of the local middle station 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 used as a compatible target public component. The 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 compiled into the compatible target public component. The target public component is pushed to the target foreground application. 2.根据权利要求1所述的组件管理系统，其特征在于，所述组件管理系统还包括部署于所述目标前台应用的云服务编译器，所述目标前台应用配置为：2. The component management system according to claim 1, wherein the component management system further comprises a cloud service compiler deployed in the target foreground application, and the target foreground application is configured as: 将针对所述目标公用组件的调用请求发送至各业务中台，并通过各业务中台获取所述兼容目标公用组件；sending the invocation request for the target public component to each business middle station, and obtaining the compatible target public component through each business middle station; 通过本地前台的云服务编译器，按照所述目标公用组件的服务序列对所述兼容目标公用组件进行编译以及排序，得到用于输出服务的应用服务。Compiling and sorting the compatible target public components according to the service sequence of the target public components through the cloud service compiler in the local foreground, to obtain application services for outputting services. 3.根据权利要求1所述的组件管理系统，其特征在于，所述组件管理系统还包括部署于所述目标前台应用的云服务编译器，所述目标前台应用配置为：3. The component management system according to claim 1, wherein the component management system further comprises a cloud service compiler deployed in the target foreground application, and the target foreground application is configured as: 将针对所述目标公用组件的调用请求发送至与本地前台处于同一云环境的同环境业务中台，通过所述同环境业务中台获取所述兼容目标公用组件；Sending a call request for the target public component to the same-environment service middle station that is in the same cloud environment as the local foreground, and obtains the compatible target public component through the same-environment service middle station; 通过本地前台的云服务编译器，按照所述目标公用组件的服务序列对所述兼容目标公用组件进行编译以及排序，得到用于输出服务的应用服务；Compiling and sorting the compatible target public components according to the service sequence of the target public components through the cloud service compiler in the local foreground, to obtain application services for outputting services; 所述同环境业务中台还配置为：The same-environment service middle-end is also configured as: 响应于针对所述目标公用组件的调用请求，通过本地中台的索引中间件定位存储于外部中台的公用组件库的外部目标公用组件；In response to the calling request for the target public component, locate the external target public component stored in the public component library of the external middle platform through the index middleware of the local middle platform; 将针对所述外部目标公用组件的调用请求发送至所述外部目标公用组件所在的异环境业务中台。The calling request for the external target public component is sent to the different environment service center where the external target public component is located. 4.根据权利要求1所述的组件管理系统，其特征在于，所述组件管理系统还包括部署于所述目标前台应用的索引中间件，部署于所述目标前台应用的云服务编译器，所述目标前台应用配置为：4. The component management system according to claim 1, wherein the component management system further comprises an index middleware deployed in the target foreground application, a cloud service compiler deployed in the target foreground application, and the The target foreground application is configured as: 通过本地前台的索引中间件定位存储有所述目标公用组件的目标业务中台；Locate the target business middle station storing the target public component through the index middleware of the local foreground; 将针对所述目标公用组件的调用请求分别发送至对应的目标业务中台，并通过所述目标业务中台获取所述兼容目标公用组件；Send the invocation request for the target public component to the corresponding target service middle station respectively, and obtain the compatible target public component through the target service middle station; 通过本地前台的云服务编译器，按照所述目标公用组件的服务序列对所述兼容目标公用组件进行编译以及排序，得到用于输出服务的应用服务。Compiling and sorting the compatible target public components according to the service sequence of the target public components through the cloud service compiler in the local foreground, to obtain application services for outputting services. 5.根据权利要求1或4所述的组件管理系统，其特征在于，各索引中间件存储有所述组件管理系统中各公用组件的以下信息：物理地址、虚拟机版本、云环境、组件描述信息。5. The component management system according to claim 1 or 4, wherein 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. 6.一种组件管理方法，其特征在于，所述方法应用于组件管理系统中的各业务中台，所述组件管理系统包括部署于各业务中台的索引中间件，部署于各业务中台的云服务编译器，部署于各业务中台的公用组件库，各业务中台分别部署于不同的云环境，所述方法包括：6. A component management method, characterized in that the method is applied to each service middle-end in a component management system, and the component management system comprises index middleware deployed in each business middle-end, deployed in each business middle-end The cloud service compiler is deployed in the public component library of each business middle platform, and each business middle platform is respectively deployed in different cloud environments, and the method includes: 响应于目标前台应用针对目标公用组件的调用请求，通过本地中台的索引中间件定位存储于本地中台的公用组件库的本地目标公用组件；In response to the calling request of the target foreground application for the target public component, locate the local target public component stored in the public component library of the local middle platform through the index middleware of the local middle platform; 若本地中台的云环境与所述目标前台应用的云环境一致，则将所述本地目标公用组件作为适用于所述目标前台应用的云环境的兼容目标公用组件，并将所述兼容目标公用组件推送至所述目标前台应用；If the cloud environment of the local middle station 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 used as a compatible target public component. The component is pushed to the target foreground application; 若本地中台的云环境与所述目标前台应用的云环境相异，则通过本地中台的云服务编译器将所述本地目标公用组件编译为所述兼容目标公用组件，并将所述兼容目标公用组件推送至所述目标前台应用。If the cloud environment of the local middle platform 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 platform, and the compatible target public component is compiled into the compatible target public component. The target public component is pushed to the target foreground application. 7.一种组件管理装置，其特征在于，所述装置设于组件管理系统中的各业务中台，所述组件管理系统包括部署于各业务中台的索引中间件，部署于各业务中台的云服务编译器，部署于各业务中台的公用组件库，各业务中台分别部署于不同的云环境，所述装置包括：7. A component management device, characterized in that the device is installed in each service middle station in a component management system, and the component management system includes an index middleware deployed in each service middle station, and is deployed in each service middle station The cloud service compiler is deployed in the public component library of each business middle platform, and each business middle platform is respectively deployed in different cloud environments, and the device includes: 本地定位模块，配置为响应于目标前台应用针对目标公用组件的调用请求，通过本地中台的索引中间件定位存储于本地中台的公用组件库的本地目标公用组件；The local positioning module is configured to locate the local target public component stored in the public component library of the local middle platform through the index middleware of the local middle platform in response to the calling request of the target foreground application for the target public component; 第一推送模块，配置为若本地中台的云环境与所述目标前台应用的云环境一致，则将所述本地目标公用组件作为适用于所述目标前台应用的云环境的兼容目标公用组件，并将所述兼容目标公用组件推送至所述目标前台应用；a first push module, configured to use the local target public component as a compatible target public component applicable to the cloud environment of the target foreground application if the cloud environment of the local middle platform is consistent with 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 public component into the compatible target public component through the cloud service compiler of the local middle platform if the cloud environment of the local middle platform is different from the cloud environment of the target foreground application component, and push the compatible target public component to the target foreground application. 8.一种电子设备，其特征在于，包括：8. An electronic device, characterized in that, comprising: 存储器，存储有计算机可读指令；a memory storing computer-readable instructions; 处理器，读取存储器存储的计算机可读指令，以执行权利要求1-6中的任一个所述的方法。A processor reading computer readable instructions stored in the memory to perform the method of any of claims 1-6. 9.一种计算机可读存储介质，其特征在于，其上存储有计算机可读指令，当所述计算机可读指令被计算机的处理器执行时，使计算机执行权利要求1-6中的任一个所述的方法。9. A computer-readable storage medium, wherein a computer-readable instruction is stored thereon, and when the computer-readable instruction is executed by a processor of the computer, the computer is made to execute any one of claims 1-6 the method described.
CN202111552624.0A 2021-12-17 2021-12-17 Component management system, method, device, electronic device and storage medium Active CN114237684B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111552624.0A CN114237684B (en) 2021-12-17 2021-12-17 Component management system, method, device, electronic device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111552624.0A CN114237684B (en) 2021-12-17 2021-12-17 Component management system, method, device, electronic device and storage medium

Publications (2)

Publication Number Publication Date
CN114237684A true CN114237684A (en) 2022-03-25
CN114237684B CN114237684B (en) 2024-12-27

Family

ID=80758029

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111552624.0A Active CN114237684B (en) 2021-12-17 2021-12-17 Component management system, method, device, electronic device and storage medium

Country Status (1)

Country Link
CN (1) CN114237684B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114936050A (en) * 2022-05-25 2022-08-23 北京百度网讯科技有限公司 Access request processing method and device, electronic equipment and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150347542A1 (en) * 2010-07-09 2015-12-03 State Street Corporation Systems and Methods for Data Warehousing in Private Cloud Environment
US9569249B1 (en) * 2015-09-08 2017-02-14 International Business Machines Corporation Pattern design for heterogeneous environments
CN111506297A (en) * 2020-05-30 2020-08-07 内蒙古电力(集团)有限责任公司内蒙古电力科学研究院分公司 Mobile top layer design system
CN111736827A (en) * 2020-08-25 2020-10-02 长沙慧码至一信息科技有限公司 Cloud native development component system
CN114661493A (en) * 2022-03-21 2022-06-24 深圳市远行科技股份有限公司 A component cloud calling method and system based on microservice architecture

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150347542A1 (en) * 2010-07-09 2015-12-03 State Street Corporation Systems and Methods for Data Warehousing in Private Cloud Environment
US9569249B1 (en) * 2015-09-08 2017-02-14 International Business Machines Corporation Pattern design for heterogeneous environments
CN111506297A (en) * 2020-05-30 2020-08-07 内蒙古电力(集团)有限责任公司内蒙古电力科学研究院分公司 Mobile top layer design system
CN111736827A (en) * 2020-08-25 2020-10-02 长沙慧码至一信息科技有限公司 Cloud native development component system
CN114661493A (en) * 2022-03-21 2022-06-24 深圳市远行科技股份有限公司 A component cloud calling method and system based on microservice architecture

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114936050A (en) * 2022-05-25 2022-08-23 北京百度网讯科技有限公司 Access request processing method and device, electronic equipment and storage medium
CN114936050B (en) * 2022-05-25 2023-12-01 北京百度网讯科技有限公司 Access request processing method and device, electronic equipment and storage medium

Also Published As

Publication number Publication date
CN114237684B (en) 2024-12-27

Similar Documents

Publication Publication Date Title
US11556348B2 (en) Bootstrapping profile-guided compilation and verification
CN110389786B (en) Kernel management method, electronic device and computer-readable storage medium
CN110688096B (en) Method and device for constructing application program containing plug-in, medium and electronic equipment
CN111324441A (en) Operating environment switching method and device, computer equipment and storage medium
CN110221840B (en) Function implementation method and device of application program, equipment and storage medium
CN113407165B (en) SDK generation and self-upgrade method, device, readable medium and equipment
CN113127134A (en) Container cluster, multi-tenant deployment method based on container cluster and electronic equipment
CN110058861B (en) Source code processing method and device, storage medium and electronic equipment
CN113778477B (en) File processing method and device, computer readable storage medium and electronic equipment
CN109669787B (en) Data transmission method and device, storage medium and electronic equipment
CN109218393B (en) Push implementation method, device, equipment and computer storage medium
CN113986402A (en) Function calling method and device, electronic equipment and storage medium
CN114237684A (en) Component management system, method, apparatus, electronic device, and storage medium
CN109343970B (en) Application program-based operation method and device, electronic equipment and computer medium
CN114301789B (en) Data transmission method and device, storage medium and electronic equipment
CN106843895B (en) Method, system and readable storage medium for processing requests
CN109669715A (en) application program dynamic updating method, device and storage medium
CN111885194B (en) Communication method and device for communication application and electronic equipment
CN109189591A (en) Method and apparatus for calling application component
CN115552369B (en) Compilation method, compilation device, compilation system, storage medium and electronic device
CN111897887B (en) Parameter configuration method, device, system, electronic equipment and storage medium
CN110661852B (en) Service processing method and device in cloud environment
CN112711602B (en) Method and device for running stored procedure, database system and storage medium
CN113992759A (en) Joint analysis device and method applied to local area network and electronic equipment
US20240330016A1 (en) Class file processing method and apparatus, device, medium, and product

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant