CN112416415A - Front-end micro-service implementation method and related components - Google Patents
Front-end micro-service implementation method and related components Download PDFInfo
- Publication number
- CN112416415A CN112416415A CN202010986670.0A CN202010986670A CN112416415A CN 112416415 A CN112416415 A CN 112416415A CN 202010986670 A CN202010986670 A CN 202010986670A CN 112416415 A CN112416415 A CN 112416415A
- Authority
- CN
- China
- Prior art keywords
- application
- sub
- global
- service
- base
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000008859 change Effects 0.000 claims description 16
- 244000035744 Hura crepitans Species 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 4
- 238000012544 monitoring process Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 abstract description 9
- 238000011161 development Methods 0.000 abstract description 6
- 238000012423 maintenance Methods 0.000 abstract description 5
- 230000008878 coupling Effects 0.000 abstract description 3
- 238000010168 coupling process Methods 0.000 abstract description 3
- 238000005859 coupling reaction Methods 0.000 abstract description 3
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 5
- 238000010276 construction Methods 0.000 description 4
- 238000013461 design Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000035515 penetration Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a front-end micro-service implementation method, which provides an independent and complete front-end micro-service architecture, does not need to be assisted or supported by the front-end service architecture, and can ensure the efficient management of the front-end micro-service by constructing a base and uniformly managing the loading and running of each sub-application through the base; meanwhile, when the life cycle management is carried out on the sub-application in the method, the life cycle is placed in the base, so that the problem of framework complexity which is easy to occur in the existing service framework can be avoided; and the corresponding processing mode is called for different management requirements of the sub-application to carry out corresponding service processing, so that the code is divided according to the service, the code coupling can be reduced, the development and the maintenance are convenient, the independent upgrade can be carried out, the product agility is enhanced, and the development efficiency is improved. The application also provides a front-end micro-service implementation device, equipment and a readable storage medium, and the device and the equipment have the beneficial effects.
Description
Technical Field
The present application relates to the field of computer software technologies, and in particular, to a method, an apparatus, a device, and a readable storage medium for implementing front-end micro-services.
Background
With the business penetration of more and more companies, the size and complexity of products or projects are continuously increasing. In order to adapt to the overall business requirements, a project often comprises a plurality of sub-project systems, and different modules are divided under each project according to specific businesses. While multiple projects may require maintenance updates by multiple different teams. These items may all have personalized business designs. How to keep the projects maintained by the various teams reasonably together becomes an important issue to be faced.
The front-end micro-service is applied to solving the problem of multi-project maintenance due to the advantages of controllable complexity, flexible module deployment, independent deployment, flexible technology type selection, good fault tolerance, strong expandability and the like, and the framework comprising Vue, React and Angular is widely applied as a front-end mainstream framework.
Currently, a Single-span web application rich application (Single-page web application) is commonly used in the existing front-end micro-service scheme, which can support most of mainstream front-end frames and also can support traditional front-end frames, does not need page jump during use, is directly loaded in the current page, is convenient for migrating old legacy systems, and provides better user experience; however, the system of the Single-SPA is complex to construct, the applications need to be integrated together for construction, the deployment and separation of different applications are not supported, the code structure is complex, and the learning cost is high.
Therefore, how to solve the problem of complexity of construction existing in the current front-end micro-service scheme and ensure excellent sub-application management efficiency is a problem that needs to be solved urgently by the technical personnel in the field.
Disclosure of Invention
The method can solve the problem of construction complexity existing in the current front-end micro-service scheme and ensure excellent sub-application management efficiency; another object of the present application is to provide a front-end microservice implementing apparatus, a device and a readable storage medium.
In order to solve the above technical problem, the present application provides a method for implementing a front-end micro service, including:
a base loads a global registration center; the global registry is an application registry which is created in advance and used for storing information of each sub-application;
loading a sub-application according to the global registry to respond to a service request;
and regularly pulling the latest sub-application configuration information, and calling a life cycle management application according to the sub-application configuration information to carry out life cycle management on the operation of each sub-application.
Optionally, the step of loading a global registry by the base and responding to the service request according to the global registry loading sub-application includes:
and the base loads the global registry from the global object and loads the sub-application according to the global registry to respond to the service request.
Optionally, the front-end micro-service implementation method further includes:
the base receives a variable change notification; wherein the variable is a global variable in a global variable pool;
determining a pre-registered observer corresponding to the changed variable;
broadcasting a notification to the observer that the global variable has changed.
Optionally, the front-end micro-service implementation method further includes:
monitoring the routing change of each sub-application;
if the situation that the route is switched from a first sub-application to a second sub-application is monitored, calling the life cycle management application to load the second sub-application, and unloading the first sub-application;
and calling the sandbox application to create the global variable and the independent operation environment of the second sub-application.
Optionally, the front-end micro-service implementation method further includes:
after receiving a simultaneous display instruction of multiple sub-applications, designating a dom element according to the identifier of each sub-application designated to be displayed simultaneously;
triggering the starting of the sub-application after receiving the sub-application operation instruction;
and unloading the sub-application after receiving a sub-application closing instruction.
Optionally, the front-end micro-service implementation method further includes:
judging whether a plurality of sub-applications exist under one page;
if a plurality of sub-applications exist in one page, judging whether the sub-applications have the same third-party dependence or not according to a pre-maintained third-party dependence list;
if the sub-applications have the same third-party dependence, the third-party dependence is uniformly imported into the base.
Optionally, before the base loads the global registry, the method further includes:
identifying an operation mode indicated by a mode operation global variable; the operation modes comprise an independent operation mode and a micro front end application mode;
and if the mode is the micro front-end application mode, executing the step of loading the global registration center by the base.
The application also provides a device is realized to little service of front end, and the device includes:
the registration loading unit is used for loading the global registration center by the base; the global registry is an application registry which is created in advance and used for storing information of each sub-application;
the sub-application calling unit is used for loading the sub-application according to the global registration center to respond to the service request;
and the life cycle management unit is used for periodically pulling the latest sub-application configuration information and calling the life cycle management application to carry out life cycle management on the operation of each sub-application according to the sub-application configuration information.
The application also provides a front-end micro-service implementation device, including:
a memory for storing a computer program;
and the processor is used for realizing the steps of the front-end micro-service realizing method when executing the computer program.
The present application further provides a readable storage medium having a program stored thereon, where the program, when executed by a processor, implements the steps of the front-end micro-service implementation method.
The front-end micro-service implementation method provided by the application provides an independent and complete front-end micro-service architecture, does not need to be assisted or supported by the front-end service architecture, and can ensure the efficient management of the front-end micro-service by constructing a base and uniformly managing the loading and running of each sub-application through the base; meanwhile, when the life cycle management is carried out on the sub-application in the method, the life cycle is placed in the base, so that the problem of framework complexity which is easy to occur in the existing service framework can be avoided; and the corresponding processing mode is called for different management requirements of the sub-application to carry out corresponding service processing, so that the code is divided according to the service, the code coupling can be reduced, the development and the maintenance are convenient, the independent upgrade can be carried out, the product agility is enhanced, and the development efficiency is improved.
The application also provides a front-end micro-service implementation device, equipment and a readable storage medium, which have the beneficial effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a front-end micro-service implementation method provided in an embodiment of the present application;
fig. 2 is a schematic view illustrating life cycle management of a sub-application under a micro service architecture according to an embodiment of the present application;
fig. 3 is a block diagram illustrating a front-end microservice implementing apparatus according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of a front-end micro-service implementing device according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a front-end micro-service implementation method, which can solve the problem of construction complexity in the current front-end micro-service scheme and ensure excellent sub-application management efficiency; the other core of the application is to provide a front-end micro-service implementation device, equipment and a readable storage medium.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for implementing front-end micro-services according to this embodiment, where the method mainly includes the following steps:
step s110, loading a global registration center by a base; the global registry is an application registry which is created in advance and used for storing information of each sub-application;
the base is one application in the front-end micro service, two relations exist between the applications of the micro front-end, namely a base mode and a self-organizing mode.
A file folder is created in a base and used as an application registry, a configuration file related to a micro front-end framework is initialized, the file is mainly used for storing sub-application information, the sub-application information can mainly comprise information of each application and an entrance of the corresponding application, and the file plays a role of a global registry. The global registry may be embodied in the form of a JSON file.
After the application is built or deployed to a server, the application is registered in the application registry, and the call of the base can be accepted to provide access rights for other applications in time.
The base calls the sub-applications based on the global registration center, and the global registration center is loaded when the base runs, so that the overall control scheduling of each sub-application is realized. And the overall control of the system behavior is realized through the global control scheduling of the sub-applications.
Step s120, loading the sub-application according to the global registry to respond to the service request;
after the service request is received, the corresponding sub-application is loaded according to the sub-application interface in the global registry to respond to the service request, and the base can uniformly manage the sub-applications.
Optionally, in order to facilitate subsequent base call, the global registry may be mounted to a global object, where the global object is, for example, a window object of a browser itself, a prototype chain, or a local cache, and this is not limited in this embodiment, and the base loads the global registry from the global object and responds to a service request according to a global registry loading sub-application, and may effectively improve a call speed of the global registry.
And step s130, periodically pulling the latest sub-application configuration information, and calling the life cycle management application to perform life cycle management on the operation of each sub-application according to the sub-application configuration information.
The base may further pull up the latest sub-application configuration information from the server during running, and call the lifecycle management application to perform lifecycle management on the running of each sub-application according to the sub-application configuration information, where the lifecycle management mainly includes initialization, running, stopping, and triggering of a completion state of the sub-application, and the like, as shown in fig. 2, a sub-application lifecycle management diagram under a micro-service architecture may be implemented, referring to fig. 2, to perform lifecycle management on the sub-application.
Optionally, in order to increase the running speed of the sub-application, the lifecycle management application may load the static resource information of the sub-application when the lifecycle management application starts to enter the initialization stage, so as to increase the loading speed and the running speed of the sub-application.
Based on the above description, the front-end micro-service implementation method provided in this embodiment provides an independent and complete front-end micro-service architecture, which does not need to be assisted or supported by the front-end service architecture, and by constructing a base, the loading and running of each sub-application are uniformly managed by the base, so that efficient management of the front-end micro-service can be ensured; meanwhile, when the life cycle management is carried out on the sub-application in the method, the life cycle is placed in the base, so that the problem of framework complexity which is easy to occur in the existing service framework can be avoided; and the corresponding processing mode is called for different management requirements of the sub-application to carry out corresponding service processing, so that the code is divided according to the service, the code coupling can be reduced, the development and the maintenance are convenient, the independent upgrade can be carried out, the product agility is enhanced, and the development efficiency is improved.
Based on the foregoing embodiments, several service processing manners for improving management efficiency under the front-end micro service are mainly described in this embodiment.
In addition to the sub-application loading and lifecycle management provided by the above embodiments, the following steps may also be performed:
(1.1) the base receiving a variable change notification;
and the base maintains the global variable pool so as to respond to the variable calling request of each sub-application.
(1.2) determining a pre-registered observer corresponding to the changed variable;
the global variable change notification may be sent by the sub-application that causes the global variable change, or may be sent by the variable monitoring end, which is not limited in this embodiment.
(1.3) broadcasting a notification to the observer that the global variable has changed.
The base is also responsible for managing communications between applications: the base maintains a global variable pool, the sub-applications can register observers, the base is informed when the variables change during the operation of the sub-applications, and the base can broadcast and inform all observer lists of the variables after the variables change, so that each sub-application can timely sense the change of the variables.
Optionally, on the basis of the above embodiment, the following steps may be further performed:
(2.1) monitoring the route change of each sub-application;
each sub-application monitors the routing change of the base in the micro front-end application mode, because the sub-applications are only independent applications, the user does not need to pay attention to the change of the non-independent applications, but when the base is applied, the user needs to monitor the routing change of the base, because the user may click the base when in use, and if the sub-applications are not monitored, the routing can not be skipped normally.
(2.2) if the routing is monitored to be switched from the first sub-application to the second sub-application, calling the life cycle management application to load the second sub-application, and unloading the first sub-application;
when the routing is switched to the designated sub-application, the lifecycle management application starts loading the corresponding sub-application and uninstalls the old application.
And (2.3) calling the sandbox application to create the global variable of the second sub-application and the independent work environment.
The sandbox can enable the program to run in an isolated environment without influencing other programs, and the program running in the sandbox cannot permanently influence the hard disk by creating an independent operation environment similar to the sandbox.
When the sandbox application is called, a routing sandbox mode of the routing parent-child application is executed, the mode refers to that the child application additionally monitors the change of the base routing, the address is sent to the main base as a message after a new routing is generated, the state change in the child application is reflected to the child routing sandbox of the child application, the base monitors the message from the child routing, and the routing of the base is changed after the new routing is obtained.
The sandbox can be constructed in a compiling mode, a native object basic operation environment of the browser is wrapped into an action domain through a webpack closure during compiling, a simulated native browser object can be called during sub-application loading, and the sandbox can be achieved through a Javascript closure.
Optionally, on the basis of the above embodiment, the following steps may be further performed:
(3.1) after receiving a simultaneous display instruction of a plurality of sub-applications, designating a dom element according to the identifier of each sub-application designated to be displayed simultaneously;
(3.2) after receiving the sub-application operation instruction, triggering the starting of the sub-application;
and (3.3) unloading the sub-application after receiving the sub-application closing instruction.
When a plurality of sub-applications need to be displayed simultaneously, in order to ensure efficient management of the plurality of sub-applications simultaneously, a processing means is provided in this embodiment, a dom element is designated according to an identifier of the sub-application, when a user operates the application, the start of the application is triggered, the uninstallation of the application is supported, the management completed for each sub-application is performed, and the normal operation of each sub-application is ensured.
Optionally, on the basis of the above embodiment, the following steps may be further performed:
(4.1) judging whether a plurality of sub-applications exist under one page;
(4.2) if a plurality of sub-applications exist in one page, judging whether the sub-applications have the same third party dependence according to a pre-maintained third party dependence list;
and (4.3) if the same third-party dependence exists in each sub-application, uniformly importing the third-party dependence into the base.
The base can further maintain a third party dependency list, the sub-applications can check whether multiple applications exist in one page or not in advance, whether multiple identical third party dependencies exist in the applications or not, when the third party plugin is needed by different sub-applications, the third party dependencies are uniformly imported into the base applications, conflicts caused by multiple references of one plugin on one page are avoided, and the running stability of the system is improved.
Optionally, before the base loads the global registry in the above embodiment, the following steps may be further performed:
(5.1) identifying an operation mode indicated by the global variable of mode operation; the operation modes comprise an independent operation mode and a micro front end application mode;
and (5.2) if the mode is the micro front-end application mode, executing the step of loading the global registry by the base.
The method includes the steps that a global variable is bound in a base, when the variable is true, the variable is in an independent operation mode, when the variable is false, the variable is in a micro front-end application mode, whether the current application is an independent application or an application of a micro front-end framework is judged according to the type of the variable, micro service can be achieved according to a traditional operation mode in the independent operation mode, and if the variable is in the micro front-end application mode, the method introduced in the embodiment is executed.
According to the method, the operation mode is specified by setting the global variable, the coexistence of a traditional service mode and a micro front-end application mode can be realized, and various possible ways are provided for the operation of the system and the sub-application, so that different modes can be called according to actual operation and use requirements, and the management efficiency and the user experience are improved.
Based on the above description, in the full-segment micro-service implementation method provided in this embodiment, a base is constructed to perform unified registration management, and the base is deployed according to a routing sandbox mode of a routing parent-child application, an observer of a variable in a base system is registered in a child application, when the variable in the base application changes, the observer in the child application is notified, an operation is triggered, and meanwhile, a lifecycle management application and the sandbox application are matched to complete framework work of a micro front end.
Referring to fig. 3, fig. 3 is a block diagram of a front-end microservice implementing apparatus according to the present embodiment; the device mainly includes: a registration loading unit 110, a sub-application calling unit 120, and a life cycle management unit 130. The front-end micro-service implementation apparatus provided in this embodiment may be contrasted with the front-end micro-service implementation method.
The registration loading unit 110 is mainly used for loading a global registration center on a base; the global registry is an application registry which is created in advance and used for storing information of each sub-application;
the sub-application calling unit 120 is mainly configured to load a sub-application according to the global registry to respond to the service request;
the lifecycle management unit 130 is mainly configured to periodically pull the latest sub-application configuration information, and invoke the lifecycle management application to perform lifecycle management on the operation of each sub-application according to the sub-application configuration information.
The embodiment provides a front-end micro-service implementation device, which mainly includes: a memory and a processor.
Wherein, the memory is used for storing programs;
the processor is configured to implement the steps of the front-end micro-service implementation method described in the above embodiments when executing the program, and may refer to the description of the front-end micro-service implementation method.
Referring to fig. 4, a schematic structural diagram of a front-end micro-service implementing device provided in this embodiment is shown, where the front-end micro-service implementing device may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors) and a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) storing an application 342 or data 344. Memory 332 and storage media 330 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instructions operating on a data processing device. Still further, the central processor 322 may be configured to communicate with the storage medium 330 to execute a series of instruction operations in the storage medium 330 on the front-end micro-service implementing device 301.
The front-end micro-service implementation device 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and the like.
The steps in the front-end micro-service implementation method described in fig. 1 above can be implemented by the structure of the front-end micro-service implementation apparatus described in this embodiment.
The present embodiment discloses a readable storage medium, on which a program is stored, and the program, when executed by a processor, implements the steps of the front-end micro-service implementing method described in the above embodiments, which may be referred to in the description of the front-end micro-service implementing method in the above embodiments.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The method, apparatus, device and readable storage medium for implementing front-end micro-service provided in the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A method for implementing front-end micro-services, the method comprising:
a base loads a global registration center; the global registry is an application registry which is created in advance and used for storing information of each sub-application;
loading a sub-application according to the global registry to respond to a service request;
and regularly pulling the latest sub-application configuration information, and calling a life cycle management application according to the sub-application configuration information to carry out life cycle management on the operation of each sub-application.
2. The front-end microservice implementation method of claim 1, wherein a base loads a global registry and loads sub-applications according to the global registry to respond to service requests, comprising:
and the base loads the global registry from the global object and loads the sub-application according to the global registry to respond to the service request.
3. The front-end micro-service implementation method of claim 1, further comprising:
the base receives a variable change notification; wherein the variable is a global variable in a global variable pool;
determining a pre-registered observer corresponding to the changed variable;
broadcasting a notification to the observer that the global variable has changed.
4. The front-end micro-service implementation method of claim 1, further comprising:
monitoring the routing change of each sub-application;
if the situation that the route is switched from a first sub-application to a second sub-application is monitored, calling the life cycle management application to load the second sub-application, and unloading the first sub-application;
and calling the sandbox application to create the global variable and the independent operation environment of the second sub-application.
5. The front-end micro-service implementation method of claim 1, further comprising:
after receiving a simultaneous display instruction of multiple sub-applications, designating a dom element according to the identifier of each sub-application designated to be displayed simultaneously;
triggering the starting of the sub-application after receiving the sub-application operation instruction;
and unloading the sub-application after receiving a sub-application closing instruction.
6. The front-end micro-service implementation method of claim 1, further comprising:
judging whether a plurality of sub-applications exist under one page;
if a plurality of sub-applications exist in one page, judging whether the sub-applications have the same third-party dependence or not according to a pre-maintained third-party dependence list;
if the sub-applications have the same third-party dependence, the third-party dependence is uniformly imported into the base.
7. The front-end microservices implementation method of claim 1 wherein prior to the base loading the global registry, further comprising:
identifying an operation mode indicated by a mode operation global variable; the operation modes comprise an independent operation mode and a micro front end application mode;
and if the mode is the micro front-end application mode, executing the step of loading the global registration center by the base.
8. A front-end microservice implementation apparatus, comprising:
the registration loading unit is used for loading the global registration center by the base; the global registry is an application registry which is created in advance and used for storing information of each sub-application;
the sub-application calling unit is used for loading the sub-application according to the global registration center to respond to the service request;
and the life cycle management unit is used for periodically pulling the latest sub-application configuration information and calling the life cycle management application to carry out life cycle management on the operation of each sub-application according to the sub-application configuration information.
9. A front-end micro-service implementation device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the front-end micro-service implementation method as claimed in any one of claims 1 to 7 when executing said computer program.
10. A readable storage medium, having stored thereon a program which, when executed by a processor, carries out the steps of the front-end micro-service implementation method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010986670.0A CN112416415A (en) | 2020-09-18 | 2020-09-18 | Front-end micro-service implementation method and related components |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010986670.0A CN112416415A (en) | 2020-09-18 | 2020-09-18 | Front-end micro-service implementation method and related components |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112416415A true CN112416415A (en) | 2021-02-26 |
Family
ID=74854922
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010986670.0A Pending CN112416415A (en) | 2020-09-18 | 2020-09-18 | Front-end micro-service implementation method and related components |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112416415A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113221097A (en) * | 2021-05-10 | 2021-08-06 | 挂号网（杭州）科技有限公司 | Code execution method and device, electronic terminal and storage medium |
| CN113254237A (en) * | 2021-06-11 | 2021-08-13 | 海尔数字科技(青岛)有限公司 | Front-end application calling method, device, storage medium and program product |
| CN113419817A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Front-end application nesting method, device, equipment and storage medium |
| CN113448702A (en) * | 2021-06-16 | 2021-09-28 | 浪潮软件股份有限公司 | Front-end-based micro-service design method |
| CN113687856A (en) * | 2021-06-24 | 2021-11-23 | 广州欢网科技有限责任公司 | Method and apparatus for granulating systems |
| CN114327687A (en) * | 2022-03-09 | 2022-04-12 | 恒生电子股份有限公司 | Method, device and equipment for constructing sub-application in micro front-end mode and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140373027A1 (en) * | 2013-06-14 | 2014-12-18 | Microsoft Corporation | Application lifetime management |
| US20190087178A1 (en) * | 2017-09-18 | 2019-03-21 | International Business Machines Corporation | Adaptable management of web application state in a micro-service architecture |
| CN110708368A (en) * | 2019-09-25 | 2020-01-17 | 北京计算机技术及应用研究所 | Micro front-end system and method based on routing distribution |
| CN111666585A (en) * | 2020-04-16 | 2020-09-15 | 北京百度网讯科技有限公司 | Method and device for accessing sub-application, electronic equipment and readable storage medium |
-
2020
- 2020-09-18 CN CN202010986670.0A patent/CN112416415A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140373027A1 (en) * | 2013-06-14 | 2014-12-18 | Microsoft Corporation | Application lifetime management |
| US20190087178A1 (en) * | 2017-09-18 | 2019-03-21 | International Business Machines Corporation | Adaptable management of web application state in a micro-service architecture |
| CN110708368A (en) * | 2019-09-25 | 2020-01-17 | 北京计算机技术及应用研究所 | Micro front-end system and method based on routing distribution |
| CN111666585A (en) * | 2020-04-16 | 2020-09-15 | 北京百度网讯科技有限公司 | Method and device for accessing sub-application, electronic equipment and readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 刘一田, 曹一鸣: "微前端化微应用管理控制台", 计算机***应用 * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113221097A (en) * | 2021-05-10 | 2021-08-06 | 挂号网（杭州）科技有限公司 | Code execution method and device, electronic terminal and storage medium |
| CN113254237A (en) * | 2021-06-11 | 2021-08-13 | 海尔数字科技(青岛)有限公司 | Front-end application calling method, device, storage medium and program product |
| CN113448702A (en) * | 2021-06-16 | 2021-09-28 | 浪潮软件股份有限公司 | Front-end-based micro-service design method |
| CN113419817A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Front-end application nesting method, device, equipment and storage medium |
| CN113419817B (en) * | 2021-06-22 | 2024-04-05 | 康键信息技术（深圳）有限公司 | Front-end application nesting method, device, equipment and storage medium |
| CN113687856A (en) * | 2021-06-24 | 2021-11-23 | 广州欢网科技有限责任公司 | Method and apparatus for granulating systems |
| CN114327687A (en) * | 2022-03-09 | 2022-04-12 | 恒生电子股份有限公司 | Method, device and equipment for constructing sub-application in micro front-end mode and storage medium |
| CN114327687B (en) * | 2022-03-09 | 2022-05-20 | 恒生电子股份有限公司 | Method, device and equipment for constructing sub-application in micro front-end mode and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112416415A (en) | Front-end micro-service implementation method and related components | |
| CN107479867B (en) | Application software plug-in operation method and device | |
| CN107092473B (en) | Desktop application development method and device | |
| CN109688191B (en) | Traffic scheduling method and communication device | |
| US8910170B2 (en) | Managing execution of interdependent tasks of a task dependency chain based on a run-once task attribute | |
| CN114077423A (en) | Airport APP development container architecture based on mobile cross-platform | |
| US20180157557A1 (en) | Determining reboot time after system update | |
| CN108132878A (en) | The dispatching method and system of a kind of test environment | |
| CN110609755A (en) | Message processing method, device, equipment and medium for cross-block chain node | |
| CN113448686A (en) | Resource deployment method and device, electronic equipment and storage medium | |
| CN111737275A (en) | Database update event processing method and device and computer readable storage medium | |
| CN112114939A (en) | Distributed system deployment equipment and method | |
| CN114968406A (en) | Plug-in management method and device, electronic equipment and storage medium | |
| CN108287737B (en) | Service Worker starting method and device and electronic equipment | |
| CN113448650A (en) | Live broadcast function plug-in loading method, device, equipment and storage medium | |
| CN115390897B (en) | Micro front end management method, micro front end management device, electronic equipment and storage medium | |
| CN110599112B (en) | Network page development and maintenance method and device | |
| CN104750553A (en) | Application operating method and device | |
| CN116382694A (en) | Method for improving compiling speed of Maven engineering in container environment | |
| CN115509531A (en) | Micro front end implementation method, device, terminal and storage medium based on front end technology | |
| Feitosa et al. | Patterns and Energy Consumption: Design, Implementation, Studies, and Stories | |
| CN115146198A (en) | Simple browser implementation method and system based on Electron | |
| CN112667491B (en) | Function test method and device for virtual machine | |
| CN111858234A (en) | Task execution method, device, equipment and medium | |
| CN114240265B (en) | Product deployment method and device based on mixed environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210226 |