Micro front-end management method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a micro front end management method and device, electronic equipment and a storage medium, and is applied to the technical field of information, the micro front end management method is applied to the electronic equipment with a Web management interface, and the Web management interface is used for managing a plurality of micro front ends. The method comprises the steps that a synchronization instruction is received, and the synchronization instruction comprises target dependency library information to be synchronized; identifying a plurality of target micro front ends to be synchronized; and according to the target dependency library information, performing batch updating on dependency libraries of the plurality of target micro front ends. After the synchronization instruction is received, the dependency libraries of the multiple target micro front ends are updated in batches through the target dependency library information in the synchronization instruction, so that the problem of inconvenient management of the micro front ends is solved, and the management efficiency of the micro front ends is improved.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a micro-front-end management method, device, electronic device and storage medium. Background Art

[0002] At present, with the development of front-end technology, micro-frontend architecture has gradually attracted attention and application. Micro-frontend architecture can split the front-end application into multiple independent and autonomous small front-end applications (micro-frontends). Each micro-frontend can be independently developed, tested and deployed, thereby improving development efficiency and maintainability. However, with the increase in the number of micro-frontend projects, manual management and maintenance of these projects has become increasingly complex. Developers need to manually update each micro-frontend, which leads to inconvenient management, which is not only time-consuming and labor-intensive, but also prone to errors. Summary of the invention

[0003] The purpose of the embodiments of the present invention is to provide a micro-frontend management method, device, electronic device and storage medium to solve the problem of inconvenience in micro-frontend management. The specific technical solution is as follows:

[0004] In a first aspect of the implementation of the present invention, a micro-frontend management method is first provided, which is applied to an electronic device having a Web management interface, wherein the Web management interface is used to manage multiple micro-frontends;

[0005] The method comprises:

[0006] Receiving a synchronization instruction, wherein the synchronization instruction includes target dependency library information to be synchronized;

[0007] Identify multiple target micro-frontends to be synchronized;

[0008] According to the target dependency library information, the dependency libraries of the multiple target micro front-ends are updated in batches.

[0009] In a possible implementation manner, the receiving a synchronization instruction includes:

[0010] The synchronization instruction is received through the GitLab API.

[0011] In a possible implementation, after identifying the multiple target micro frontends to be synchronized, the method further includes:

[0012] Execute the multiple target micro-frontends and clone one or more requests among local request, local update MASTER request, local dependency INSTALL request, local update and INSTALL request, management dependency request, batch workflow request, create TAG request, and batch command line request.

[0013] In a possible implementation, the identifying multiple target micro frontends to be synchronized includes:

[0014] Receive selection instructions for multiple target micro-frontends;

[0015] Multiple target micro frontends to be synchronized are identified according to the selection instruction.

[0016] In a second aspect of the implementation of the present invention, there is also provided a micro-frontend management device, which is applied to an electronic device having a Web management interface, wherein the Web management interface is used to manage multiple micro-frontends;

[0017] The device comprises:

[0018] An instruction receiving module, used for receiving a synchronization instruction, wherein the synchronization instruction includes target dependency library information to be synchronized;

[0019] The front-end identification module is used to identify multiple target micro-front-ends to be synchronized;

[0020] The dependency library update module is used to batch update the dependency libraries of the multiple target micro front-ends according to the target dependency library information.

[0021] In a possible implementation, the instruction receiving module is specifically configured to receive the synchronization instruction through a GitLab API.

[0022] In a possible implementation, the device further includes:

[0023] The request execution module is specifically used to execute on the multiple target micro-frontends, cloning to local request, local update MASTER request, local dependency INSTALL request, local update and INSTALL request, management dependency request, batch workflow request, create TAG request, batch command line request or one or more requests.

[0024] In a possible implementation, the front-end identification module is specifically used to receive a selection instruction of multiple target micro-front-ends; and identify multiple target micro-front-ends to be synchronized according to the selection instruction.

[0025] In another aspect of the present invention, there is provided an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0026] Memory, used to store computer programs;

[0027] The processor is used to implement any of the micro-frontend management methods described above when executing a program stored in the memory.

[0028] In another aspect of the implementation of the present invention, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, any of the above-mentioned micro-frontend management methods is implemented.

[0029] In another aspect of the implementation of the present invention, a computer program product comprising instructions is also provided, which, when executed on a computer, enables the computer to execute any of the micro-frontend management methods described above.

[0030] A micro-frontend management method, device, electronic device and storage medium provided by an embodiment of the present invention, wherein the micro-frontend management method is applied to an electronic device having a Web management interface, and the Web management interface is used to manage multiple micro-frontends; the method comprises: receiving a synchronization instruction, wherein the synchronization instruction comprises target dependency library information to be synchronized; identifying multiple target micro-frontends to be synchronized; and batch updating the dependency libraries of the multiple target micro-frontends according to the target dependency library information. After receiving the synchronization instruction, the dependency libraries of the multiple target micro-frontends are batch updated according to the target dependency library information in the synchronization instruction, thereby solving the problem of inconvenience in micro-frontend management and improving the management efficiency of micro-frontends. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art are briefly introduced below.

[0032] Figure 1 A schematic diagram of a process flow of a micro-frontend management method provided by an embodiment of the present invention;

[0033] Figure 2 A schematic diagram of a process for obtaining an operation request of a target micro-frontend provided in an embodiment of the present invention;

[0034] Figure 3 A first schematic diagram of a micro-frontend management interface provided by an embodiment of the present invention;

[0035] Figure 4 A second schematic diagram of a micro-frontend management interface provided by an embodiment of the present invention;

[0036] Figure 5 A third schematic diagram of the micro-frontend management interface provided by an embodiment of the present invention;

[0037] Figure 6 A fourth schematic diagram of a micro-frontend management interface provided by an embodiment of the present invention;

[0038] Figure 7 A schematic diagram of the structure of a micro front-end management system provided by an embodiment of the present invention;

[0039] Figure 8 A schematic diagram of the structure of a micro front-end management device provided in an embodiment of the present invention;

[0040] Fig. 9 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0041] The technical solutions in the embodiments of the present invention will be described below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0042] In order to solve the problem that developers need to manually update each micro front-end, which leads to inconvenient management, time-consuming and labor-intensive, and prone to errors, an embodiment of the present invention provides a micro front-end management method, device, electronic device and storage medium.

[0043] In a first aspect of the present invention, a micro-frontend management method is first provided, which is applied to an electronic device having a Web management interface, wherein the Web management interface is used to manage multiple micro-frontends. Figure 1 , Figure 1 A schematic diagram of a flow chart of a micro-frontend management method provided in an embodiment of the present invention, the method comprising:

[0044] Step S11, receiving a synchronization instruction, wherein the synchronization instruction includes target dependency library information to be synchronized;

[0045] Step S12, identifying multiple target micro frontends to be synchronized;

[0046] Step S13: batch update the dependency libraries of the multiple target micro front-ends according to the target dependency library information.

[0047] Corresponding to the above step S11, when receiving the synchronization instruction, the synchronization instruction includes the target dependency library information to be synchronized, so as to facilitate the update of the dependency library according to the target dependency library information. The target dependency library can be a new dependency library for updating, and the old dependency library is updated through the dependency library. In a possible implementation, the method of the embodiment of the present invention can be implemented by a management platform, and the user can perform various batch operations through the user-friendly interface provided by the platform. Specifically, a modern front-end framework such as React (a JavaScript library for building user interfaces) can be used for development. In an example, in the interface, the user can select a local folder, and through the scanning option, scan all microservices in the folder, and extract the attribute information of these microservices, so as to manage these microservices. When selecting the target dependency library in the management platform, the location information of the target dependency library can be selected, so as to identify and add the target dependency library through the location information. Specifically, the synchronization instruction can be input by the user through the user interface or selected from a plurality of optional requests provided in advance.

[0048] Corresponding to the above-mentioned step S12, to identify multiple target micro-frontends to be synchronized, the selection information of multiple target micro-frontends can be received first, and then the multiple target micro-frontends can be identified according to the multiple target micro-frontends. Among them, the selection information of multiple target micro-frontends can be selected by the user according to the attribute information of multiple micro-frontends displayed on the interface corresponding to the method of the embodiment of the present invention. Specifically, the attribute information of multiple micro-frontends may include the name, storage location, content, size, version and other information of the multiple micro-frontends. It should be noted that in actual use, multiple target micro-frontends can also be identified first, and then the synchronization instruction can be received, that is, executing step S12 first and then executing step S11 also belongs to the protection scope of the present invention.

[0049] Corresponding to the above step S13, the dependency libraries of the multiple target micro-frontends are updated in batches according to the target dependency library information, and the dependency libraries of the multiple target micro-frontends can be synchronized in batches according to the target dependency library information, thereby realizing the management of multiple micro-frontends and improving management efficiency.

[0050] The present invention can centrally manage and maintain multiple micro-frontend projects through a unified Web (network) interface. Utilize automated tools and batch operations to reduce the complexity and error rate of manual operations. The core principle is to automate various operations using an API (application programming interface) through integration with a version control system (such as GitLab (a warehouse management system)) to ensure the consistency and efficiency of the dependencies and version control of multiple micro-frontend projects. Specifically, based on external input instructions, the dependency libraries of multiple front-end microservice applications can be synchronized (including synchronous updates or rollbacks), that is, through the network architecture, the target version of the dependency library installation resources are transmitted to the client device where the corresponding micro-frontend is located, so that each microservice application updates the dependency library version based on the installation resources, with the aim of keeping the dependency libraries of these microservice applications consistent, so as to improve synchronization efficiency and reduce compatibility issues.

[0051] It can be seen that through the method of the embodiment of the present invention, after receiving the synchronization instruction, the dependency libraries of multiple target micro-frontends are updated in batches through the target dependency library information in the synchronization instruction, thereby solving the problem of inconvenient management of micro-frontends and improving the management efficiency of micro-frontends.

[0052] In one possible implementation, see Figure 2 , the identifying multiple target micro frontends to be synchronized includes:

[0053] Step S21, receiving selection instructions of multiple target micro front-ends;

[0054] Step S22, identifying multiple target micro front-ends to be synchronized according to the selection instruction.

[0055] Among them, see Figure 3-Figure 6 , receiving the selection instructions of multiple target micro-frontends, the user can perform various batch operations through the user-friendly interface provided by the embodiment of the present invention, and the interface can be developed using an existing front-end framework such as React. For example, the user can select multiple target micro-frontends by clicking the cursor, or by entering the corresponding numbers of multiple target micro-frontends to select, thereby realizing the identification of multiple target micro-frontends.

[0056] In a possible implementation, after identifying the multiple target micro-frontends to be synchronized, the method further includes: executing, on the multiple target micro-frontends, one or more requests selected from the group consisting of: clone to local request, local update MASTER (default master branch name) request, local dependency INSTALL (installation) request, local update and INSTALL request, management dependency request, batch workflow request, create TAG (element) request, and batch command line request. Figure 3The front-end management interface can include common front-end batch operations, such as cloning to local, local update MASTER (default master branch name), local dependency INSTALL, local update and INSTALL, manage dependencies, batch workflow, create TAG, batch command line, etc., and can automatically scan through local folders and local directories to obtain information about scanned local file 1, scanned local file 2, scanned local file 3, scanned local file 4, and scanned local file 5. See Figure 4 In the front-end management interface, you can scan local folders and local directories automatically to obtain information about scanned local file 1, scanned local file 2, scanned local file 3, scanned local file 4, and scanned local file 5. For dependency management, you can click to expand and select sub-items, select sub-items according to the options, and perform one-click upgrades and dependency package upgrades. You can upgrade common dependency packages with one click, enter the dependency package name to upgrade the dependency package, and after the selection is completed, you can click the Execute option to execute. See Figure 5 In the front-end management interface, you can scan local folders and local directories automatically to get information about scanned local file 1, scanned local file 2, scanned local file 3, scanned local file 4, and scanned local file 5. You can also execute in batch workflows, click to expand and select sub-projects, and then create temporary branches, batch modify, submit to create MR (MapReduce, a programming model), and delete branches. You can also enter the branch name in the creation of temporary branches. See Figure 6 In the front-end management interface, you can scan local folders and local directories automatically to get information about scanned local file 1, scanned local file 2, scanned local file 3, scanned local file 4, and scanned local file 5. In the batch command line option, you can click to expand and select sub-items, enter commands, and execute them. Figure 4, after selecting a local project, you can use scripts to batch update and install the npm (Node Package Manager, a package management and distribution tool) package dependency versions of the selected project. The default latest version can be freely specified. Operation requests can include batch workflows, which can refer to abstracting the daily development process into several steps and applying them in batches to the selected sub-projects, i.e., micro-frontends. Operation requests can include batch workflows, such as stash>create branch>manual modification>commit>MR to master. The batch command line function is a batch request, a more flexible function. The above capabilities can be achieved through the distributed execution of the batch command line function.

[0057] In a possible implementation, the receiving of the synchronization instruction includes: receiving the synchronization instruction through GitLab API (an interface for interacting with GitLab (an open source project for warehouse management system) service). In the embodiment of the present invention, when sending operation requests for each target micro-frontend to the backend, the backend is mainly responsible for processing the frontend request and interacting with the GitLab API. Specifically, Node.js, Socket.io, and Express frameworks can be used for development, which can not only process real-time tasks and execute asynchronous tasks, thereby achieving more flexible execution, but also handle complex business logic and automation tasks.

[0058] See also Figure 7 , in order to illustrate the scheme of the embodiment of the present invention, the following is a specific embodiment, including: the front-end function module sends a request to the back-end local-agent through the web front-end interface, and then the back-end local-agent interacts with the GitLab API; at the same time, the front-end function module can include batch update master, batch management of dependencies, batch workflow and batch command functions; and the back-end local-agent interacts with the back-end function module, and the back-end function module includes executing real-time and asynchronous tasks and processing front-end requests, as well as interacting with the GitLab API. In the system corresponding to the present invention, the front-end function module includes batch update master, batch management of dependencies, batch workflow, and batch command line functions, and these modules can be controlled through the Web front-end interface; the back-end function module includes: executing real-time and asynchronous tasks, processing front-end requests, interacting with the GitLab API, and also includes the back-end local-agent and the GitLab API.

[0059] The scheme of the embodiment of the present invention includes: 1. Batch update and operation functions, which can select multiple microservices and corresponding operation instructions through the front-end interface, so as to perform corresponding operations on the selected multiple microservices and realize batch operation of microservices. Specifically, the corresponding operation instructions can be executed on the selected multiple microservices in sequence; using the Web front-end interface, batch update master, batch management of dependencies, batch workflow, batch command line operation and other functions of multiple micro front-end projects can be realized; through the batch operation function, users can update and manage multiple projects at one time, which greatly saves time and energy, improves operation efficiency and reduces the tediousness and error rate of manual operation.

[0060] 2. Automated dependency management. In the batch dependency management function, you can select the projects that need to be managed through the front-end interface and batch update their npm package dependency versions, and update them to the latest version or specified version; realize automated and batch dependency management to ensure that all micro-front-end projects use consistent dependency versions, reduce dependency conflicts and compatibility issues, and improve the efficiency of dependency management.

[0061] 3. Abstracted batch workflow. The present invention can abstract the daily development process into several steps, and apply them in batches to selected sub-projects through the Web interface to achieve batch operations; standardize and automate the daily development process, so that the development operations of multiple projects are more consistent, reduce errors introduced by human operations, and improve development efficiency and process standardization.

[0062] 4. Flexible batch command line function. The present invention can provide a more flexible batch command line function. Users can input any command through the Web interface and execute these commands in a distributed manner. Through the batch command line function, users can flexibly execute various customized operation requirements to meet the usage requirements of different scenarios, thereby improving the flexibility and versatility of the system.

[0063] 5. The backend service interacts with the GitLab API. The backend service (local-agent) of the present invention realizes a series of automated operations such as version control and branch management through integration with the GitLab API. By using the GitLab API, automated operations on version control and branch management are realized, which improves the management efficiency and consistency of the code, reduces the necessity of manual intervention, and further improves the automation level of the development process.

[0064] It can be seen that through the solution of the embodiment of the present invention, not only can batch updates and operations be implemented, but also basic operations of multiple micro-frontend projects can be automatically updated in batches, such as updating master branches, dependency management, workflow operations, etc.; and dependency management can be implemented, by batch updating and managing the dependencies of multiple projects, to ensure that all micro-frontend projects use consistent dependency versions; standardized workflows are implemented, daily development operation processes are abstracted, and batch applied to multiple micro-frontend projects to ensure consistency of operations; flexible command line operations are implemented, allowing users to enter customized commands through the Web interface and execute these commands in batches to meet flexible operation requirements.

[0065] In a second aspect of the implementation of the present invention, there is also provided a micro-frontend management device, which is applied to an electronic device having a Web management interface, wherein the Web management interface is used to manage multiple micro-frontends;

[0066] See also Figure 8 , the device comprises:

[0067] The instruction receiving module 801 is used to receive a synchronization instruction, wherein the synchronization instruction includes target dependency library information to be synchronized;

[0068] A front-end identification module 802 is used to identify multiple target micro-front-ends to be synchronized;

[0069] The dependency library update module 803 is used to batch update the dependency libraries of the multiple target micro front-ends according to the target dependency library information.

[0070] In a possible implementation, the instruction receiving module is specifically configured to receive the synchronization instruction through a GitLab API.

[0071] In a possible implementation, the device further includes:

[0072] The request execution module is specifically used to execute on the multiple target micro-frontends, cloning to local request, local update MASTER request, local dependency INSTALL request, local update and INSTALL request, management dependency request, batch workflow request, create TAG request, batch command line request or one or more requests.

[0073] In a possible implementation, the front-end identification module is specifically used to receive a selection instruction of multiple target micro-front-ends; and identify multiple target micro-front-ends to be synchronized according to the selection instruction.

[0074] It can be seen that through the device of the embodiment of the present invention, after receiving the synchronization instruction, the dependency libraries of multiple target micro-frontends are updated in batches through the target dependency library information in the synchronization instruction, thereby solving the problem of inconvenient management of micro-frontends and improving the management efficiency of micro-frontends.

[0075] The embodiment of the present invention further provides an electronic device, such as Fig. 9 As shown, it includes a processor 901, a communication interface 902, a memory 903 and a communication bus 904, wherein the processor 901, the communication interface 902, and the memory 903 communicate with each other through the communication bus 904.

[0076] Memory 903, used for storing computer programs;

[0077] The processor 901 is used to execute the program stored in the memory 903 to implement the following steps:

[0078] Receiving a synchronization instruction, wherein the synchronization instruction includes target dependency library information to be synchronized;

[0079] Identify multiple target micro-frontends to be synchronized;

[0080] According to the target dependency library information, the dependency libraries of the multiple target micro front-ends are updated in batches.

[0081] The communication bus mentioned in the above terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0082] The communication interface is used for communication between the above terminal and other devices.

[0083] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0084] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0085] In another embodiment provided by the present invention, a computer-readable storage medium is also provided, in which a computer program is stored. When the computer program is executed by a processor, the micro-front-end management method described in any one of the above embodiments is implemented.

[0086] In another embodiment provided by the present invention, a computer program product comprising instructions is also provided, which, when executed on a computer, enables the computer to execute the micro-frontend management method described in any one of the above embodiments.

[0087] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.

[0088] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0089] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, electronic device, storage medium and computer program product embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0090] The above description is only a preferred embodiment of the present invention and is not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A micro front-end management method, characterized in that: Applied to electronic devices with a Web management interface, the Web management interface is used to manage multiple micro front ends; The method comprises: Receiving a synchronization instruction, wherein the synchronization instruction includes target dependency library information to be synchronized; Identify multiple target micro-frontends to be synchronized; According to the target dependency library information, the dependency libraries of the multiple target micro front-ends are updated in batches.

2. The method according to claim 1, characterized in that The receiving synchronization instruction comprises: The synchronization instruction is received through the GitLab API.

3. The method according to claim 1, characterized in that After identifying the plurality of target micro frontends to be synchronized, the method further includes: Execute the multiple target micro-frontends and clone one or more requests among local request, local update MASTER request, local dependency INSTALL request, local update and INSTALL request, management dependency request, batch workflow request, create TAG request, and batch command line request.

4. The method according to claim 1, characterized in that: The identifying multiple target micro frontends to be synchronized includes: Receive selection instructions for multiple target micro-frontends; Multiple target micro frontends to be synchronized are identified according to the selection instruction.

5. A micro front-end management device, characterized in that: Applied to electronic devices with a Web management interface, the Web management interface is used to manage multiple micro front ends; The device comprises: An instruction receiving module, used for receiving a synchronization instruction, wherein the synchronization instruction includes target dependency library information to be synchronized; The front-end identification module is used to identify multiple target micro-front-ends to be synchronized; The dependency library update module is used to batch update the dependency libraries of the multiple target micro front-ends according to the target dependency library information.

6. The device according to claim 5, characterized in that The instruction receiving module is specifically used to receive the synchronization instruction through the GitLab API.

7. The device according to claim 5, characterized in that The device also includes: The request execution module is specifically used to execute on the multiple target micro-frontends, cloning to local request, local update MASTER request, local dependency INSTALL request, local update and INSTALL request, management dependency request, batch workflow request, create TAG request, batch command line request or one or more requests.

8. The device according to claim 7, characterized in that The front-end identification module is specifically used to receive a selection instruction of multiple target micro-front-ends; and identify multiple target micro-front-ends to be synchronized according to the selection instruction.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; A processor, for implementing the method steps described in any one of claims 1 to 4 when executing a program stored in a memory.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps described in any one of claims 1 to 4 are implemented.

Images