CN117290013A - Front-end application management method, system, electronic equipment and medium - Google Patents

Front-end application management method, system, electronic equipment and medium Download PDF

Info

Publication number
CN117290013A
CN117290013A CN202311347520.5A CN202311347520A CN117290013A CN 117290013 A CN117290013 A CN 117290013A CN 202311347520 A CN202311347520 A CN 202311347520A CN 117290013 A CN117290013 A CN 117290013A
Authority
CN
China
Prior art keywords
application
micro
communication interface
management method
module
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
Application number
CN202311347520.5A
Other languages
Chinese (zh)
Inventor
胡佐治
严哲
王焰
吴连谱
樊佳冉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Waigaoqiao Shipbuilding And Offshore Engineering Co ltd
Original Assignee
Shanghai Waigaoqiao Shipbuilding And Offshore Engineering Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Waigaoqiao Shipbuilding And Offshore Engineering Co ltd filed Critical Shanghai Waigaoqiao Shipbuilding And Offshore Engineering Co ltd
Priority to CN202311347520.5A priority Critical patent/CN117290013A/en
Publication of CN117290013A publication Critical patent/CN117290013A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/543—User-generated data transfer, e.g. clipboards, dynamic data exchange [DDE], object linking and embedding [OLE]

Abstract

The invention discloses a front-end application management method, a system, electronic equipment and a medium, wherein the front-end application management method comprises the following steps: a communication interface integrating the host application and at least two micro applications; acquiring a route change message through a communication interface of a main application; determining the micro application to be jumped according to the route change information; and loading the corresponding micro-application through the communication interface of the micro-application to be jumped. According to the invention, through integrating the communication interfaces of the main application and the front-end multiple micro applications, the front-end system can uniformly load and schedule the front-end micro applications through the main application, and the micro applications are mutually independent, so that the front-end micro applications can be developed in parallel, the development efficiency is improved, the invasiveness to codes is reduced, and the experience of a user in using the micro applications can be improved.

Description

Front-end application management method, system, electronic equipment and medium
Technical Field
The present invention relates to the field of software technologies, and in particular, to a front end application management method, system, electronic device, and medium.
Background
The software front-end usually has a plurality of application functions, and if a user needs to switch applications, the application functions can be realized by embedding addresses of micro applications in a main application in a development stage. But this approach not only increases the complexity of front-end application development and reduces development efficiency, but also makes it difficult to manage and maintain different types of micro-applications at the front end later.
Disclosure of Invention
The invention aims to overcome the defects of low development efficiency and difficult maintenance of front-end application in the prior art, and provides a front-end application management method, a system, electronic equipment and a medium.
The invention solves the technical problems by the following technical scheme:
the invention provides a front-end application management method, which is applied to a front-end system comprising a main application and at least two micro applications, and comprises the following steps:
integrating the communication interfaces of the host application and the at least two micro applications;
acquiring a route change message through a communication interface of a main application;
determining the micro application to be jumped according to the route change message;
and loading the corresponding micro-application through the communication interface of the micro-application to be jumped.
Preferably, the front-end application management method further includes:
acquiring a routing event through a communication interface of a first micro application;
determining an execution action according to the routing event, wherein the execution action comprises loading the first micro-application through a communication interface of the first micro-application or jumping to a second micro-application through a communication interface of the second micro-application.
Preferably, the front-end application management method further includes:
and integrating the micro application into an interface of the main application according to a preset layout.
Preferably, the step of loading the corresponding micro-application through the communication interface of the micro-application to be skipped further includes:
and when the micro-application version to be jumped is updated, loading the micro-application of the new version through the communication interface of the micro-application to be jumped.
The invention also provides a front-end application management system, which is applied to a front-end system comprising a main application and at least two micro applications, and comprises:
the integration module is used for integrating the communication interfaces of the main application and the at least two micro applications;
the acquisition module is used for acquiring the route change message through the communication interface of the main application;
the determining module is used for determining the micro application to be skipped according to the route change message;
and the loading module is used for loading the corresponding micro-application through the communication interface of the micro-application to be jumped.
Preferably, the acquiring module is further configured to acquire the routing event through a communication interface of the first micro application;
the determining module is further configured to determine, according to the routing event, an execution action, where the execution action includes loading the first micro-application through a communication interface of the first micro-application or jumping to the second micro-application through a communication interface of the second micro-application.
Preferably, the integration module is further configured to integrate the micro-application into an interface of the host application according to a preset layout.
Preferably, the loading module is further configured to load a new version of the micro-application through the communication interface of the micro-application to be skipped when the micro-application version to be skipped is updated.
The invention also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and used for running on the processor, wherein the front-end application management method is realized when the processor executes the computer program.
The present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the front-end application management method described above.
On the basis of conforming to the common knowledge in the field, the above preferred conditions can be arbitrarily combined to obtain the preferred examples of the invention.
The invention has the positive progress effects that:
according to the invention, through integrating the communication interfaces of the main application and the front-end multiple micro applications, the front-end system can uniformly load and schedule the front-end micro applications through the main application, and the micro applications are mutually independent, so that the front-end micro applications can be developed in parallel, the development efficiency is improved, the invasiveness to codes is reduced, and the experience of a user in using the micro applications can be improved.
Drawings
FIG. 1 is a flow chart of a front end application management method according to embodiment 1 of the present invention;
fig. 2 is a configuration diagram of a front-end application program of a specific example of a front-end application management method of embodiment 1 of the present invention;
fig. 3 is a flowchart of a front-end application program when a route is changed according to a specific example of the front-end application management method in embodiment 1 of the present invention:
FIG. 4 is a block diagram of a front-end application management system according to embodiment 2 of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to embodiment 3 of the present invention.
Detailed Description
The invention is further illustrated by means of the following examples, which are not intended to limit the scope of the invention.
Example 1
The embodiment provides a front-end application management method, which is applied to a front-end system comprising a main application and at least two micro applications, wherein the micro applications are divided according to service functions, and the front-end system respectively provides communication interfaces for the micro applications and the main application, so that the micro applications and the main applications are allowed to communicate and coordinate with each other when needed, and further complex functions are realized. Referring to fig. 1, the front-end application management method includes:
s1, integrating communication interfaces of a main application and at least two micro applications.
S2, obtaining the route change message through the communication interface of the main application.
S3, determining the micro application to be jumped according to the route change message.
S4, loading the corresponding micro-application through the communication interface of the micro-application to be jumped.
In this embodiment, through integrating the communication interfaces of the main application and the front-end multiple micro applications, the front-end system can uniformly load and schedule the front-end micro applications through the main application, and the micro applications are mutually independent, so that the front-end micro applications can be developed in parallel, the development efficiency is improved, the invasiveness to codes is reduced, and the experience of using the micro applications by users can be improved.
In an alternative embodiment, the front-end application management method further includes:
s5, acquiring a routing event through a communication interface of the first micro application.
S6, determining to execute the action according to the routing event.
Performing the action includes at least one of the following two steps:
s61, loading the first micro-application through a communication interface of the first micro-application.
S62, jumping to the second micro-application through the communication interface of the second micro-application.
It should be noted that "first" and "second" are used herein only to distinguish different micro-applications.
In the embodiment, the micro applications can also perform unified communication and coordination through the integrated communication interface, so that different micro application modules can be more flexibly combined and deployed according to the function requirements, and better user experience is provided.
In an alternative embodiment, the front-end application management method further includes:
and integrating the micro-application into the interface of the main application according to the preset layout.
In the embodiment, the front-end application adopts a loosely coupled architecture to lay out the micro-application and the main application, which is not only beneficial to parallel development of the micro-application and acceleration of development process, but also enables the micro-application to independently update and maintain without affecting the stability of the main application.
In an alternative embodiment, step S4 further comprises:
s41, when the micro-application version to be jumped is updated, loading the micro-application of the new version through the communication interface of the micro-application to be jumped.
In the embodiment, by loading the latest version of the micro application, better user experience is further provided.
A specific example is described below to describe in detail the front-end application management method of the present embodiment. Fig. 2 is a schematic diagram of a front-end application, wherein the layout module 204 and the micro-application module 201 include a configuration file (acconfig) and script styles (scripts), respectively. The flow of a specific example is as follows:
s100, dividing the front-end application into a plurality of independent micro application modules 201.
S101, a communication interface is provided for each micro application module 201 to enable communication and coordination between the main application module 202 and the micro application module 201 or between the micro application modules 201, and the communication interface is integrated into the routing module 203.
S102, developing different micro-application modules 201, main application modules 202 and layout modules 204 in parallel.
S103, integrating each micro-application module 201, and the layout module 204 into the main application module 202.
S104, deploying the architecture of the whole front-end application program into a server.
The main application module 202 is used for integrating and controlling the layout module 204, the routing module 203 and the micro application module 201. The host application module 202 may maintain a registry of the micro-application modules 201, manage the lifecycle of each micro-application module 201, load the entry resources of the micro-application project, and provide mounting points for the instances of the micro-application modules 201.
The layout module 204 is used to control the layout of the micro-application module 201 on the host application module.
The routing module 203 is configured to distribute the routing change message of the main application module 202 to the micro application module 201, and control loading and skipping of the micro application module 201. When the route is changed, the micro-application module 201 pushes the route event to the routing module 203, and then the routing module 203 decides to load, or jump to, the target micro-application module 201. If the routing does not require switching of the micro-application module 201, then processing is done by the current micro-application module 201.
The micro-application module 201 is responsible for the implementation of business logic.
Fig. 3 is a flowchart of a front-end application program at the time of route change:
s301, route change.
S302, judging whether the application needs to be switched.
If no handover is required, step S303 is performed; if a handover is required, step S306 is performed.
S303, notifying related micro-application route change information.
S304, the micro-application module changes the internal route.
S305, ending the flow.
S306, unloading the resources of the existing micro-application module.
S307, searching a configuration file mapping table of the micro application module.
S308, loading a new micro-application module configuration file.
S309, judging whether the version of the micro application module is changed.
If not, executing step S310; if so, step S311 is performed.
S310, judging whether the micro application module is instantiated or not.
If so, returning to step S305; if not, step S311 is performed.
S311, loading new micro application module entry resources.
S312, instantiation of the micro-application.
S313, marking that the micro application module is instantiated, and returning to the step S305.
The present example constructs a high-dimensional architecture for decoupling front-end micro-applications, which can split modules with business functions that do not interfere with each other into individual micro-application modules during the development phase, each of which is focused on processing a specific function or page, each iteration, and integrated at runtime into a complete system that can cover the various usage scenarios described above. This splitting enables different development teams to develop their respective micro-application modules in parallel, thereby speeding up the overall development process. Each micro-application module has its own communication interface allowing them to communicate and coordinate with each other as needed to achieve more complex functions.
The purpose of this example is to disassemble and decouple the front-end application into micro-application modules, develop the micro-application modules in parallel by adopting a loosely coupled architecture, accelerate the overall development process, also enable the micro-application modules to be updated and maintained independently without affecting the stability of the main application module, and simultaneously, can more flexibly combine and deploy different micro-application modules according to functional requirements. By faster loading time and smaller module volume, the amount of data transmission is reduced, providing a better user experience. Meanwhile, the learning cost of the developer can be reduced, the effect of the technical stack is unified, and a front-end development mode which is more flexible, efficient and modularized is provided for the developer.
Example 2
The present embodiment provides a front-end application management system, which is applied to a front-end system including a main application and at least two micro applications, and referring to fig. 4, the front-end application management system includes:
an integration module 1 for integrating the communication interfaces of the host application and at least two micro applications.
And the obtaining module 2 is used for obtaining the route change message through the communication interface of the main application.
A determining module 3, configured to determine the micro application to be skipped according to the route change message.
And the loading module 4 is used for loading the corresponding micro-application through the communication interface of the micro-application to be jumped.
In an alternative embodiment, the obtaining module 2 is further configured to obtain the routing event through a communication interface of the first micro-application.
The determining module 3 is further configured to determine, according to the routing event, to perform an action, where the performing action includes loading the first micro-application through a communication interface of the first micro-application or jumping to the second micro-application through a communication interface of the second micro-application.
In an alternative embodiment, the integration module 1 is further configured to integrate the micro-application into the interface of the host application according to a preset layout.
In an alternative embodiment, the loading module 4 is further configured to load a new version of the micro-application through the communication interface of the micro-application to be skipped when the version of the micro-application to be skipped is updated.
It should be noted that, the implementation principle and the technical effect of each module of the front-end application management system in this embodiment may refer to the corresponding parts of embodiment 1, and are not described herein again.
Example 3
The embodiment provides an electronic device, and fig. 5 is a schematic block diagram of the electronic device. The electronic device includes a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the front-end application management method of embodiment 1 when executing the program. The electronic device 30 shown in fig. 5 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 5, the electronic device 30 may be embodied in the form of a general purpose computing device, which may be a server device, for example. Components of electronic device 30 may include, but are not limited to: the at least one processor 31, the at least one memory 32, a bus 33 connecting the different system components, including the memory 32 and the processor 31.
The bus 33 includes a data bus, an address bus, and a control bus.
Memory 32 may include volatile memory such as Random Access Memory (RAM) 321 and/or cache memory 322, and may further include Read Only Memory (ROM) 323.
Memory 32 may also include a program/utility 325 having a set (at least one) of program modules 324, such program modules 324 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The processor 31 executes various functional applications and data processing, such as the front-end application management method of embodiment 1 of the present invention, by running a computer program stored in the memory 32.
The electronic device 30 may also communicate with one or more external devices 34 (e.g., keyboard, pointing device, etc.). Such communication may be through an input/output (I/O) interface 35. Also, model-generating device 30 may also communicate with one or more networks, such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet, via network adapter 36. As shown in fig. 5, network adapter 36 communicates with the other modules of model-generating device 30 via bus 33. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in connection with the model-generating device 30, including, but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, data backup storage systems, and the like.
It should be noted that although several units/modules or sub-units/modules of an electronic device are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more units/modules described above may be embodied in one unit/module in accordance with embodiments of the present invention. Conversely, the features and functions of one unit/module described above may be further divided into ones that are embodied by a plurality of units/modules.
Example 4
The present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the front-end application management method of embodiment 1.
More specifically, among others, readable storage media may be employed including, but not limited to: portable disk, hard disk, random access memory, read only memory, erasable programmable read only memory, optical storage device, magnetic storage device, or any suitable combination of the foregoing.
In a possible embodiment, the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the front-end application management method of embodiment 1 when the program product is run on the terminal device.
Wherein the program code for carrying out the invention may be written in any combination of one or more programming languages, the program code may execute entirely on the user device, partly on the user device, as a stand-alone software package, partly on the user device, partly on a remote device or entirely on the remote device.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that this is by way of example only, and the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the principles and spirit of the invention, but such changes and modifications fall within the scope of the invention.

Claims (10)

1. A front-end application management method, applied to a front-end system including a main application and at least two micro applications, the front-end application management method comprising:
integrating the communication interfaces of the host application and the at least two micro applications;
acquiring a route change message through a communication interface of a main application;
determining the micro application to be jumped according to the route change message;
and loading the corresponding micro-application through the communication interface of the micro-application to be jumped.
2. The front-end application management method of claim 1, wherein the front-end application management method further comprises:
acquiring a routing event through a communication interface of a first micro application;
determining an execution action according to the routing event, wherein the execution action comprises loading the first micro-application through a communication interface of the first micro-application or jumping to a second micro-application through a communication interface of the second micro-application.
3. The front-end application management method of claim 1, wherein the front-end application management method further comprises:
and integrating the micro application into an interface of the main application according to a preset layout.
4. The front-end application management method according to claim 1, wherein the step of loading the corresponding micro-application through the communication interface of the micro-application to be jumped further comprises:
and when the micro-application version to be jumped is updated, loading the micro-application of the new version through the communication interface of the micro-application to be jumped.
5. A front-end application management system for a front-end system comprising a host application and at least two micro-applications, said front-end application management system comprising:
the integration module is used for integrating the communication interfaces of the main application and the at least two micro applications;
the acquisition module is used for acquiring the route change message through the communication interface of the main application;
the determining module is used for determining the micro application to be skipped according to the route change message;
and the loading module is used for loading the corresponding micro-application through the communication interface of the micro-application to be jumped.
6. The front-end application management system of claim 5, wherein the acquisition module is further configured to acquire the routing event through a communication interface of the first micro-application;
the determining module is further configured to determine, according to the routing event, an execution action, where the execution action includes loading the first micro-application through a communication interface of the first micro-application or jumping to the second micro-application through a communication interface of the second micro-application.
7. The front-end application management system of claim 5, wherein the integration module is further configured to integrate the micro-application into an interface of the host application according to a preset layout.
8. The front-end application management system of claim 5, wherein the loading module is further configured to load a new version of the micro-application through the communication interface of the micro-application to be jumped when the version of the micro-application to be jumped is updated.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory for execution on the processor, wherein the processor implements the front-end application management method of any of claims 1-4 when executing the computer program.
10. A computer readable storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the front-end application management method of any of claims 1-4.
CN202311347520.5A 2023-10-18 2023-10-18 Front-end application management method, system, electronic equipment and medium Pending CN117290013A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311347520.5A CN117290013A (en) 2023-10-18 2023-10-18 Front-end application management method, system, electronic equipment and medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311347520.5A CN117290013A (en) 2023-10-18 2023-10-18 Front-end application management method, system, electronic equipment and medium

Publications (1)

Publication Number Publication Date
CN117290013A true CN117290013A (en) 2023-12-26

Family

ID=89251721

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311347520.5A Pending CN117290013A (en) 2023-10-18 2023-10-18 Front-end application management method, system, electronic equipment and medium

Country Status (1)

Country Link
CN (1) CN117290013A (en)

Similar Documents

Publication Publication Date Title
EP3754495B1 (en) Data processing method and related products
CN101676874B (en) Licy-based hypervisor configuration management
US20050204333A1 (en) Integrated system-of-systems modeling environment and related methods
US10977076B2 (en) Method and apparatus for processing a heterogeneous cluster-oriented task
CN102792270A (en) BIOS parameter virtualization via BIOS configuration profiles
US20080040725A1 (en) Method and apparatus for a parallel model of tasks including abstracted execution and software development
CN113971095A (en) KUBERNETES application program interface in extended process
CN111399897A (en) Application issuing method and system based on kubernets
CN113641413B (en) Target model loading updating method and device, readable medium and electronic equipment
US20210149723A1 (en) Method and apparatus for microservice architecture reconfiguration
CN110990081A (en) Microservice registration and discovery method and device, storage medium and electronic equipment
CN114490062A (en) Local disk scheduling method and device, electronic equipment and storage medium
CN112015371B (en) Software development device under non-embedded software platform
CN111352664B (en) Distributed machine learning task starting method, system, equipment and storage medium
CN117290013A (en) Front-end application management method, system, electronic equipment and medium
CN103617077A (en) Intelligent cloud migration method and system
Erlank et al. A hybrid real-time agent platform for fault-tolerant, embedded applications
JP2000276359A (en) Information processor, method for initializing program and program providing medium
CN113220507B (en) Version consistency checking method and device for double-master control system
CN113126961B (en) Pipeline processing method, device and storage medium
CN102567034B (en) Driver management system
CN104285211A (en) Periodic access of hardware resource
CN115022317B (en) Cloud platform-based application management method and device, electronic equipment and storage medium
CN108989586B (en) IVR implementation method, system, equipment and storage medium
CN114816672A (en) Virtual machine creation method and device, electronic equipment and storage medium

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