Application management system and method

Abstract

The present invention discloses an application management system and method, and relates to the field of computer technology. A specific implementation of the application management system includes: an application configuration center and an application management center; wherein the application configuration center is used to receive a sub-application update request sent by a user, the sub-application belongs to one or more applications, and updates the configuration information of the application according to the sub-application update request; the application management center is used to update one or more middleware called by the sub-application according to the updated configuration information, so that the application loads and executes the updated middleware when it is started next time. This implementation can realize hot update of sub-applications, and can also realize unified management and maintenance of sub-applications, and can improve the development efficiency of sub-applications.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an application management system and method. Background Art

[0002] In the actual development process, it takes a lot of time and energy to develop an application from scratch. In order to improve the efficiency of application development, various scaffolding tools have emerged, such as Create-react-app officially launched by React (a JavaScript library for building user interfaces) and Vue-cli officially launched by Vue (a progressive framework for building web interfaces), which have greatly improved the efficiency of application development.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art: the existing scaffolding tools have poor scalability and only support a single framework such as React or Vue. When multiple scaffolding tools are required, the subsequent maintenance cost is high, and unified management and maintenance of multiple applications are not supported; when the configuration file is updated, the application needs to be restarted, hot updates cannot be supported, and the user experience is poor. Summary of the invention

[0004] In view of this, the present invention provides an application management system and method, which can realize hot update of sub-applications, realize unified management and maintenance of sub-applications, and improve the development efficiency of sub-applications.

[0005] To achieve the above object, according to one aspect of the present invention, an application management system is provided, comprising: an application configuration center and an application management center; wherein:

[0006] The application configuration center is used to receive a sub-application update request sent by a user, the sub-application belonging to one or more applications, and update the configuration information of the application according to the sub-application update request;

[0007] The application management center is used to update one or more middlewares called by the sub-application according to the updated configuration information, so that the application loads and executes the updated middlewares when it is started next time.

[0008] Optionally, the sub-application is composed of one or more middlewares called in sequence.

[0009] Optionally, it also includes: an application routing center; wherein,

[0010] The application configuration center is further used to receive a new sub-application request sent by a user, and update the configuration information of the application to which the new sub-application belongs according to the new sub-application request;

[0011] The application management center is used to create the new sub-application according to the configuration information;

[0012] The application routing center is used to update the routing information of the application to which the new sub-application belongs according to the configuration information, so that the new sub-application is called according to the routing information.

[0013] Optionally, the creating the new sub-application according to the configuration information includes:

[0014] Registering the new sub-application to add the new sub-application to a sub-application list of the application to which the new sub-application belongs;

[0015] Registering the middleware called by the new sub-application according to the configuration information, so as to add the middleware to the sub-application list of the application to which the new sub-application belongs;

[0016] Creating the new sub-application according to the middleware called by the new sub-application;

[0017] The middleware is loaded and executed in sequence to start the new application.

[0018] Optionally, updating routing information of an application to which the new sub-application belongs according to the configuration information includes:

[0019] Determine routing information of the new sub-application according to the configuration information;

[0020] According to the routing information of the new sub-application, the routing information of the application to which the new sub-application belongs is updated.

[0021] Optionally, the middleware called by the new sub-application includes: a module packager;

[0022] The application management center is also used to set the query dependency path of the module packager to a preset integrated query dependency path before creating the new sub-application.

[0023] Optionally, the new sub-application request indicates a name of the new sub-application;

[0024] The application configuration center is further configured to determine whether the name of the new sub-application exists in the current configuration list, and if so, to notify the user that the name of the new sub-application is incorrect.

[0025] Optionally, the application configuration center is further used to receive a sub-application deletion request sent by a user, and update the configuration information of the application to which the sub-application belongs according to the sub-application deletion request;

[0026] The application management center is used to delete the sub-application according to the configuration information;

[0027] The application routing center is used to update the routing information of the application to which the sub-application belongs according to the configuration information, so that the sub-application cannot be called according to the routing information.

[0028] To achieve the above object, according to another aspect of the present invention, there is provided an application management method, which is applied to an application management system, comprising:

[0029] receiving a sub-application update request sent by a user, the sub-application belonging to one or more applications, and updating configuration information of the application according to the sub-application update request;

[0030] According to the updated configuration information, one or more middlewares called by the sub-application are updated, so that the application loads and executes the updated middlewares when it is started next time.

[0031] Optionally, the sub-application is composed of one or more middlewares called in sequence.

[0032] Optionally, it also includes:

[0033] Receive a new sub-application request sent by a user, and update configuration information of an application to which the new sub-application belongs according to the new sub-application request;

[0034] Creating the new sub-application according to the configuration information;

[0035] The routing information of the application to which the new sub-application belongs is updated according to the configuration information, so that the new sub-application is called according to the routing information.

[0036] Optionally, the creating the new sub-application according to the configuration information includes:

[0037] Registering the new sub-application to add the new sub-application to a sub-application list of the application to which the new sub-application belongs;

[0038] Registering the middleware called by the new sub-application according to the configuration information, so as to add the middleware to the sub-application list of the application to which the new sub-application belongs;

[0039] Creating the new sub-application according to the middleware called by the new sub-application;

[0040] The middleware is loaded and executed in sequence to start the new application.

[0041] Optionally, updating routing information of an application to which the new sub-application belongs according to the configuration information includes:

[0042] Determine routing information of the new sub-application according to the configuration information;

[0043] According to the routing information of the new sub-application, the routing information of the application to which the new sub-application belongs is updated.

[0044] Optionally, the middleware called by the new sub-application includes: a module packager;

[0045] Before creating the new sub-application, the query dependency path of the module packager is set to a preset integrated query dependency path.

[0046] Optionally, it also includes:

[0047] The request to create a new sub-application indicates the name of the new application;

[0048] It is determined whether the name of the new sub-application exists in the current configuration list. If so, the user is notified that the name of the new sub-application is incorrect.

[0049] Optionally, receiving a sub-application deletion request sent by a user, and updating configuration information of an application to which the sub-application belongs according to the sub-application deletion request;

[0050] Deleting the sub-application according to the configuration information;

[0051] The routing information of the application to which the sub-application belongs is updated according to the configuration information, so that the sub-application cannot be called according to the routing information.

[0052] To achieve the above-mentioned purpose, according to another aspect of the present invention, there is provided an electronic device for application management, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any of the methods described in the above-mentioned application management method.

[0053] To achieve the above objective, according to another aspect of the present invention, there is provided a computer-readable medium storing a computer program, wherein when the program is executed by a processor, any of the above-mentioned application management methods is implemented.

[0054] The above invention has the following advantages or beneficial effects: the application configuration center of the application management system can generate or configure the configuration information of the application, and realize the unified management and maintenance of one or more sub-applications by creating a new sub-application, deleting a sub-application, updating a sub-application, etc. in the application management center; in addition, after the middleware called by the sub-application is updated, the started sub-application still uses the middleware before the update, etc., and only loads and runs the updated middleware at the next startup, thereby realizing the hot update of the sub-application. In addition, before creating a new sub-application, the query dependency path of the module packager of the sub-application is changed to a preset integrated query path of the module packager that integrates one or more sub-applications, which greatly reduces the number of query dependency paths that need to be installed when creating a new sub-application, shortens the creation time, and thus improves the development efficiency of the application.

[0055] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0057] Figure 1 is a schematic diagram of the main structure of an application management system according to an embodiment of the present invention;

[0058] Figure 2 is a schematic diagram of the main process of a method for updating a sub-application applied to a management system according to an embodiment of the present invention;

[0059] Figure 3 is a schematic diagram of the main process of a method for creating a new sub-application in a management system according to an embodiment of the present invention;

[0060] Figure 4 is a schematic diagram of the main process of another method for creating a new sub-application in a management system according to an embodiment of the present invention;

[0061] Figure 5 is a schematic diagram of the main process of a method for deleting a sub-application applied to a management system according to an embodiment of the present invention;

[0062] Figure 6 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0063] Figure 7 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0064] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0065] Figure 1 Schematic diagram of the main structure of an application management system according to an embodiment of the present invention; Figure 1 As shown, the application management system 100 includes: an application configuration center 101 and an application management center 102; wherein,

[0066] The application configuration center 101 is used to receive a sub-application update request sent by a user, the sub-application belonging to one or more applications, and update the configuration information of the application according to the sub-application update request;

[0067] The application management center 102 is used to update one or more middlewares called by the sub-application according to the updated configuration information, so that the application loads and executes the updated middlewares when it is started next time.

[0068] It is understandable that a sub-application may belong to one or more applications, and similarly, one or more sub-applications may belong to the same application. For example, if a product has multiple sections, such as a monitoring platform, the entire platform can be regarded as an application, which has a mobile monitoring sub-application, a PC monitoring sub-application, and the like. The one or more middleware called by the sub-application include, but are not limited to, message middleware, module packager, Apache and other middleware. In a preferred embodiment, the sub-application is composed of one or more middleware called in sequence. In other words, the sub-application is composed of one or more middleware to accelerate the construction or update of the sub-application. Therefore, the update request of the sub-application includes, but is not limited to, updating the number of middleware constituting the sub-application, changing the type of middleware, and changing the middleware instance. It is worth noting that the update of the sub-application can be achieved when the sub-application is started, or when the sub-application is closed. When updating while a sub-application is started, the currently running sub-application still uses the one or more middleware that have been loaded and executed during this startup. At the same time, the middleware is updated according to the notification of the application configuration center. After the sub-application is closed after this startup, the updated one or more middleware are loaded and used when the user restarts the sub-application next time to achieve hot refresh of the sub-application, thereby improving the user experience of the sub-application.

[0069] Still see Figure 1Based on the above embodiment, the application management system 100 further includes: an application routing center 103; wherein,

[0070] The application configuration center 101 is further configured to receive a new sub-application request sent by a user, and update configuration information of the application to which the new sub-application belongs according to the new sub-application request;

[0071] The application management center 102 is used to create the new sub-application according to the configuration information;

[0072] The application routing 103 is used to update the routing information of the application to which the new sub-application belongs according to the configuration information, so that the new sub-application is called according to the routing information.

[0073] Specifically, the routing information refers to the routing information indicating the calling relationship between sub-applications and / or the calling relationship between an application and a sub-application.

[0074] In an optional implementation, the creation of the new sub-application according to the configuration information includes: registering the new sub-application to add the new sub-application to the sub-application list of the application to which it belongs; registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information to add the middleware to the sub-application list of the application to which the new sub-application belongs; creating the new sub-application according to the middleware called by the new sub-application; and sequentially loading and executing the middleware to start the new application. On this basis, the sub-applications can be uniformly managed and maintained through the sub-application list of the application to which the sub-application belongs according to actual needs, and at the same time, the application, sub-application, middleware, etc. can be monitored in real time through preset visualization functions, etc. In a preferred embodiment, the newly created new sub-application is composed of one or more middlewares called in sequence. In this way, the way of creating a new sub-application through one or more middlewares greatly reduces the time and experience required to create a new sub-application from scratch, and improves the efficiency of creating a new sub-application.

[0075] In an optional implementation, the updating of the routing information of the application to which the new sub-application belongs according to the configuration information includes: determining the routing information of the new sub-application according to the configuration information; and updating the routing information of the application to which the new sub-application belongs according to the routing information of the new sub-application. Based on this, the calling of the application and the sub-application can be realized through the updated routing information of the application to which the new sub-application belongs.

[0076] In an optional implementation, the middleware called by the new sub-application includes: a module packager; the application management center is further used to set the query dependency path of the module packager to a preset integrated query dependency path before creating the new sub-application.

[0077] Module bundlers include but are not limited to: Webpack, grunt, Gulp, etc. Currently, most applications need to install the query dependency path that the module bundler needs to use during initialization. Due to the large number of query dependency paths, it takes a long time to install. Therefore, by integrating the query dependency paths that may need to be installed in the current application, and modifying the query dependency of the module bundler to the preset integrated query dependency path before creating the sub-application, the number of query dependency paths installed by the application itself is greatly reduced. At the same time, when creating a new sub-application, the creation time of the sub-application can be shortened. In addition, the preset, fixed integrated query dependency path can further ensure the stability of the application build.

[0078] In an optional implementation, the new sub-application request indicates the name of the new sub-application; the application configuration center is further configured to determine whether the name of the new sub-application exists in the current configuration list, and if so, to notify the user that the name of the new sub-application is incorrect. In this way, the uniqueness of the names of different sub-applications can be guaranteed, and confusion or errors caused by duplicate names when calling sub-applications can be prevented.

[0079] On this basis, after the application is started, the application configuration center 101 will read the configuration information of all sub-applications in the directory corresponding to the application. After the configuration information is initialized, the relevant configuration information will be synchronized to the application management center 102 and the application routing center 103. After receiving the configuration information, the application management center 102 will register all current sub-applications in the sub-application list of the application in the application management center, and at the same time, according to the middleware configured in all sub-applications, register the middleware called by the new sub-application to add the middleware to the sub-application list of the application to which the sub-application belongs; then, according to the configured middleware order, load and execute the middleware in sequence to complete the startup of all sub-applications.

[0080] Still see Figure 1 On the basis of the above embodiment, the application configuration center 101 is further used to receive a sub-application deletion request sent by a user, and to update the configuration information of the application to which the sub-application belongs according to the sub-application deletion request; the application management center 102 is used to delete the sub-application according to the configuration information; the application routing center 103 is used to update the routing information of the application to which the sub-application belongs according to the configuration information, so that the sub-application cannot be called according to the routing information.

[0081] Based on the above embodiments, the application configuration center of the application management system can generate or configure the configuration information of the application, and realize the unified management and maintenance of one or more sub-applications by creating new sub-applications, deleting sub-applications, updating sub-applications, etc. in the application management center; in addition, after the middleware called by the sub-application is updated, the started sub-application still uses the middleware before the update, etc., and only loads and runs the updated middleware at the next startup, thereby realizing the hot update of the sub-application. In addition, before creating a new sub-application, the query dependency path of the module packager of the sub-application is changed to a preset integrated query path of the module packager that integrates one or more sub-applications, which greatly reduces the number of query dependency paths that need to be installed when creating a new sub-application, shortens the creation time, and thus improves the development efficiency of the application.

[0082] See also Figure 2 Based on the above embodiment, the embodiment of the present invention provides a method for updating a sub-application applied to a management system. The method may specifically include the following steps:

[0083] Step S201, receiving a sub-application update request sent by a user, the sub-application belonging to one or more applications, and updating the configuration information of the application according to the sub-application update request. The sub-application is composed of one or more middlewares called in sequence, and the sub-application update request indicates a change in the number or type of sub-application middleware, or a change in a middleware instance.

[0084] Step S202: updating one or more middlewares called by the sub-application according to the updated configuration information, so that the application loads and executes the updated middlewares when it is started next time.

[0085] See also Figure 3 Based on the above embodiment, the embodiment of the present invention provides a method for creating a new sub-application in a management system. The method may specifically include the following steps:

[0086] Step S301, receiving a new sub-application request sent by a user, and updating configuration information of the application to which the new sub-application belongs according to the new sub-application request. The new sub-application is composed of one or more called middlewares, and the configuration information indicates the one or more middlewares called by the sub-application.

[0087] In an optional implementation, the middleware called by the new sub-application includes: a module packager; before creating the new sub-application, setting the query dependency path of the module packager to a preset integrated query dependency path to improve the efficiency of creating the new sub-application.

[0088] In an optional implementation, the request to create a new sub-application indicates the name of the new application; it is determined whether the name of the new sub-application exists in the current configuration list, and if so, the user is notified that the name of the new sub-application is incorrect.

[0089] Step S302: Create the new sub-application according to the configuration information.

[0090] Specifically, register the new sub-application to add the new sub-application to the sub-application list of the application to which it belongs; register the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information to add the middleware to the sub-application list of the application to which the new sub-application belongs; create the new sub-application according to the middleware called by the new sub-application; and load and execute the middleware in sequence to start the new application.

[0091] Step S303: updating the routing information of the application to which the new sub-application belongs according to the configuration information, so that the new sub-application can be called according to the routing information.

[0092] Specifically, the routing information of the new sub-application is determined according to the configuration information; and the routing information of the application to which the new sub-application belongs is updated according to the routing information of the new sub-application.

[0093] See also Figure 4 Based on the above embodiment, the embodiment of the present invention provides another method for creating a new sub-application in a management system. The method may specifically include the following steps:

[0094] Step S401, receiving a new sub-application request sent by a user, and the middleware called by the new sub-application includes: module packager. That is to say, the new sub-application is composed of one or more middlewares, one of which is a module packager such as Webpack, grunt, Gulp, etc. It can be understood that after receiving the request to create a new sub-application, it should also be determined whether the name of the new sub-application exists in the current configuration list. If so, the user is notified that the name of the new sub-application is wrong to prevent different sub-applications from having the same name. If not, continue to execute the following steps.

[0095] Step S402: setting the query dependency path of the module packager to a preset integrated query dependency path.

[0096] Step S403: updating configuration information of the application to which the new sub-application belongs according to the newly created sub-application request.

[0097] Step S404: Create the new sub-application according to the configuration information.

[0098] Step S405: updating the routing information of the application to which the new sub-application belongs according to the configuration information, so that the new sub-application can be called according to the routing information.

[0099] See also Figure 5 Based on the above embodiment, a method for deleting a sub-application applied to an application management system is provided. The method may specifically include the following steps:

[0100] Step S501: receiving a sub-application deletion request sent by a user, and updating configuration information of an application to which the sub-application belongs according to the sub-application deletion request.

[0101] Step S502: Delete the sub-application according to the configuration information.

[0102] Step S503: updating the routing information of the application to which the sub-application belongs according to the configuration information, so that the sub-application cannot be called according to the routing information.

[0103] Figure 6 An exemplary system architecture 600 is shown to which the application management method according to an embodiment of the present invention can be applied.

[0104] like Figure 6 As shown, system architecture 600 may include terminal devices 601, 602, 603, network 604 and server 605. Network 604 is used to provide a medium for communication links between terminal devices 601, 602, 603 and server 605. Network 604 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0105] The user can use the terminal devices 601, 602, 603 to interact with the server 605 through the network 604 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 601, 602, 603, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0106] The terminal devices 601 , 602 , and 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers, etc.

[0107] The server 605 may be a server that provides various services, such as a backend management server (only an example) that provides support for shopping websites browsed by users using the terminal devices 601, 602, and 603. The backend management server may analyze and process the received data such as the product information query request, and feed back the processing result (the new sub-application name already exists) to the terminal device.

[0108] It should be noted that the application management method provided in the embodiment of the present invention is generally executed by the server 605 .

[0109] It should be understood that Figure 6 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0110] Reference below Figure 7 , which shows a schematic diagram of the structure of a computer system 700 of a terminal device suitable for implementing an embodiment of the present invention. Figure 7 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0111] like Figure 7 As shown, the computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 into a random access memory (RAM) 703. In the RAM 703, various programs and data required for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0112] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 708 including a hard disk, etc.; and a communication section 709 including a network interface card such as a LAN card, a modem, etc. The communication section 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the I / O interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage section 708 as needed.

[0113] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, the above-mentioned functions defined in the system of the present invention are executed.

[0114] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0115] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0116] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs, and when the above one or more programs are executed by a device, the device includes: receiving a sub-application update request sent by a user, the sub-application belongs to one or more applications, and updating the configuration information of the application according to the sub-application update request; updating one or more middleware called by the sub-application according to the updated configuration information, so that the application loads and executes the updated middleware when it is started next time.

[0117] According to the technical solution of the embodiment of the present invention, the application configuration center of the application management system can generate or configure the configuration information of the application, and realize the unified management and maintenance of one or more sub-applications by creating new sub-applications, deleting sub-applications, updating sub-applications, etc. in the application management center; in addition, after the middleware called by the sub-application is updated, the started sub-application still uses the middleware before the update, etc., and only loads and runs the updated middleware at the next startup, thereby realizing the hot update of the sub-application. In addition, before creating a new sub-application, the query dependency path of the module packager of the sub-application is changed to a preset integrated query path of the module packager that integrates one or more sub-applications, which greatly reduces the number of query dependency paths that need to be installed when creating a new sub-application, shortens the creation time, and thus improves the development efficiency of the application.

[0118] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. An application management system, characterized in that: include: Application configuration center, application management center and routing center; among them, The application configuration center is used to receive a sub-application update request sent by a user, the sub-application belonging to one or more applications, and update the configuration information of the application according to the sub-application update request; The application management center is used to update one or more middlewares called by the sub-application according to the updated configuration information, so that the application loads and executes the updated middlewares when it is started next time; The application configuration center is further used to receive a new sub-application request sent by a user, and update the configuration information of the application to which the new sub-application belongs according to the new sub-application request; The application management center is further used to create the new sub-application according to the configuration information, including: registering the new sub-application to add the new sub-application to the sub-application list of the application to which it belongs; registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information to add the middleware to the sub-application list of the application to which the new sub-application belongs; creating the new sub-application after setting the query dependency path of the module packager to a preset integrated query dependency path according to the middleware called by the new sub-application, the middleware including a module packager; and sequentially loading and executing the middleware to start the new sub-application; The application routing center is used to update the routing information of the application to which the new sub-application belongs according to the configuration information, so that the new sub-application is called according to the routing information.

2. The application management system according to claim 1, characterized in that: The updating, according to the configuration information, of the routing information of the application to which the new sub-application belongs includes: Determine routing information of the new sub-application according to the configuration information; According to the routing information of the new sub-application, the routing information of the application to which the new sub-application belongs is updated.

3. The application management system according to claim 1, characterized in that: The new sub-application request indicates the name of the new sub-application; The application configuration center is further configured to determine whether the name of the new sub-application exists in the current configuration list, and if so, to notify the user that the name of the new sub-application is incorrect.

4. The application management system according to claim 1, characterized in that: The application configuration center is further configured to receive a sub-application deletion request sent by a user, and update configuration information of the application to which the sub-application belongs according to the sub-application deletion request; The application management center is used to delete the sub-application according to the configuration information; The application routing center is used to update the routing information of the application to which the sub-application belongs according to the configuration information, so that the sub-application cannot be called according to the routing information.

5. An application management method, characterized in that: Applied to application management systems, including: receiving a sub-application update request sent by a user, the sub-application belonging to one or more applications, and updating configuration information of the application according to the sub-application update request; According to the updated configuration information, update one or more middlewares called by the sub-application, so that the application loads and executes the updated middlewares when it is started next time; Receive a new sub-application request sent by a user, and update configuration information of an application to which the new sub-application belongs according to the new sub-application request; Creating the new sub-application according to the configuration information includes: registering the new sub-application to add the new sub-application to a sub-application list of an application to which the new sub-application belongs; registering the middleware called by the new sub-application according to the middleware called by the new sub-application indicated by the configuration information to add the middleware to a sub-application list of an application to which the new sub-application belongs; creating the new sub-application after setting a query dependency path of the module packager to a preset integrated query dependency path according to the middleware called by the new sub-application, the middleware including a module packager; and sequentially loading and executing the middleware to start the new sub-application; The routing information of the application to which the new sub-application belongs is updated according to the configuration information, so that the new sub-application is called according to the routing information.

6. The application management method according to claim 5, characterized in that: The updating, according to the configuration information, of the routing information of the application to which the new sub-application belongs includes: Determine routing information of the new sub-application according to the configuration information; According to the routing information of the new sub-application, the routing information of the application to which the new sub-application belongs is updated.

7. The application management method according to claim 5, characterized in that: Also includes: The new sub-application request indicates the name of the new sub-application; It is determined whether the name of the new sub-application exists in the current configuration list. If so, the user is notified that the name of the new sub-application is incorrect.

8. The application management method according to claim 5, characterized in that: receiving a sub-application deletion request sent by a user, and updating configuration information of an application to which the sub-application belongs according to the sub-application deletion request; Deleting the sub-application according to the configuration information; The routing information of the application to which the sub-application belongs is updated according to the configuration information, so that the sub-application cannot be called according to the routing information.

9. An electronic device for application management, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 5 to 8.

10. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 5 to 8 is implemented.

Images