CN114780080A - Micro front end integration method, device and monitoring method - Google Patents
Micro front end integration method, device and monitoring method Download PDFInfo
- Publication number
- CN114780080A CN114780080A CN202210450768.3A CN202210450768A CN114780080A CN 114780080 A CN114780080 A CN 114780080A CN 202210450768 A CN202210450768 A CN 202210450768A CN 114780080 A CN114780080 A CN 114780080A
- Authority
- CN
- China
- Prior art keywords
- application
- sub
- main application
- main
- applications
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
Abstract
The present disclosure relates to the field of finance, and in particular, to a micro front end integration method, apparatus, and monitoring method. The method comprises determining a primary application function according to a business requirement; determining a sub-application realizing the main application function from a preset sub-application set; generating a configuration file of the main application according to the main application function and the determined sub-application; and generating and displaying the topological structures of the main application and the sub-applications according to the configuration file. According to the scheme, online application is quickly and stably integrated through a visual configuration interface, and the development and production time of the main application is reduced; moreover, hot updating can be realized without production, human errors are reduced, and positioning errors are facilitated.
Description
Technical Field
The present disclosure relates to the field of finance, and in particular, to a micro front end integration method, device and monitoring method.
Background
With the continuous development of business requirements of large enterprises such as banks and the like, the integrated functions of the application system are more and more complex, the number of sub-applications is more and more, and the calling relationship among the applications is more and more complex.
Taking a general item application as an example, the application item involves dozens of sub-applications, and a large number of sub-applications (such as a loan module and a rating module) need to be integrated into multiple application systems and multiple channel terminals, and the combination manner thereof becomes increasingly complex.
Most application systems in the prior art adopt a micro front end design mode, sub-applications realize independent service functions, and a main application integrates the sub-applications according to requirements to establish a determined mapping relation between a route and the sub-applications. However, the mapping relationship is maintained in the program code of the main application, and each time the main application version is generated, the main application version needs to be validated through one batch of production, so that the maintenance cost is extremely high. In addition, the arrangement sub-application is repeated, the arrangement rule is often determined before production, and errors are easily caused when the arrangement work is carried out manually. In addition, as the business system becomes more complex, the calling relationship between the main application and the sub-application is complex, and the problem is extremely difficult to troubleshoot.
Aiming at the problems that the relation between a sub-application and an application system cannot be directly known and the investigation and calling relation is complex in the prior art, a micro front end integration method, a micro front end integration device and a micro front end monitoring method are needed.
Disclosure of Invention
To solve the above-mentioned problems of the prior art, embodiments herein provide a micro front end integration method, apparatus, monitoring method, computer device, storage medium, and computer program product.
The embodiment of the present disclosure provides a micro front end integration method, which is applied to a micro front end application system, and includes: determining a main application function according to the service requirement; determining a sub-application realizing the main application function from a preset sub-application set; generating a configuration file of the main application according to the main application function and the determined sub-application; and generating and displaying the topological structures of the main application and the sub-applications according to the configuration file.
According to one aspect of embodiments herein, generating a configuration file for a primary application according to the primary application function and the determined sub-applications comprises: and generating the configuration file according to the name of the main application, the field related to the sub-application and the routing relation between the main application and the sub-application, wherein the field related to the sub-application comprises the name of the sub-application, the application identifier of the sub-application and the entry file of the sub-application.
According to one aspect of embodiments herein, the method further comprises: determining an application scene to be launched by a main application according to a service requirement; determining an application template of the main application according to the application scene to be launched by the main application; and generating the main application according to the application template of the main application and the configuration file.
According to one aspect of embodiments herein, the method further comprises: and when the service requirement is changed, updating the main application by changing the configuration file of the main application.
According to one aspect of embodiments herein, updating the master application comprises: when the service requirement is that a main application function is newly added, adding a field related to a sub-application for realizing the main application function to be newly added in a configuration file of the main application; and when the service requirement is to delete one of the main application functions, eliminating fields related to the sub-applications for realizing the main application function to be deleted from the configuration file of the main application.
According to one aspect of embodiments herein, the determining an application template for the master application comprises: and selecting an application template of the main application according to any one of the running channel, the container, the layout, the language and the third-party plug-in of the main application.
The embodiment herein further provides a micro front end monitoring method, which performs the following steps by using the topology structure of the main application and the sub-application, including: and determining a main application having a routing relation with the sub-application from the topological structure according to the alarm information of the sub-application, and controlling the sub-application in the main application to suspend.
According to one aspect of embodiments herein, the method further comprises: when a plurality of main applications generate alarm information at the same time, whether the same sub-application corresponding to the main applications has faults or not is preferentially determined according to the topological structure.
Embodiments herein also provide a micro front end integrated device, the device comprising: a main application function determining unit, configured to determine a main application function according to a service requirement; the sub-application determining unit is used for determining the sub-application realizing the main application function from a preset sub-application set; the configuration file generating unit is used for generating a configuration file of the main application according to the main application function and the determined sub-application; and the topological structure generating unit is used for generating and displaying the topological structures of the main application and the sub-applications according to the configuration file.
Embodiments herein also provide a computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the micro front end integration method when executing the computer program.
Embodiments herein also provide a computer-readable storage medium storing a computer program which, when executed by a processor, implements the micro front-end integration method.
Embodiments herein also provide a computer program product comprising a computer program which, when executed by a processor, implements the micro front-end integration method.
According to the scheme, online application is quickly and stably integrated through a visual configuration interface, and the development and production time of the main application is reduced; moreover, hot updating can be realized without production, human errors are reduced, and positioning errors are facilitated.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the embodiments or technical solutions in the prior art are briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a flow chart illustrating a micro front end integration method according to an embodiment herein;
FIG. 2 is a flow diagram illustrating a method for generating a master application according to an embodiment of the disclosure;
FIG. 3 is a flow diagram illustrating a method for updating a primary application according to an embodiment of the disclosure;
FIG. 4 is a schematic diagram of a micro-front end integrated device according to an embodiment of the present disclosure;
FIG. 5 is a schematic diagram illustrating an embodiment of a micro front end integrated device;
FIG. 6 is a schematic diagram illustrating a topology of a primary application and a secondary application according to an embodiment herein;
FIG. 7 is a diagram illustrating a set of sub-applications according to an embodiment herein;
fig. 8 is a schematic structural diagram of a computer device according to an embodiment of the present disclosure.
Description of the figures the symbols:
401. a master application function determining unit;
4011. a service requirement acquisition unit;
402. a sub-application determining unit;
4021. a sub-application set presetting module;
403. a configuration file generating unit;
4031. a new module is changed by the configuration file;
404. a topology generating unit;
4041. a display unit;
701. a set of sub-applications;
802. a computer device;
804. a processor;
806. a memory;
808. a drive mechanism;
810. an input/output module;
812. an input device;
814. an output device;
816. a presentation device;
818. a graphical user interface;
820. a network interface;
822. a communication link;
824. a communication bus.
Detailed Description
In order to make the technical solutions in the present specification better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments, but not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments herein without making any creative effort, shall fall within the scope of protection.
It should be noted that the terms "first," "second," and the like in the description and claims herein and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments herein described are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or device.
The present specification provides method steps as described in the examples or flowcharts, but may include more or fewer steps based on routine or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of sequences, and does not represent a unique order of performance. In the actual implementation of the system or the device product, the method according to the embodiments or shown in the drawings can be executed in sequence or in parallel.
It should be noted that the micro front end integration method can be used in the financial field and the distributed architecture field, and the application field of the micro front end integration method and the micro front end integration device is not limited herein.
The micro front end is a method for achieving engineering splitting treatment by using component splitting. By code multiplexing, the problems of engineering expansion, difficult development and maintenance and the like can be solved.
Fig. 1 is a flowchart of a micro front end integration method according to an embodiment of the present disclosure, which specifically includes the following steps:
In some embodiments of the present description, the master application is responsible for application registration, route resolution, and other responsibilities associated with aspects of sub-application integration, etc. And determining the function of the main application according to the service requirement. For example, if the business requirement is to develop a web page with financial services and loan marketing, it may be determined that the primary application functionality needs to include financial services and loan marketing.
And 102, determining the sub-application realizing the main application function from a preset sub-application set. In this step, the sub-applications are independent Vue single-page applications divided according to functions or scenes, and each sub-application can implement a specific service function and has an independent ID. Development and deployment of each sub-application are independent, and functions are independent. As shown in fig. 7, content management, user management, loan marketing, financial services, and enterprise social are 5 sub-applications, and are independent in function and deployed on different servers. In this step, a plurality of sub-applications with different business functions form a sub-application set, and the sub-application set may also be a sub-application resource pool. The content management, user management, loan marketing, financial services, enterprise social in fig. 7 is a 5 sub-application travel sub-application set. The sub-application set/sub-application resource pool may be pre-configured. For example, the set of sub-applications includes a user management sub-application, a content management sub-application, a loan marketing sub-application, a financial services sub-application, and a business social sub-application, among others.
According to the main application function determined in step 101, the sub-applications capable of realizing the main application function are inquired from the sub-application set/sub-application resource pool. For example, the primary application functions are: and financial service and loan marketing, namely finding a financial service sub-application and a loan marketing sub-application from the sub-application set/sub-application resource pool.
In this step, one main application may have a plurality of sub-applications corresponding to its functions. Meanwhile, one sub-application may implement the same function of a plurality of main applications. Thus, multiple master applications may share the same sub-application to achieve the same partial functionality.
And 103, generating a configuration file of the main application according to the main application function and the determined sub-application. In some embodiments of the present description, a configuration file for a primary application includes primary application-related fields, sub-application-related fields that enable functionality of the primary application, and routing relationships between the primary application and corresponding sub-applications. Specifically, the configuration file is generated according to a name of a main application, a field related to the sub-application, and a routing relationship between the main application and the sub-application, where the field related to the sub-application includes the name of the sub-application, an application identifier of the sub-application, and the entry file of the sub-application.
An example of a profile for a host application is as follows:
the projectame represents the name of the main application as 'main 1', the modulesList represents the sub-application list for realizing the main application function, and the sub-application list comprises the name and the ID of the sub-application for realizing the main application function, the routing relation path between the sub-application and the main application and the entry file 'entry' of each sub-application.
In this step, the configuration file of the main application may represent a mapping relationship between the main application and the sub-application. The configuration file is automatically generated through scripts. Further, the configuration file may be changed to modify the primary application according to changes in business requirements.
And 104, generating and displaying the topological structures of the main application and the sub-applications according to the configuration file. In some embodiments of the present specification, the topology result of the main application and the sub-application may be generated according to the main application name, the sub-application name and the routing relationship of the main application and the sub-application in the configuration file. The step also comprises the step of sending the topological result to a display interface for visual display. The topology structure can be changed according to the change of the service requirement.
The step also comprises the step of sending the topological results between the main applications and the sub applications generated by the configuration files to a display interface for displaying.
Fig. 2 is a flowchart illustrating a method for generating a master application according to an embodiment of the disclosure. The method specifically comprises the following steps:
Fig. 3 is a flowchart illustrating a method for updating a master application according to an embodiment of the present disclosure. As described above, when the service requirement changes, the configuration file of the primary application is changed to update the primary application. The method specifically comprises the following steps:
The application also comprises a micro front end monitoring method, which executes the following steps by using a topological structure generated by the main application and the sub-applications: and determining a main application having a routing relation with the sub-application from the topological structure according to the alarm information of the sub-application, and controlling the sub-application in the main application to suspend. In some embodiments of the present specification, it may be found that the sub-application has a failure in alarm information according to the monitoring log of the sub-application, and then the main application having a routing relationship with the sub-application having the alarm may be searched from the topology results of the main application and the sub-application, and by modifying a field related to the sub-application having the alarm in the configuration file of the main application, the sub-application in the main application is controlled to suspend running, and the configuration file of the main application is updated. Correspondingly, the topology structure on the display page is updated. Specifically, by adding an availability field 'available' in the configuration file of the main application, the suspended use or normal use of the sub application which generates the alarm is controlled by setting the parameter of the availability field. The details are as follows:
the main application comprises two sub-application components, namely 'sub 1' and 'sub 2'. Wherein, the availability field of 'sub 1' is: available is false; the availability fields for 'sub 2' are: true respectively, indicating that the sub application 'sub 1' is suspended from running and the sub application 'sub 2' is normally used.
In some embodiments of the present description, the micro-front end control method further comprises: when the alarm information occurs to a plurality of main applications at the same time, whether the same sub-application corresponding to the main applications fails or not is preferentially determined according to the topological structure. When a certain main application fails, alarm information is generated, and the failure causes include but are not limited to: the main application may be down, the third-party system introduced by the main application is abnormal, and the sub-application of the main application is in failure.
Therefore, the plurality of sub-applications that implement the main application each have a certain probability of failure. As described above, when two or more main applications have the same function and use the same sub-application to implement some of the functions of the main application, if two or more main applications fail to generate alarm information, the probability of failure of the same sub-application is higher than the probability of failure of other single sub-applications. And determining the sub-application common to the two or more main applications according to the topological structures of the main application and the sub-applications, and preferably checking whether the common sub-application has a problem. For example, the main application 1 includes 2 sub-applications of financial services, marketing of loans; the main application 2 includes 3 sub-applications for content approval, loan marketing, and user management. The master application 1 has the same sub-applications as the master application 2: and (4) loan marketing. When the main application 1 and the main application 2 simultaneously fail to generate alarm information, the mapping relation of the main application 1, the main application 2 and the sub-applications thereof can be obtained according to the topological structure, and further, the probability that the common sub-application fails is determined to be relatively higher according to the common sub-application of the 2 main applications. Therefore, when troubleshooting, the operation and maintenance personnel preferably troubleshoot whether the common sub-application fails.
Fig. 4 is a schematic structural diagram of a micro front end integrated device according to an embodiment of the present disclosure, in which a basic structure is described, where functional units and modules may be implemented in a software manner, or implemented by a general chip or a specific chip to implement a micro front end integrated service, where the device specifically includes:
a primary application function determining unit 401, configured to determine a primary application function according to a service requirement;
a sub-application determining unit 402, configured to determine a sub-application that implements the main application function from a preset set of sub-applications;
a configuration file generating unit 403, configured to generate a configuration file of a main application according to the main application function and the determined sub-application;
a topology generating unit 404, configured to generate and display a topology of the main application and the sub-application according to the configuration file.
According to the scheme, online application is quickly and stably integrated through a visual configuration interface, and the development and production time of the main application is reduced; moreover, hot updating can be realized without production, human errors are reduced, and positioning errors are facilitated.
As an embodiment herein, reference may also be made to fig. 5, which is a schematic structural diagram of the apparatus in this embodiment.
As an embodiment herein, the master application function determining unit 401 further includes:
a service requirement obtaining unit 4011, configured to obtain a service requirement;
as an embodiment herein, the sub application determining unit 402 further includes:
a sub-application set presetting module 4021, configured to preset a sub-application set;
as an embodiment herein, the configuration file generating unit 403 further includes:
a new configuration file change module 4031, configured to change the configuration file of the primary application according to the change of the service requirement.
As an embodiment herein, the topology generation unit 404 further includes:
the display unit 4041 is configured to send the topology structure to a display interface for displaying.
Fig. 6 is a schematic diagram illustrating a topology of a main application and a sub-application according to an embodiment of the present disclosure. As shown, the micro front-end application system includes two main applications, main application 1 and main application 2. The main application 1 corresponds to three sub-applications, which are respectively: sub-application 1, sub-application 2, and sub-application 4; the main application 2 corresponds to 3 sub-applications, respectively: sub-application 3, sub-application 5, and sub-application 6.
Fig. 7 is a diagram illustrating a set of sub-applications according to an embodiment herein. The sub-application set 701 includes a plurality of sub-applications, which are respectively: the system comprises a user management sub-application, a content auditing sub-application, a loan marketing sub-application, a financial service sub-application and an enterprise social sub-application.
As shown in fig. 8, for a computer device provided for embodiments herein, the computer device 802 may include one or more processors 804, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 802 may also include any memory 806 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 806 may include any one or combination of the following: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 802. In one case, when the processor 804 executes the associated instructions, which are stored in any memory or combination of memories, the computer device 802 can perform any of the operations of the associated instructions. The computer device 802 also includes one or more drive mechanisms 808, such as a hard disk drive mechanism, an optical disk drive mechanism, etc., for interacting with any memory.
Corresponding to the methods in fig. 1 to 3, the embodiments herein also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the steps of the above-mentioned method.
Embodiments herein also provide computer readable instructions, wherein a program therein causes a processor to perform the method as shown in fig. 1-3 when the instructions are executed by the processor.
Embodiments herein also provide a computer program product comprising a computer program which, when executed by a processor, implements the method illustrated in fig. 1 to 3.
It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.
It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical functional division, and other divisions may be realized in practice, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on multiple network units. Some or all of the elements may be selected according to actual needs to achieve the objectives of the embodiments herein.
In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.
The principles and embodiments of this document are explained herein using specific examples, which are presented only to aid in understanding the methods and their core concepts; meanwhile, for the general technical personnel in the field, according to the idea of this document, there may be changes in the concrete implementation and the application scope, in summary, this description should not be understood as the limitation of this document.
Claims (12)
1. A micro front-end integration method is applied to a micro front-end application system and comprises the following steps:
determining a main application function according to the service requirement;
determining a sub-application for realizing the main application function from a preset sub-application set;
generating a configuration file of the main application according to the main application function and the determined sub-application;
and generating and displaying the topological structures of the main application and the sub-applications according to the configuration file.
2. The micro front-end integration method of claim 1, wherein generating a configuration file for a master application based on the master application functionality and the determined sub-applications comprises:
and generating the configuration file according to the name of the main application, the fields related to the sub-applications and the routing relationship between the main application and the sub-applications, wherein the fields related to the sub-applications comprise the names of the sub-applications, the application identifications of the sub-applications and the entry files of the sub-applications.
3. The micro front-end integration method of claim 2, further comprising:
determining an application scene to be launched by a main application according to a service requirement;
determining an application template of the main application according to the application scene to be launched of the main application;
and generating the master application according to the application template of the master application and the configuration file.
4. The micro front-end integration method of claim 3, further comprising: and when the service requirement is changed, updating the main application by changing the configuration file of the main application.
5. The micro front-end integration method of claim 4, wherein updating the master application comprises:
when the service requirement is that a main application function is newly added, adding a field related to a sub-application for realizing the main application function to be newly added into a configuration file of the main application;
and when the service requirement is to delete one of the main application functions, eliminating fields related to the sub-applications for realizing the main application function to be deleted from the configuration file of the main application.
6. The micro front-end integration method of claim 5, wherein the determining an application template for a master application comprises: and selecting an application template of the main application according to any one of the running channel, the container, the layout, the language and the third-party plug-in of the main application.
7. A micro front-end monitoring method, characterized in that the method performs the following steps using the topology of any of claims 1-6, comprising:
and determining a main application having a routing relation with the sub-application from the topological structure according to the alarm information of the sub-application, and controlling the sub-application in the main application to suspend.
8. The micro front-end monitoring method of claim 7, the method further comprising:
when the alarm information occurs to a plurality of main applications at the same time, whether the same sub-application corresponding to the main applications fails or not is preferentially determined according to the topological structure.
9. A micro-front end integrated device, the device comprising:
a main application function determining unit, configured to determine a main application function according to a service requirement;
the sub-application determining unit is used for determining the sub-application realizing the main application function from a preset sub-application set;
the configuration file generating unit is used for generating a configuration file of the main application according to the main application function and the determined sub-application;
and the topological structure generating unit is used for generating and displaying the topological structures of the main application and the sub-applications according to the configuration file.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any one of claims 1 to 8 when executing the computer program.
11. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1 to 8.
12. A computer program product, characterized in that the computer program product comprises a computer program which, when being executed by a processor, carries out the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210450768.3A CN114780080A (en) | 2022-04-27 | 2022-04-27 | Micro front end integration method, device and monitoring method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210450768.3A CN114780080A (en) | 2022-04-27 | 2022-04-27 | Micro front end integration method, device and monitoring method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114780080A true CN114780080A (en) | 2022-07-22 |
Family
ID=82432876
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210450768.3A Pending CN114780080A (en) | 2022-04-27 | 2022-04-27 | Micro front end integration method, device and monitoring method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114780080A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113535160A (en) * | 2021-07-13 | 2021-10-22 | 杭州安恒信息技术股份有限公司 | Application module multiplexing method, device, system, electronic device and storage medium |
| CN115277637A (en) * | 2022-09-26 | 2022-11-01 | 中企云链（北京）金融信息服务有限公司 | Multi-domain name item management platform based on micro front-end architecture and high aggregation deployment method |
| CN115562889A (en) * | 2022-10-12 | 2023-01-03 | 中航信移动科技有限公司 | Application control method, electronic device and storage medium |
| CN115857891A (en) * | 2022-11-17 | 2023-03-28 | 北京百度网讯科技有限公司 | Front-end application program generation method and device, electronic equipment and storage medium |
| CN116662123A (en) * | 2023-08-01 | 2023-08-29 | 苏州浪潮智能科技有限公司 | Method and device for monitoring server component, electronic equipment and storage medium |
-
2022
- 2022-04-27 CN CN202210450768.3A patent/CN114780080A/en active Pending
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113535160A (en) * | 2021-07-13 | 2021-10-22 | 杭州安恒信息技术股份有限公司 | Application module multiplexing method, device, system, electronic device and storage medium |
| CN113535160B (en) * | 2021-07-13 | 2024-03-26 | 杭州安恒信息技术股份有限公司 | Method, device, system, electronic device and storage medium for multiplexing application modules |
| CN115277637A (en) * | 2022-09-26 | 2022-11-01 | 中企云链（北京）金融信息服务有限公司 | Multi-domain name item management platform based on micro front-end architecture and high aggregation deployment method |
| CN115277637B (en) * | 2022-09-26 | 2023-01-13 | 中企云链（北京）金融信息服务有限公司 | Multi-domain name item management platform based on micro front-end architecture and high aggregation deployment method |
| CN115562889A (en) * | 2022-10-12 | 2023-01-03 | 中航信移动科技有限公司 | Application control method, electronic device and storage medium |
| CN115562889B (en) * | 2022-10-12 | 2024-01-23 | 中航信移动科技有限公司 | Application control method, electronic equipment and storage medium |
| CN115857891A (en) * | 2022-11-17 | 2023-03-28 | 北京百度网讯科技有限公司 | Front-end application program generation method and device, electronic equipment and storage medium |
| CN116662123A (en) * | 2023-08-01 | 2023-08-29 | 苏州浪潮智能科技有限公司 | Method and device for monitoring server component, electronic equipment and storage medium |
| CN116662123B (en) * | 2023-08-01 | 2023-11-17 | 苏州浪潮智能科技有限公司 | Method and device for monitoring server component, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114780080A (en) | Micro front end integration method, device and monitoring method | |
| CN112118565B (en) | Multi-tenant service gray level publishing method, device, computer equipment and storage medium | |
| US11269660B2 (en) | Methods and systems for integrated development environment editor support with a single code base | |
| US20180101371A1 (en) | Deployment manager | |
| CN107896162B (en) | Deployment method and device of monitoring system, computer equipment and storage medium | |
| US20170161059A1 (en) | Management of multiple application programming interface versions for development environments | |
| CN110096424B (en) | Test processing method and device, electronic equipment and storage medium | |
| US10817267B2 (en) | State machine representation of a development environment deployment process | |
| CN112631614B (en) | Application deployment method, device, computer equipment and storage medium | |
| US11303729B2 (en) | Virtual workspace experience visualization and optimization | |
| CN104765621A (en) | Method and system for deploying program on cluster node | |
| CN112242920B (en) | Cloud platform deployment method, device and node | |
| US10120707B2 (en) | Deployment of development environments | |
| CN114650223A (en) | Network configuration method and device of Kubernetes cluster and electronic equipment | |
| CN114661375A (en) | Application integration method and device | |
| US8015274B2 (en) | Automated validation of peripheral director hardware | |
| CN106161075B (en) | Service processing method, device and system | |
| US10491674B2 (en) | Network topology templates for internal states of management and control planes | |
| CN104219280A (en) | Intelligent application data transmission channel | |
| CN116450165A (en) | Method, system, terminal and storage medium for quickly building environment and deploying program | |
| CN113746676B (en) | Network card management method, device, equipment, medium and product based on container cluster | |
| CN115525578A (en) | Form generation method and device, electronic equipment and storage medium | |
| US11487411B2 (en) | Context-driven group pill in a user interface | |
| CN114936152A (en) | Application testing method and device | |
| EP3852424A1 (en) | Application resilience system and method thereof for applications deployed on a platform |
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 |