Modularization-based application service architecture construction method

Abstract

The invention discloses a modularization-based application service architecture construction method. The construction method comprises the following steps: an application service architecture comprises a first component and a second component; the first component is a basic component and comprises a non-business-related module; and the second component is a modular component cluster. The flexibility and expandability of the system are improved, and more convenient and efficient use experience is provided for users. And through the setting of the independent updating strategy and the background service, each component can obtain the latest function and security update in time, and the stability and security of the whole system are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of software development, and particularly to a method for constructing an application service architecture based on modularization. Background Art

[0002] With the popularization of smart phones and mobile devices, application programs (Apps) have become an indispensable part of people's daily lives. Users carry out activities such as communication, entertainment, learning, and shopping through various Apps. In order to meet the needs of different users, developers continuously launch Apps with rich functions and high integration. However, this "big and comprehensive" development model has brought a series of problems.

[0003] In order to add new functions or improve the user experience, the updates of Apps have become increasingly frequent. This not only consumes users' time and data traffic, but may also cause users to feel fatigued with updates. As the functions continue to increase, the size of Apps is also constantly expanding. This leads to an increased storage space pressure on users' devices, especially for users of low-end devices with limited storage capacity, which is a great burden. Although Apps provide numerous functions, most users usually only use a small part of them. This means that many resources are wasted on functions that are not commonly used, reducing the actual utility of the Apps. For users with limited data plans, downloading and updating large Apps will consume a large amount of traffic, increasing the additional economic burden. Large Apps may occupy more system resources, such as memory and processor time, thus affecting the performance and battery life of the devices.

[0004] In view of the above problems, a solution that can provide personalized services, reduce unnecessary downloads and updates, save users' traffic, and improve device performance is needed. The present invention aims to solve these problems by establishing a personalized application service system based on a modular architecture, enabling users to customize the functions of Apps according to their own needs, thereby optimizing the user experience, reducing resource waste, and improving overall efficiency.

[0005] Existing technical solutions:

[0006] 2.1 Overall update strategy

[0007] This solution adopts the traditional software development design concept. The development team will use the traditional APP software deployment package for development. During the development process, it is necessary to dock with the interface strategy of the background service to ensure that the APP can interact smoothly with the background system.

[0008] When a user uses it for the first time, it is necessary to first download and install the APP from the application store. After the installation is completed, the user needs to perform registration and login operations. Only after successful registration and login can the user access and use the relevant functions provided by the APP.

[0009] During the use of the APP, in case of a major update, the APP will first send an interface request to the background server when starting up to verify whether an update is required currently. If the result returned by the background server indicates that an update is needed, then the user will be prompted on the APP interface that there is a new update available. At this time, if the user chooses to click to confirm the update, the APP will automatically download the installation package of the latest version. After the download is completed, the user can install it manually, and after the installation is completed, the APP can be restarted and the latest functions can be continued to be used.

[0010] This update mechanism can ensure that users always use the most complete and secure version of the function, and at the same time avoid various problems caused by the outdated version of the user.

[0011] Disadvantages of the overall update strategy

[0012] The disadvantages of this solution include cumbersome update process, data traffic consumption, storage space pressure, strong dependence on background services, security risks and compatibility issues. The new version of the App may require more system resources, which may cause some old devices to be unable to run the latest version of the App.

[0013] In addition, limited user choice, single update push strategy and high development and maintenance costs are also the disadvantages of this solution. Summary of the Invention

[0014] In view of the above problems, the present invention is proposed to provide a modular-based application service architecture construction method that overcomes the above problems or at least partially solves the above problems.

[0015] According to one aspect of the present invention, there is provided a modular-based application service architecture construction method, the construction method comprising: the application service architecture includes a first component and a second component;

[0016] The first component is a basic component, including non-business-related modules;

[0017] The second component is a modular component cluster.

[0018] Optionally, the basic component includes: native functions that need to be adapted by the application based on multiple application end systems, including secure login, parts of non-system business functions, and functions that allow users to make personal customization selections based on the modular component group.

[0019] Optionally, the modular component cluster includes multiple business component function modules, depending on the common method of data encryption transmission of the basic component;

[0020] It is independently embedded and run in the form of H5, and the accessed background service is an independent background service.

[0021] Optionally, the accessed background service is an independent background service, specifically including:

[0022] If the user chooses to use the modular component cluster, it is added to the components used by the user. When the user opens their application, each component determines whether there is an update policy. If so, the components are updated one by one to achieve the update of the smallest modular unit.

[0023] Optionally, the basic components include:

[0024] The basic component application is based on the native functions adapted to each application end system, including the parts of secure login and non-system business function registration, and also includes the function for users to make personalized selections based on the modular component group;

[0025] The basic components cover multiple aspects, including secure login and registration functions;

[0026] The entry for users to enter the application;

[0027] The basic components also provide a modular component group, allowing users to make personalized customizations according to their own needs.

[0028] Optionally, the entry for users to enter the application specifically includes: protecting the user's account information through multi-factor authentication, encrypted transmission, etc.

[0029] Optionally, the modular component cluster specifically includes: multiple business component function modules;

[0030] Dependent on the common method of data encrypted transmission provided by the basic components, it is independently embedded and run in the H5 manner, and is an independent background service that accesses the background service;

[0031] When the user chooses to use a certain component, the component will be added to the components used by the user;

[0032] When the user opens their application, each component determines whether there is an update policy;

[0033] If there is an update policy, the components are updated one by one to achieve the update of the smallest modular unit;

[0034] Through the setting of the independent background service, the security and stability of the system are further guaranteed;

[0035] In actual applications, users freely combine and use multiple business components according to their needs to meet personalized requirements.

[0036] A method for constructing a modular-based application service architecture provided by the present invention, the construction method comprising: the application service architecture includes a first component and a second component; the first component is a basic component, including non-business-related modules; the second component is a modular component cluster. It improves the flexibility and scalability of the system and also provides users with a more convenient and efficient usage experience. Through the independent update strategy and the setting of background services, it ensures that each component can obtain the latest functions and security updates in a timely manner, enhancing the stability and security of the overall system.

[0037] The above description is only an overview of the technical solution of the present invention. In order to be able to understand the technical means of the present invention more clearly, it can be implemented in accordance with the content of the description. And in order to make the above and other objects, features and advantages of the present invention more obvious and understandable, the specific embodiments of the present invention are specifically exemplified below. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0039] Figure 1 It is a flowchart of the basic component provided by the embodiment of the present invention;

[0040] Figure 2 It is a flowchart of the modular component cluster provided by the embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0041] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the drawings. Although the exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided so that the present disclosure can be more thoroughly understood and the scope of the present disclosure can be completely conveyed to those skilled in the art.

[0042] The terms "including" and "having" and any variations thereof in the description of the embodiments, claims and drawings of the present invention are intended to cover non-exclusive inclusion. For example, including a series of steps or units.

[0043] The technical solutions of the present invention will be further described in detail below with reference to the drawings and embodiments.

[0044] A method for constructing a modular-based application service architecture, comprising: the first component, the basic component, is a non-business-related module, and the second component is a modular component cluster.

[0045] Basic components: The basic components mainly include the native functions that need to be applied based on the adaptation of each application end system, including parts of non-system business functions such as secure login and registration, and also include the function for users to make personal customization selections based on the modular component group.

[0046] Modular component cluster: It includes various business component function modules, depends on common methods such as data encryption and transmission provided by the basic components, and generally runs independently in the form of H5. The accessed back-end service is still an independent back-end service. If the user chooses to use this component, this component will be added to the components used by the user. When the user opens their own application, each component will judge whether there is an update policy by itself. If there is, each component will be updated one by one to achieve the smallest unit update of the module.

[0047] As Figure 1 shown, basic components:

[0048] The basic components mainly need to apply the native functions adapted based on each application end system, including parts of non-system business functions such as secure login and registration, and also include the function for users to make personal customization selections based on the modular component group.

[0049] The basic components cover multiple aspects, such as secure login and registration functions. This is the entry for users to enter the application, and its security and reliability must be ensured. For example, user account information is protected through multi-factor authentication and encrypted transmission methods. There are also parts of non-system business functions, such as user management and permission control. Although these functions are not direct business functions, they are crucial for the normal operation of the entire system. The basic components also provide a modular component group, allowing users to make personalized customizations according to their own needs. This flexibility enables the application to better adapt to the needs of different users and enhances the user experience.

[0050] The basic components play an important role in the application. They not only provide the necessary basic functions but also provide space for users to make personalized customizations, thus enhancing the attractiveness and practicality of the application.

[0051] As Figure 2 shown, modular component cluster:

[0052] The modular component cluster mainly covers various business component function modules. It depends on common methods such as data encryption and transmission provided by the basic components, usually runs independently in the form of H5, and the accessed back-end service is still an independent back-end service. When the user chooses to use a certain component, the component will be added to the components used by the user. When the user opens their own application, each component will judge whether there is an update policy by itself. If there is an update policy, each component will be updated one by one to achieve the smallest unit update of the module.

[0053] Each component operates independently without affecting other components, ensuring the efficiency and maintainability of the system. Through the setting of independent background services, the security and stability of the system are further guaranteed. When each component is updated, only its own update strategy needs to be concerned, without considering the compatibility issues of other components, simplifying the complexity of update and maintenance.

[0054] In practical applications, users can freely combine and use different business components according to their needs to meet their personalized requirements. For example, an e-commerce application selects multiple business components such as product display, shopping cart, and order management, and can update the versions of these components at any time to obtain the latest functions and security fixes.

[0055] The modular design not only improves the flexibility and scalability of the system, but also provides users with a more convenient and efficient usage experience. Through the setting of independent update strategies and background services, it is ensured that each component can obtain the latest functions and security updates in a timely manner, enhancing the stability and security of the overall system.

[0056] The present invention proposes an innovative architecture design mechanism, which is based on the design concept of multi-modularization on the client side and multi-componentization on the corresponding server side, and realizes multi-version support for both the front end and the back end at the same time. The core of this design mechanism is to split the APP application into multiple independent functional modules, and each module corresponds to a specific service or function. Users can flexibly select and use the required modules according to their specific needs, so as to obtain a personalized application experience.

[0057] Due to the adoption of modular and component-based strategies, users can also customize the layout of functional components on the main interface according to their personal preferences. Users can decide which functional modules should appear on the main interface and the arrangement order of these modules, etc. This not only improves the user experience, but also increases the flexibility and customizability of the application.

[0058] The component-based design also brings another significant advantage. When the service needs to be upgraded, it is upgraded based on the combination of the smallest units. This means that both the client side and the server side are independently updated and upgraded for specific components or modules, without the need to make comprehensive changes to the entire system. This not only reduces the risks during the upgrade process, but also improves the efficiency and flexibility of the upgrade.

[0059] Based on the architecture design mechanism of multi-modularization on the client side and multi-componentization on the corresponding server side, combined with multi-version support for both the front end and the back end, it provides a highly flexible, scalable and easy-to-maintain development and management framework for APP applications. By allowing users to select and use functional modules as needed, and customize the main interface according to their personal preferences, it fully meets the personalized needs of users, and at the same time simplifies the upgrade and maintenance process of the service.

[0060] Beneficial effects:

[0061] 1. Highly personalized user experience: By splitting the APP application into multiple independent functional modules, the present invention allows users to flexibly select and use the required modules according to their specific needs. This not only enhances the user experience but also increases the flexibility and customizability of the application. Users can decide which functional modules should appear on the main interface and the arrangement order of the modules, etc., to obtain a more personalized application experience.

[0062] 2. Simplified service upgrade and maintenance process: Due to the adoption of modular and component-based strategies, when the service needs to be upgraded, it is upgraded based on the combination of the smallest units. Whether it is the client or the server, independent updates and upgrades are carried out for specific components or modules without the need to make comprehensive changes to the entire system. This not only reduces the risks during the upgrade process but also improves the efficiency and flexibility of the upgrade.

[0063] 3. Development framework that is easy to maintain and expand: Based on the architecture design mechanism of multi-modularization on the client side and multi-componentization on the server side, combined with the support of multiple versions for both the front and back ends, a highly flexible, scalable, and easy-to-maintain development and management framework is provided for the APP application. This enables the development team to more easily manage and update each module and also facilitates future function expansion.

[0064] The above specific implementation manners further elaborate on the purpose, technical solutions, and beneficial effects of the present invention. It should be understood that the above are only the specific implementation manners of the present invention and are not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for constructing a modular application service architecture, characterized in that: The construction method includes: the application service architecture includes a first component and a second component; The first component is a basic component, including non-business related modules; The second component is a modular component cluster.

2. A modular application service architecture construction method according to claim 1, characterized in that: The basic components include: native functions that need to be applied based on multiple application-side system adaptation, including secure login and registration of non-system business functions, and functions for users to make personalized customization choices based on modular component groups.

3. A modular application service architecture construction method according to claim 1, characterized in that: The modular component cluster includes multiple business component function modules, relying on the public method of data encryption transmission of the basic components; It is independently embedded and run in H5 mode, and the background service accessed is an independent background service.

4. A modular application service architecture construction method according to claim 3, characterized in that: The accessed background service is an independent background service and specifically includes: If the user chooses to use a modular component cluster, he will be added to the user's components. When the user opens his own application, each component will determine whether there is an update strategy. If so, the components will be updated one by one to achieve modular minimum unit updates.

5. The method for constructing a modular application service architecture according to claim 1, characterized in that: The basic components include: Basic component applications are based on the native functions of each application-side system adaptation, including secure login and registration of non-system business functions, and include the function of users making personalized customization choices based on modular component groups; The basic components cover many aspects, including secure login and registration functions; The user's entry point into the application; The basic components also provide modular component groups, allowing users to customize them according to their needs.

6. A modularized application service architecture construction method according to claim 5, characterized in that: The user's entry into the application specifically includes: protecting the user's account information through multi-factor authentication, encrypted transmission, etc.

7. A modularized application service architecture construction method according to claim 1, characterized in that: The modular component cluster specifically includes: a plurality of business component function modules; Relying on the public data encryption transmission method provided by the basic components, it uses H5 to independently embed and run, and is an independent and accessible background service; When a user chooses to use a component, the component will be added to the user's usage components; When a user opens their app, each component determines whether there is an update policy; If an update strategy exists, update the components one by one to achieve modular minimum unit update; Through the setting of independent background services, the security and stability of the system are further guaranteed; In actual applications, users can freely combine and use a variety of business components as needed to meet personalized needs.

Images