WO2023016019A1

WO2023016019A1 - Resource sharing methods and micro-front-end system, application, and computer-readable storage medium

Info

Publication number: WO2023016019A1
Application number: PCT/CN2022/093303
Authority: WO
Inventors: 唐华; 熊大旺; 王淼; 孟照星
Original assignee: 中兴通讯股份有限公司
Priority date: 2021-08-10
Filing date: 2022-05-17
Publication date: 2023-02-16
Also published as: CN115842733A

Abstract

Resource sharing methods, a micro-front-end system, an application, and a computer-readable storage medium. A resource sharing method is applied to a micro-front-end system. The micro-front-end system comprises a first application (100), a second application (200), and a resource management apparatus (300). The first application (100) comprises a resource loading apparatus (110) that is configured to load a standby shared resource. The method comprises: a second application sending registration information to a first application, the registration information comprising resource information, and the resource information being used to represent a feature of a target shared resource that needs to be invoked by the second application (S100); a resource management apparatus determining, according to the resource information and the standby shared resource, a loading policy for the target shared resource (S200); the first application updating a resource loading apparatus according to the loading policy (S300); and the second application invoking the target shared resource from the updated resource loading apparatus (S400).

Description

Resource sharing method, micro-frontend system, application, and computer-readable storage medium

Cross References to Related Applications

This application is based on a Chinese patent application with application number 202110914151.8 and a filing date of August 10, 2021, and claims the priority of this Chinese patent application. The entire content of this Chinese patent application is hereby incorporated by reference into this application.

technical field

Embodiments of the present application relate to but are not limited to the technical field of computer networks, and in particular, relate to a resource sharing method, a micro front-end system, an application, and a computer-readable storage medium.

Background technique

At present, in the front-end field, single-page applications are widely concerned and used as a project form, but with the passage of time and the enrichment of application functions, the single-page applications become less and less single and more and more Difficult to maintain, often changing one of them will affect the whole single page application, and the resulting cost of publishing is getting higher and higher. In response to this problem, the industry has proposed the concept of microservices, that is, to split and decouple these huge applications, so that each module can be maintained and deployed independently, thereby improving development efficiency. The concept of microservices is also applied to the front-end field, that is, the micro-frontend. Its core idea is to transform the network application from a single single application to multiple applications that aggregate multiple small front-end applications into one.

Micro front-end technology is different from server-side technology. Although each front-end application has been split to achieve independent development, independent operation and independent deployment, it still needs to be integrated at the browser level when it is displayed to users. When the browser loads, it will refer to a large number of repeated static dependent resources. This shared basic resource has problems such as repeated packaging, storage space occupation, and low reuse rate of basic library code. It not only wastes network bandwidth at runtime, but also increases Access response time. For this reason, the front-end field proposes to share duplicate network resources to alleviate the above problems. In some cases, it mainly stores the requested shared resources in the cache of a network node and makes a judgment every time a resource is requested, thereby Choosing to access from the cache or the original resource address has the disadvantage of increasing the computational complexity of resource requests and increasing the complexity of managing cache resources. For example, when multiple resource requests are involved, a large number of cache resources may need to be managed at the same time , causing the response time of the access to be extended, and this method cannot rule out the occurrence of repeated requests, which may still waste network bandwidth.

Contents of the invention

The following is an overview of the topics described in detail in this article. This summary is not intended to limit the scope of the claims.

Embodiments of the present application provide a resource sharing method, a micro front-end system, an application, and a computer-readable storage medium.

In the first aspect, the embodiment of the present application provides a resource sharing method, which is applied to a micro front-end system, and the micro front-end system includes a first application, a second application, and a resource management device, and the first application includes a A resource loading device for standby shared resources, the resource sharing method includes: the second application sends registration information to the first application, the registration information includes resource information, and the resource information is used to characterize the second application The characteristics of the target shared resource to be called; the resource management device receives the resource information sent by the first application, and determines the loading of the target shared resource according to the resource information and the standby shared resource strategy; the first application receives the loading strategy sent by the resource management device, and updates the resource loading device according to the loading strategy; the second application calls from the updated resource loading device The objects share resources.

In the second aspect, the embodiment of the present application also provides a resource sharing method, which is applied to the first application in the micro front end system, and the first application includes a resource loading device configured to load a spare shared resource, and the micro front end The system further includes a second application and a resource management device, and the resource sharing method includes: acquiring registration information sent by the second application, the registration information including resource information, and the resource information is used to characterize the second application The characteristics of the target shared resource to be called; sending the resource information to the resource management device, so that the resource management device determines the loading strategy for the target shared resource according to the resource information and the standby shared resource; receiving The loading strategy sent by the resource management device, and updating the resource loading device according to the loading policy, so that the second application calls the target shared resource from the updated resource loading device.

In the third aspect, the embodiment of the present application also provides a resource sharing method, which is applied to the second application in the micro front end system, and the micro front end system also includes a first application and a resource management device, and the first application includes the A resource loading device configured to load standby shared resources, the resource sharing method includes: sending registration information to the first application, so that the first application sends resource information to the resource management device, and makes the resource The management device determines a loading strategy for the target shared resource according to the resource information and the backup shared resource, wherein the registration information includes resource information, and the resource information is used to characterize the The characteristics of the target shared resource; the target shared resource is called from the updated resource loading device, and the updated resource loading device is the first application according to the loading sent by the resource management device. determined by the strategy.

In the fourth aspect, the embodiment of the present application also provides a micro front-end system, including: a memory, a processor, and a computer program stored on the memory and operable on the processor, and the processor implements the computer program when executing the computer program. The resource sharing method of the first aspect as mentioned above.

In the fifth aspect, the embodiment of the present application also provides a network device, including: a memory, a processor, and a computer program stored on the memory and operable on the processor. When the processor executes the computer program, the above-mentioned The resource sharing method in the second aspect, or, implement the resource sharing method in the third aspect as described above.

In the sixth aspect, the embodiment of the present application also provides a computer-readable storage medium, which stores computer-executable instructions, and the computer-executable instructions are used to execute the resource sharing method in the first aspect as described above, or to execute the above-mentioned The resource sharing method in the second aspect, or execute the resource sharing method in the third aspect as described above.

Additional features and advantages of the application will be set forth in the description which follows, and, in part, will be obvious from the description, or may be learned by practice of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The accompanying drawings are used to provide a further understanding of the technical solution of the present application, and constitute a part of the specification, and are used together with the embodiments of the present application to explain the technical solution of the present application, and do not constitute a limitation to the technical solution of the present application.

FIG. 1 is a schematic diagram of a micro front-end system for performing a resource sharing method provided by an embodiment of the present application;

Fig. 2 is a schematic diagram of a page of a menu module provided by an embodiment of the present application;

FIG. 3 is a flowchart of a resource sharing method provided by an embodiment of the present application;

FIG. 4 is a flow chart of determining a loading policy by a resource management device in a resource sharing method provided by an embodiment of the present application;

FIG. 5 is a flow chart of determining a loading policy by a resource management device in a resource sharing method provided by another embodiment of the present application;

Fig. 6 is a flow chart of the first application update resource loading device in the resource sharing method provided by an embodiment of the present application;

FIG. 7 is a flow chart after the second application calls the target shared resource in the resource sharing method provided by an embodiment of the present application;

Fig. 8 is a schematic diagram of the page of the first application provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of a micro front-end system provided by another embodiment of the present application;

Fig. 10 is a flow chart of the resource sharing method performed by the micro front-end system provided by the embodiment shown in Fig. 9;

FIG. 11 is a flowchart of a resource sharing method provided by another embodiment of the present application;

Fig. 12 is a flowchart of updating a resource loading device in a resource sharing method provided by an embodiment of the present application;

FIG. 13 is a flowchart of a resource sharing method provided by another embodiment of the present application;

Fig. 14 is a schematic diagram of a micro front-end system provided by another embodiment of the present application;

Fig. 15 is a schematic diagram of a network device provided by an embodiment of the present application;

Fig. 16 is a schematic diagram of a network device provided by another embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the application clearer, the application will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described here are only used to explain the present application, not to limit the present application.

It should be noted that although the functional modules are divided in the schematic diagram of the device, and the logical sequence is shown in the flowchart, in some cases, it can be executed in a different order than the module division in the device or the flowchart in the flowchart. steps shown or described. The terms "first", "second" and the like in the specification and claims and the above drawings are used to distinguish similar objects, and not necessarily used to describe a specific sequence or sequence.

The present application provides a resource sharing method, a micro-frontend system, an application, and a computer-readable storage medium. In the micro-frontend system, the first application collects the registration information of the second application so that the resource management device determines the loading strategy, and according to The loading strategy updates the resource loading device, so that the resource loading device can dynamically introduce the target shared resources that the second application needs to call as needed. Since the first application and the second application in the micro front-end system are loaded on the same page, it is available for The second application directly calls the target shared resource from the resource loading device. Compared with some situations, it does not need to perform address access or cache call resource multiple times, so resource sharing can be performed while saving network bandwidth and shortening response delay. It is beneficial to improve the execution efficiency of the micro front-end system for resource sharing.

The embodiments of the present application will be further described below in conjunction with the accompanying drawings.

As shown in FIG. 1 , FIG. 1 is a schematic diagram of a micro front-end system 400 for performing a resource sharing method provided by an embodiment of the present application.

In the example of FIG. 1 , the micro frontend system 400 includes, but is not limited to: a first application 100, a second application 200, and a resource management device 300. The first application 100 may include, but is not limited to, the Resource loading means 110. In another embodiment, the micro front end system 400 may also include a shared resource library, where the shared resource library is used to store shared resources, and the stored shared resources may be spare contribution resources, or other types or forms of shared resources , the shared resource library can be, but not limited to, a micro-application that runs independently, and is responsible for storage and version management of shared resources.

In one embodiment, the micro-frontend system 400 can be constructed based on micro-services, but not limited to, and can realize related functions of the micro-frontend. In the micro-frontend system 400, the first application 100 and the second application 200 are mutually subordinate, Among them, the first application 100 serves as the main application, and the second application 200 serves as the sub-application, and the normal function execution of the micro front-end system 400 can be realized through cooperation and interaction between the two and the resource management device 300. It should be noted that the second application 200 It can be set to multiple, in this case, each second application 200 is a sub-application corresponding to the first application 100, that is, each second application 200 can also realize The normal function of the micro frontend system 400 is executed, therefore, this embodiment does not and does not need to limit the specific number of the second applications 200 .

In an embodiment, the first application 100 may be the micro-application that the terminal finally accesses, that is, no matter how many applications the terminal accesses, the application that the terminal finally confirms to access is used as the first application 100, so that the determined first application 100 can better match the routing rules under network conditions, so as to more accurately and reliably integrate one or more second applications 200 split from the micro front end, so as to cooperate to realize one or more second applications 200's loading display, communication and resource sharing, in other words, in the micro front-end system 400, the first application 100 and the second application 200 are integrated on the same hypertext markup language (Hyper Text Markup Language, HTML) page, therefore, the second The application 200 can share the resource pool of the first application 100, that is, not only the first application 100 can call the corresponding standby shared resource from the resource loading device 110, but the second application 200 can also call the corresponding standby shared resource from the resource loading device 110 .

In one embodiment, the number of terminals accessing the first application 100 is not limited, it can be set to multiple, and each terminal can be called an access terminal, user equipment (User Equipment, UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. For example, each terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a Handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, 5G networks or terminal devices in future 5G or higher networks, etc., are not specifically limited in this embodiment.

In one embodiment, the second application 200 can be, but not limited to, a front-end micro-application that can be independently developed and deployed independently according to the division of internal functional modules and has certain functional responsibilities. The second application 200 can run independently or be integrated into Running on the page of the first application 100, the embodiment of the present application is mainly aimed at resource sharing by integrating the second application 200 into running on the page of the first application 100, those skilled in the art can select the second application 200 according to the actual scene The mode of operation is not limited.

In an embodiment, various types of functional modules can be integrated inside the second application 200 and presented in the form of menus. For example, the second application 200 includes but not limited to functional modules, resource modules, and registration modules. Arranged on the page of the second application 200 in the form of a menu, wherein the functional modules can reflect the situation of the life cycle function of the second application 200 itself and display it to the outside, and the resource module is set to be imported and managed with the second application 200 Matching shared resources, the registration module can be applied to the situation when the second application 200 is integrated, can register relevant information inside the second application 200 to the first application 100, and can monitor menus and receive menu-related information definition files (For example, it can be an identification information file, a resource information file, and a serial number information file, etc.), so that the terminal can know the possible changes in the menu. It can be understood that the way the registration module implements message registration and reception is not limited. Those skilled in the art can make settings according to actual scenarios.

In one embodiment, the resource loading device 110 is provided as a resource pool, which can accommodate different shared resources as backup, and has the capability of continuous updating, that is, under the action of the first application 100, new shared resources can be continuously introduced. , to achieve the effect of updating shared resources in a timely manner. It should be noted that the resource loading device 110 can also be set as an independently running micro-application, that is, the resource loading device 110 is distinguished from the first application 100, which does not affect the function execution of the resource loading device 110; in addition, other types of modules can also be integrated inside the first application 100, for example, the first application 100 also includes but is not limited to a routing loading module, a menu module and a document object model (Document Object Model, DOM) container, etc., wherein, the route loading module is set to respond to route switching and trigger the loading of the corresponding second application 200, thereby displaying the interface elements of the second application 200 to the DOM container, and the menu module is responsible for receiving and displaying information from the second application The registration information of the application 200 can cache the content information of one or more shared resources corresponding to the second application 200 at the same time, and the DOM container, as a kind of HTML container, can be used to display the interface elements of the second application 200, so that the second The degree of visualization of the application 200 becomes higher.

It can be understood that there may be more types and quantities of multiple function modules integrated in the first application 100 and the second application 200, which is not limited; The purpose of multiple functional modules is to achieve functional differentiation, that is, the corresponding functional modules perform corresponding functions, which greatly reduces the probability of errors in function execution, and is more convenient for management and control, and it is easier to find out more intuitively when problems occur The functional modules corresponding to the problems, so that the corresponding functional modules can be easily adjusted or updated.

Example one:

As shown in FIG. 2, FIG. 2 shows a form of a menu module presented in a table. It can be seen from FIG. 2 that the types and meanings of the attributes corresponding to the second application 200 are determined in one-to-one correspondence. For example, the ID corresponds to the string type and is a unique identifier. mfaHash embodies the routing rule that triggers the loading of the second application 200, and also serves as the globally unique name of the second application 200; Shown together, for example, Share Component embodies the shared resource list, the first subattribute Component Name embodies the name of the shared resource, and the second subattribute Component Version embodies the shared resource version, therefore, the menu module shown in Figure 2 can accurately The registration information about the second application 200 is obtained.

In Figure 2, for each attribute, ID represents a unique identifier, name is divided into zh name and en name, representing the Chinese name and English name respectively, parentid represents the parent menu identification, order represents the menu sorting number, and href represents the uniform resource locator ( Uniform Resource Locator, URL) address, mfaHash indicates the hash name that triggers loading, Share Component is divided into Component Name and Component Version, which respectively indicate the shared resource name and shared resource version, group indicates other extended fields; for each type, string indicates characters String type, int means integer type, and object means software set type of related variables and methods.

Both the first application 100 and the second application 200 in the micro-frontend system 400 may respectively include a memory and a processor, wherein the memory and the processor may be connected through a bus or in other ways.

As a non-transitory computer-readable storage medium, memory can be configured to store non-transitory software programs and non-transitory computer-executable programs. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage devices. In some embodiments, the memory may include memory located remotely from the processor, which remote memory may be connected to the processor through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The micro front-end system 400 and the application scenarios described in the embodiment of the present application are to illustrate the technical solutions of the embodiments of the present application more clearly, and do not constitute a limitation to the technical solutions provided in the embodiments of the present application. Those skilled in the art know that as With the evolution of the micro front-end system 400 and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

Those skilled in the art can understand that the micro front end system 400 shown in FIG. layout of the components.

In the micro-frontend system 400 shown in FIG. 1 , the first application 100 and the second application 200 can respectively call their stored resource sharing programs to execute the resource sharing method.

Based on the above structure of the micro front end system 400, various embodiments of the resource sharing method of the present application are proposed.

As shown in Figure 3, Figure 3 is a flow chart of a resource sharing method provided by an embodiment of the present application, which can be but not limited to be applied to the micro front-end system shown in the embodiment of Figure 1, the resource sharing method includes but is not limited to the steps S100 to S400.

Step S100, the second application sends registration information to the first application, the registration information includes resource information, and the resource information is used to characterize the characteristics of the target shared resource that the second application needs to call.

In an embodiment, because the registration information can represent the characteristics of each module or device inside the second application, for example, the registration information includes resource information, which discloses the characteristics of the target shared resource that the second application needs to call, therefore, By sending the registration information to the first application, the second application can make the first application accurately know the internal situation of the second application, and use it as a basis for interaction, so as to facilitate subsequent loading of the second application as a corresponding reference condition.

In one embodiment, the second application uses the model-driven message middleware method to send registration information to the first application, that is, the information is transmitted based on the model-driven message middleware method, the information transmission process is relatively stable, and registration information is not easy to occur. In the case of information loss, good sending efficiency can be guaranteed.

It should be noted that there may be various types of registration information. For example, referring to the types shown in FIG. 2 , those skilled in the art may select according to actual scenarios, which is not limited in this embodiment.

In step S200, the resource management device receives the resource information sent by the first application, and determines a loading strategy for the target shared resource according to the resource information and the standby shared resource.

In one embodiment, the resource management device can be used as an independently running micro-application to manage the shared resources at runtime, maintain the currently loaded standby shared resources, and dynamically construct new resource access addresses as needed according to the loading strategy and introduce them to the first An application, that is, by determining the loading policy for the first application, the resource management device can lay a foundation for the first application to update the resource loading device, so that the first application performs subsequent corresponding operations according to the loading policy.

It should be noted that, in a certain scenario, the resource management device may also be integrated into the first application for use, which is not limited.

As shown in FIG. 4 , "determining a loading strategy for the target shared resource according to the resource information and the standby shared resource" in step S200 includes but is not limited to steps S210 to S220.

Step S210, the resource management device determines the loading status of the target shared resource in the resource loading device according to the resource information and the backup shared resource;

In step S220, the resource management device determines a loading strategy for the target shared resource according to the loading situation.

In an embodiment, since the resource information is used to characterize the characteristics of the target shared resource to be invoked by the second application, by coordinating the resource information with the standby shared resource, it can be determined that the target shared resource corresponding to the resource information is Based on the actual situation in the device, the resource management device can determine an accurate and reliable loading strategy according to the loading situation.

Specifically, as shown in FIG. 5, step S220 includes but is not limited to step S221.

Step S221, if the target shared resource is not loaded in the resource loading device, the resource management device constructs a target access address corresponding to the target shared resource according to the target shared resource, and embeds the target access address into the first application.

In one embodiment, if the target shared resource is loaded on the resource loading device, it means that the backup shared resource in the resource loading device already contains the target shared resource, so there is no need to adjust the backup shared resource in the resource loading device, and you can directly Applying the resource loading device, this is a loading strategy for the target shared resource in one situation; on the contrary, if the target shared resource is not loaded in the resource loading device, it means that the backup shared resource in the resource loading device does not include the target shared resource, Therefore, it is necessary to adjust the spare shared resources in the resource loading device. Therefore, the resource management device constructs the target access address corresponding to the target shared resource according to the target shared resource, and embeds the target access address into the first application, that is, equivalent to The target shared resource corresponding to the target access address can be introduced into the first application, so that the first application can correspondingly update the resource loading device, which is the loading strategy of the target shared resource in another situation.

It can be understood that the target access address corresponds to the target shared resource. Therefore, embedding the target access address into the first application is equivalent to introducing the target shared resource into the first application. Other forms of expression replace the access address, as long as the replaced form of expression is related to the target shared resource. In addition, the loading policy is not limited to only being related to the loading situation of the target shared resource on the resource loading device, and those skilled in the art can also set the loading policy according to specific application scenarios, which is not limited in this embodiment.

Step S300, the first application receives the loading policy sent by the resource management device, and updates the resource loading device according to the loading policy.

In one embodiment, the first application updates the resource loading device according to the loading strategy, so that the resource loading device can dynamically introduce the target shared resources that the second application needs to call as needed. Therefore, the backup shared resources in the updated resource management device Resources, including target shared resources, are able to meet loading requirements.

Specifically, as shown in FIG. 6, step S300 includes but is not limited to step S310.

Step S310, the first application imports the target shared resource from the shared resource library according to the target access address, and sends the target shared resource to the resource loading device.

In one embodiment, since the target access address corresponds to the target shared resource, the relevant information of the target shared resource can be determined through the target access address, so that the target shared resource can be imported from the shared resource library only through the target access address As far as the resource loading device is concerned, it can be seen that the loading strategy can realize the introduction of shared resources only depending on the network access address, without consuming a large amount of network resources, which is beneficial to reduce network costs.

Step S400, the second application invokes the target shared resource from the updated resource loading device.

In one embodiment, the resource loading device dynamically imports the target shared resources that the second application needs to call as needed. Since the first application and the second application in the micro frontend system are loaded on the same page, they can be used by the second application Directly call the target shared resource from the resource loading device. Compared with some situations, there is no need to perform multiple address access or cache call resources. Therefore, resource sharing can be carried out while saving network bandwidth and shortening response delay, which is conducive to improving micro The execution efficiency of the front-end system for resource sharing.

In the example of FIG. 7 , after step S400 , step S500 is also included but not limited to.

In step S500, the first application displays interface elements of the second application, and the interface elements correspond to target shared resources.

In an embodiment, by displaying the interface elements of the second application integratedly on the first application, it can be used to display the loading status of the second application, so that the visibility of loading the second application becomes higher. For the terminal In other words, it is possible to understand the loading situation of the second application more intuitively, so as to meet the application requirements of the terminal.

It should be noted that there may be multiple second applications, and each second application and related components execute the steps of the above embodiments independently of each other. Therefore, since each application is loaded on the same page, the required component resources are running It can be loaded only once to achieve global shared access, saving network bandwidth and improving access performance; in this process, no matter how many second applications are set, resource sharing is managed by the first application in a unified manner , even though the registration information of different second applications may change, the first application will still implement dynamic on-demand import according to the loading situation, so that the second application can directly call the required target shared resources. Therefore, this implementation The micro-frontend system of the example realizes "one-time introduction, multiple use" of shared resources, which is simple, reliable and more efficient.

Specific examples are given below to illustrate the basic principles of the above-mentioned embodiments.

Example two:

As shown in FIG. 8 , FIG. 8 is a schematic diagram of a page of a first application provided by an embodiment of the present application.

As shown in Figure 8, the menu area and the module menu area of the second application are integrated into the first application, and the first application also integrates its own function menu area. Specifically, the page presented to the user is composed of a Portal main application (namely the first application) and several independently deployed sub-applications (namely the second application). The first application menu area is dynamically combined by each second application through menu registration. The menu model information includes the resource information of the second application. The second application content display area is set in the interface element display container inside the first application, which can Using a DOM container, for the first application, dynamically match and load the corresponding second application according to the change of the routing address, and render it to a DOM container to display its interface elements, as shown in Figure 8 The module menu area of the second application is also rendered to the corresponding DOM container at the same time. and the second application 5), through the first application, each second application can run independently in different DOM containers after being loaded, and be isolated from each other, so that the coupling between the various functional modules is greatly reduced. It can be seen that, as The integrated display method shown in FIG. 8 ensures that both the first application and the second application have a good display space, and the second applications do not affect each other, thereby improving the rendering and display effect of the second application.

Example three:

As shown in FIG. 9 , FIG. 9 is a schematic diagram of a micro front-end system provided by another embodiment of the present application.

As shown in FIG. 10 , FIG. 10 is a flow chart of the resource sharing method performed by the micro front-end system shown in FIG. 9 .

In the example in FIG. 9 , the second application includes two, respectively, the second application 1 and the second application 2. Since the second application 1 and the second application 2 work on the same principle, in order to avoid redundancy, only One of them is used for illustration, referring to FIG. 9 and FIG. 10 , an embodiment of a specific operation mode of the micro front-end system is given.

First, the shared resource component in the second application 1 is extracted, the shared resource component includes but not limited to the component of the target shared resource. Compared with the situation in the traditional technology that the shared resource component is packaged into an engineering module for separate deployment, Alternatively, in the case of storing the shared resource components in a third-party public shared resource library for their respective references, this embodiment chooses to uniformly store the extracted shared resource components in the shared resource library to provide a similar Content Delivery Network (Content Delivery Network, CDN) shared access can reduce the code volume of compiled shared resource components.

Secondly, after obtaining the address of the shared resource library, the resource module can import the shared resource component into the head tag of the home page HTML of the second application 1 by default, and mount it in the window global object to ensure that the second application 1 is in the independent access scenario It is running normally, and the second application 1 can add the ignore attribute in the imported tag as a distinguishing mark, that is, when the second application 1 is loaded in the micro-frontend system environment, after the analysis of the first application, it will The loading of the resources with the ignore attribute is ignored, and the second application 1 itself can normally load the component resources through the resource module during independent access.

Secondly, the second application 1 registers resource information with the first application through the registration module, and the first application dynamically integrates the pages of the second application 1 through the menu module, that is, the menu module receives the registration information from the second application 1 and performs Conversion, so that the registration information is converted into interface elements to be displayed on the portal unit, and the corresponding resource information is cached for backup;

Among them, the menu information is registered from the second application 1 to the first application by adopting a model-driven message middleware method, and the menu information includes the unique ID of the second application 1, the displayed Chinese and English names, the IP address and the list of shared resources, etc., wherein, The registration module can register the relevant information of the second application 1 to the first application through the message middleware. Specifically, the message middleware deployed in a cluster mode is used to receive menu-related messages and notify the message terminals that monitor menu changes. , in this embodiment, a kafka cluster is used to implement distributed publication and subscription of messages.

Secondly, when the user or terminal clicks on the menu of the second application 1, the page loading process of the second application 1 is triggered, and the resource loading method of the second application 1 is judged, that is, the script of the second application 1 to realize the business function through the function module and style, so as to expose the necessary life cycle function to the first application, so that the first application can identify it under the micro front-end system, and judge whether the registration information has resource information registered on the basis of the life cycle function, if If it is not registered, it will directly load the target shared resource and perform container isolation. On the contrary, if it has been registered, it will send the registered resource information to the resource management device for further processing.

Secondly, within the life cycle of the second application 1 page, the resource management device compares the received resource information with the spare shared resource in the resource loading device, and if the target shared resource corresponding to the resource information has been loaded, directly returns the resource Information, do not process it, otherwise, if the target shared resource corresponding to the resource information has not been loaded, then the target access address corresponding to the target shared resource is dynamically constructed by the resource loading device, and the address is returned to the current HTML of the first application, Introduced by the head tag of the current HTML.

Secondly, the first application requests and imports the target shared resource from the shared resource library according to the address, and mounts it to the window global object for direct calling by the second application 1 .

Finally, the interface elements of the second application 1 are displayed in the DOM container of the first application, and the page rendering of the second application 1 is completed.

As shown in Figure 11, Figure 11 is a flow chart of a resource sharing method provided by another embodiment of the present application, which can be but not limited to be applied to the first application in the micro front-end system shown in the embodiment of Figure 1, the resource sharing The method includes but not limited to steps S600 to S800.

Step S600, obtaining the registration information sent by the second application, the registration information includes resource information, and the resource information is used to characterize the characteristics of the target shared resource that the second application needs to call;

Step S700, sending resource information to the resource management device, so that the resource management device determines a loading strategy for the target shared resource according to the resource information and the backup shared resource;

Step S800, receiving the loading policy sent by the resource management device, and updating the resource loading device according to the loading policy, so that the second application calls the target shared resource from the updated resource loading device.

In one embodiment, the resource management device determines the loading strategy by collecting the registration information of the second application, and updates the resource loading device according to the loading strategy, so that the resource loading device can dynamically introduce the target that the second application needs to call Shared resources, since the first application and the second application are loaded on the same page in the micro-frontend system, the second application can directly call the target shared resource from the resource loading device. Compared with some situations, there is no need to address multiple times Access or cache call resources, so resource sharing can be performed while saving network bandwidth and shortening response delay, which is conducive to improving the execution efficiency of the micro front-end system for resource sharing.

Specifically, as shown in FIG. 12 , the "update resource loading device according to the loading strategy" in step S800 includes but is not limited to step S810.

Step S810, if the target shared resource is not loaded in the resource loading device, import the target shared resource from the shared resource library to the resource loading device according to the loading strategy.

It should be noted that since the resource sharing method in this embodiment and the resource sharing methods in the above-mentioned embodiments belong to the same inventive concept, the only difference is that the execution subject of the resource sharing method in this embodiment is the first For an application, the execution subject of the resource sharing method in the above-mentioned embodiments is the micro front-end system, so the specific implementation manner of the resource sharing method in this embodiment can refer to the specific embodiments of the resource sharing method in the above-mentioned embodiments, In order to avoid redundancy, the specific implementation manner of the resource sharing method in this embodiment will not be repeated here.

As shown in Figure 13, Figure 13 is a flowchart of a resource sharing method provided by another embodiment of the present application, which can be but not limited to be applied to the second application in the micro front-end system shown in the embodiment of Figure 1, the resource sharing The method includes but not limited to steps S900 to S1000.

Step S900, sending registration information to the first application, so that the first application sends resource information to the resource management device, and makes the resource management device determine a loading policy for the target shared resource according to the resource information and the backup shared resource, wherein the registration information includes Resource information, the resource information is used to characterize the characteristics of the target shared resource that the second application needs to call;

Step S1000, call the target shared resource from the updated resource loading device, the updated resource loading device is determined by the first application according to the loading strategy sent by the resource management device.

In one embodiment, the resource management device determines the loading policy by sending the registration information to the first application, and makes the first application update the resource loading device according to the loading policy, so that the resource loading device can dynamically import the resource loaded by the second application as needed. The target shared resource that needs to be called, because the first application and the second application in the micro front-end system are loaded on the same page, so the target shared resource can be called directly from the resource loading device. Access or cache call resources, so resource sharing can be performed while saving network bandwidth and shortening response delay, which is conducive to improving the execution efficiency of the micro front-end system for resource sharing.

Specifically, "sending registration information to the first application" in step S900 includes but is not limited to step S910.

In step S910, the registration information is sent to the first application in a model-driven message middleware manner.

Specifically, step S1100 is also included after step S1000.

Step S1100, display interface elements on the first application, where the interface elements correspond to target shared resources.

It should be noted that since the resource sharing method in this embodiment and the resource sharing methods in the above-mentioned embodiments belong to the same inventive concept, the only difference is that the execution subject of the resource sharing method in this embodiment is the first Two applications, the execution subject of the resource sharing method in the above-mentioned embodiments is the micro front-end system, so the specific implementation manner of the resource sharing method in this embodiment can refer to the specific embodiments of the resource sharing method in the above-mentioned embodiments, In order to avoid redundancy, the specific implementation manner of the resource sharing method in this embodiment will not be repeated here.

In addition, referring to FIG. 14 , an embodiment of the present application also provides a micro front-end system, the micro front-end system includes: a first memory, a first processor, and a A computer program that runs.

The first processor and the first memory may be connected through a first bus or in other ways.

It should be noted that the server in this embodiment can be applied, for example, to the micro front-end system in the embodiment shown in FIG. These embodiments all belong to the same inventive concept, so these embodiments have the same implementation principle and technical effect, and will not be described in detail here.

The non-transitory software programs and instructions required to realize the resource sharing method of the above-mentioned embodiments are stored in the first memory, and when executed by the first processor, the resource sharing methods of the above-mentioned embodiments are executed, for example, the above-described Method steps S100 to S400 in FIG. 3 , method steps S210 to S220 in FIG. 4 , method step S221 in FIG. 5 , method step S310 in FIG. 6 or method step S500 in FIG. 7 .

In addition, referring to FIG. 15 , an embodiment of the present application also provides a network device, which includes: a second memory, a second processor, and a program stored in the second memory and operable on the second processor. Computer program.

The second processor and the second memory may be connected through a second bus or in other ways.

It should be noted that, the network device in this embodiment can be applied, for example, to the micro front-end system in the embodiment shown in Figure 1, and the network device in this embodiment can constitute, for example, the micro front-end system in the embodiment shown in Figure 1 These embodiments all belong to the same inventive concept, so these embodiments have the same implementation principle and technical effect, and will not be described in detail here.

The non-transitory software programs and instructions required to realize the resource sharing method of the above-mentioned embodiments are stored in the second memory, and when executed by the second processor, the resource sharing methods of the above-mentioned embodiments are executed, for example, the above-described Method steps S600 to S800 in FIG. 11 or method step S810 in FIG. 12 .

In addition, referring to FIG. 16 , an embodiment of the present application also provides a network device, the network device includes: a third memory, a third processor, and a program stored in the third memory and operable on the third processor Computer program.

The third processor and the third memory may be connected through a third bus or in other ways.

The non-transitory software programs and instructions required to realize the resource sharing method of the above-mentioned embodiments are stored in the third memory, and when executed by the third processor, the resource sharing methods of the above-mentioned embodiments are executed, for example, the above-described Method steps S900 to S1000, method step S910 or method step S1100 in FIG. 13 .

The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, an embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a first processor, a second processor, and a second processor. Execution by three processors or controllers, for example, being executed by a first processor, a second processor or a third processor in the above-mentioned device embodiment, may cause the above-mentioned first processor, second processor or third processing The device executes the resource sharing method in the above embodiment, for example, executes the method steps S100 to S400 in FIG. 3 described above, the method steps S210 to S220 in FIG. 4 , the method step S221 in FIG. 5 , and the method in FIG. 6 Step S310, method step S500 in FIG. 7, method step S600 to S800 in FIG. 11, method step S810 in FIG. 12, method step S900 to S1000 in FIG. 13, method step S910 or method step S1100.

The embodiment of the present application includes: a resource sharing method applied to a micro front-end system, the micro front-end system includes a first application, a second application and a resource management device, the first application includes a resource loading device configured to load a backup shared resource, and the resource sharing The method includes: the second application sends registration information to the first application, the registration information includes resource information, and the resource information is used to characterize the characteristics of the target shared resource that the second application needs to call; the resource management device receives the resource information sent by the first application , and determine the loading strategy for the target shared resource according to the resource information and the standby shared resource; the first application receives the loading strategy sent by the resource management device, and updates the resource loading device according to the loading strategy; the second application loads the device from the updated resource Invoking the target shared resource. According to the solution provided by the embodiment of the present application, in the micro front-end system, the first application collects the registration information of the second application so that the resource management device determines the loading strategy, and updates the resource loading device according to the loading strategy, so that the resource loading device can press It is necessary to dynamically introduce the target shared resource that the second application needs to call. Since the first application and the second application in the micro-frontend system are loaded on the same page, the second application can directly call the target shared resource from the resource loading device. Compared with some situations, there is no need to perform address access or cache call resources multiple times, so resource sharing can be performed while saving network bandwidth and shortening response delay, which is conducive to improving the execution efficiency of the micro front-end system for resource sharing.

Those skilled in the art can understand that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware and an appropriate combination thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit . Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As known to those of ordinary skill in the art, the term computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer. In addition, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

The above is a specific description of several implementations of the present application, but the application is not limited to the above-mentioned implementations. Those skilled in the art can also make various equivalent deformations or replacements without violating the spirit of the application. Equivalent modifications or replacements are all within the scope defined by the claims of the present application.

Claims

A resource sharing method, applied to a micro front-end system, the micro front-end system includes a first application, a second application and a resource management device, the first application includes a resource loading device configured to load a backup shared resource, the Resource sharing methods include:

The second application sends registration information to the first application, the registration information includes resource information, and the resource information is used to characterize the characteristics of the target shared resource that the second application needs to call;

The resource management device receives the resource information sent by the first application, and determines a loading strategy for the target shared resource according to the resource information and the standby shared resource;

The first application receives the loading policy sent by the resource management device, and updates the resource loading device according to the loading policy;

The second application invokes the target shared resource from the updated resource loading device.
The resource sharing method according to claim 1, wherein the resource management device determines a loading strategy for the target shared resource according to the resource information and the standby shared resource, comprising:

The resource management device determines the loading status of the target shared resource in the resource loading device according to the resource information and the standby shared resource;

The resource management device determines a loading strategy for the target shared resource according to the loading situation.
The resource sharing method according to claim 2, wherein the resource management device determines a loading strategy for the target shared resource according to the loading situation, comprising:

In the case that the target shared resource is not loaded in the resource loading device, the resource management device constructs a target access address corresponding to the target shared resource according to the target shared resource, and embeds the target access address into to the first application.
The resource sharing method according to claim 3, wherein the micro front end system further comprises a shared resource library for storing shared resources;

The first application updating the resource loading device according to the loading strategy includes:

The first application imports the target shared resource from the shared resource library according to the target access address, and sends the target shared resource to the resource loading device.
The resource sharing method according to claim 1, wherein the second application sends registration information to the first application, comprising:

The second application sends registration information to the first application in a model-driven message middleware manner.
The resource sharing method according to claim 1, wherein, after the second application invokes the target shared resource from the updated resource loading device, further comprising:

The first application presents an interface element of the second application, the interface element corresponding to the target shared resource.
A resource sharing method, applied to a first application in a micro front end system, the first application includes a resource loading device configured to load a spare shared resource, the micro front end system further includes a second application and a resource management device, The resource sharing method includes:

Acquire registration information sent by the second application, where the registration information includes resource information, and the resource information is used to characterize the characteristics of the target shared resource that the second application needs to call;

sending the resource information to a resource management device, so that the resource management device determines a loading strategy for the target shared resource according to the resource information and the standby shared resource;

receiving the loading strategy sent by the resource management device, and updating the resource loading device according to the loading strategy, so that the second application calls the target shared resource from the updated resource loading device .
The resource sharing method according to claim 7, wherein the micro front end system further comprises a shared resource library for storing shared resources;

The updating the resource loading device according to the loading strategy includes:

In the case that the target shared resource is not loaded in the resource loading device, import the target shared resource from the shared resource library to the resource loading device according to the loading strategy.
A resource sharing method, applied to a second application in a micro front-end system, the micro front-end system also includes a first application and a resource management device, the first application includes a resource loading device configured to load a standby shared resource, The resource sharing method includes:

sending registration information to the first application, so that the first application sends resource information to the resource management device, and makes the resource management device determine the target shared resource according to the resource information and the standby shared resource The loading policy, wherein the registration information includes resource information, and the resource information is used to characterize the characteristics of the target shared resource that the second application needs to call;

calling the target shared resource from the updated resource loading means determined by the first application according to the loading policy sent by the resource management means.
The resource sharing method according to claim 9, wherein the sending registration information to the first application comprises:

The registration information is sent to the first application in a model-driven message middleware manner.
The resource sharing method according to claim 9, wherein the calling the target shared resource from the updated resource loading device further comprises:

Displaying an interface element on the first application, the interface element corresponding to the target shared resource.
A micro front end system, comprising: a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein, when the processor executes the computer program, any one of claims 1 to 6 is realized. The resource sharing method described in the item.
A network device, comprising: a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein, when the processor executes the computer program, the method described in claim 7 or 8 is realized A resource sharing method, or implement the resource sharing method according to any one of claims 9-11.
A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the resource sharing method according to any one of claims 1 to 6, or to execute claim 7 or 8 The resource sharing method, or execute the resource sharing method described in any one of claims 9 to 11.