A microservice management system based on car dealers
By designing acquisition, classification and splitting modules in the microservice management system, combining filtering modules and single sign-on verification, the problems of front-end code crossover and user permission management are solved, and the system availability and user security are improved.
Patent Information
- Application Number
- CN202410546708.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-04-28
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2044-04-28
AI Technical Summary
The crossover of front and back-end codes in existing microservice systems under the same project package leads to development redundancy, code duplication, complex user permission management, poor system availability and scalability, and easy to crash.
Design a microservice management system based on car dealers, including storage, user and server. By obtaining modules, classification modules and splitting modules, functional units are generated, and user permission management is realized by combining filter modules, and through Single sign-on and token verification improve security.
It realizes the independence of code management, reduces configuration dependencies, simplifies administrator management, improves system availability and scalability, and improves user account security.
Smart Images

Figure CN118227104B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data management, and in particular to a microservice management system based on car dealers. Background Art
[0002] In the existing microservice system, the front-end and back-end codes of the old architecture are crossed in the same project package, the front-end and back-end development are redundant, and some codes are repeated. It is urgent to split the front-end and back-end codes and perform code management and development separately.
[0003] User permissions and user management have not been implemented in a functionally configurable and manageable manner, which leads to complex permission reading and configuration, and increases the workload of business personnel and developers.
[0004] The system has poor availability and scalability, and is prone to crash when errors or overloads occur. Automatic service discovery and load balancing are needed to improve system availability and scalability. Summary of the invention
[0005] In view of the above problems, the present application is proposed to provide a microservice management system based on car dealers that overcomes the above problems or at least partially solves the above problems, including:
[0006] A microservice management system based on a car dealer, the system involves a storage end, a user end, a calling end and several service ends, each of which includes an acquisition module, a classification module and a splitting module;
[0007] The acquisition module is used to acquire all source codes in the storage end when receiving a user request sent by the user end;
[0008] The classification module is used to classify all the source codes to generate code types, wherein the code types include primary codes and secondary codes;
[0009] The splitting module is used to structurally split the main code to generate functional units for the user end and the calling end, and the functional units include an interface unit for interaction between the user end and the calling end, a business logic unit for determining the interaction logic, a data management unit for determining the interaction between the business logic unit and a preset database, and a project management unit for interaction between each of the server ends.
[0010] Further, the interface unit includes an external interface subunit and an internal interface subunit;
[0011] The external interface subunit is used for connecting to an external system;
[0012] The internal interface subunit is used for interaction between the user end and the calling end.
[0013] Furthermore, when docking with the external system is performed through the external interface subunit, an interface document for the user terminal is generated according to a preset document tool, and the interface document is sent to the user terminal.
[0014] Further, the business logic unit is used to determine the logic rules between each of the functional units; wherein the logic rules include the logic flow between the interface unit and the data management unit, the logic flow between the interface unit and the project management unit, the logic flow between the interface unit and the user end, the logic flow between the interface unit and the calling end, the logic flow between the project management units and the user end, the logic flow between the project management units and the calling end, the logic flow between the data management units and the user end, and the logic flow between the data management units and the calling end.
[0015] Furthermore, the data management unit is used to write the interaction logic between the business logic unit and the preset database.
[0016] Further, the project management unit includes a configuration subunit, a packaging subunit and a startup subunit;
[0017] The configuration subunit is used for initialization configuration of each function, which includes configuration files, system parameters, databases and dependent services;
[0018] The packaging subunit is used to obtain corresponding target data according to user requirements, and integrate the target data to generate an executable file;
[0019] The startup subunit is responsible for loading the main program framework, creating necessary processes and instantiating key objects.
[0020] Furthermore, it also includes a filtering module, which is used to determine the user rights of the user in the user terminal through preset filtering chain rules when the user in the user terminal accesses, wherein the preset filtering chain rules include initialization filtering chain rules and dynamic loading filtering chain rules.
[0021] An embodiment of the present application further discloses a microservice management system based on a car dealer, the system involves a storage end, a user end, a calling end and several service ends, the user end includes a basic management module, a login management module, a role management module and a role allocation module;
[0022] The basic management module is used to initialize the user data of newly added users and collect data for known users;
[0023] The login management module is used to receive the interface document sent by the server to generate login information, and perform login verification through the login information;
[0024] The resource management module is used for each of the known users to create a corresponding target role and to authorize functions of the target role;
[0025] The role assignment module is used to assign a target role of a corresponding function type to each of the known users, and the function types include viewing function, maintenance entry function, audit function and management function.
[0026] Furthermore, the login module is also used to encrypt the login password in the login information and store it in a preset database.
[0027] An embodiment of the present application further discloses a microservice management system based on a car dealer, the system involving a storage end, a user end, a calling end and several service ends, the calling end including a first interaction module and a second interaction module;
[0028] The first interaction module is used for service calling between the user end and the calling end;
[0029] The second interaction module is used for project management of a plurality of target projects in the server, wherein the project management includes adding new projects and modifying projects.
[0030] This application has the following advantages:
[0031] In the embodiments of the present application, compared with the prior art of "redundant cross-development of front-end and back-end, repeated parts of the code, the urgent need to split the front-end and back-end codes, and perform code management and development separately; complicated permission reading and configuration, increased workload of business personnel and developers; poor system availability and scalability, easy to crash when the system fails or is overloaded", the present application provides a solution of "a microservice management system based on car dealers", specifically: "a microservice management system based on car dealers, the system involves a storage end, a user end, a calling end and several service ends, each of the service ends includes an acquisition module, a classification module and a splitting module; the acquisition module is used when When receiving a user request sent by the user end, all source codes are obtained in the storage end; the classification module is used to classify all the source codes to generate code types, wherein the code types include main codes and secondary codes; the splitting module is used to perform structural splitting on the main code to generate functional units for the user end and the calling end, wherein the functional units include an interface unit for interaction between the user end and the calling end, a business logic unit for determining interaction logic, a data management unit for determining interaction between the business logic unit and a preset database, and a project management unit for interaction between each of the service ends. Through the "storage end, user end, calling end and several service ends", the problems of "redundant cross-development of front-end and back-end, duplication of some codes, urgent need to split the front-end and back-end codes, and perform code management and development separately; complicated permission reading and configuration, increased workload of business personnel and developers; poor system availability and scalability, easy to crash when the system fails or is overloaded" were solved, achieving the effect of "microservice architecture greatly reduces the dependence of system configuration on code, facilitates unified management and configuration by administrators, and has a cluster module to reduce the configuration workload and error probability. Through the microservice architecture, users and user authority management of the car dealer management system, combined with single sign-on and token verification, improve user account security". BRIEF DESCRIPTION OF THE DRAWINGS
[0032] In order to more clearly illustrate the technical solution of the present application, the drawings required for use in the description of the present application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0033] Figure 1 This is a structural block diagram of a microservice management system based on a car dealer provided in one embodiment of the present application;
[0034] Figure 2 This is a structural block diagram of a microservice management system based on a car dealer provided in one embodiment of the present application;
[0035] Figure 3 This is a structural block diagram of a microservice management system based on car dealers provided in one embodiment of the present application. DETAILED DESCRIPTION
[0036] In order to make the objects, features and advantages of the present application more obvious and understandable, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.
[0037] The inventors analyzed the prior art and found that the front-end and back-end codes of the old architecture were cross-linked under the same project package, the front-end and back-end development was redundant, and some codes were repeated. It was urgent to split the front-end and back-end codes and manage and develop them separately. User rights and user management were not functionally configured and managed, which resulted in complicated permission reading and configuration, and increased workload for business personnel and developers. The system had poor availability and scalability, and was prone to crash when the system failed or was overloaded. Automatic discovery and load balancing of services were needed to improve the availability and scalability of the system.
[0038] Reference Figure 1 , showing a structural block diagram of a microservice management system based on a car dealer provided by an embodiment of the present application;
[0039] A microservice management system based on a car dealer, the system involves a storage end, a user end, a calling end and several service ends, each of which includes an acquisition module, a classification module and a splitting module;
[0040] The acquisition module is used to acquire all source codes in the storage end when receiving a user request sent by the user end;
[0041] The classification module is used to classify all the source codes to generate code types, wherein the code types include primary codes and secondary codes;
[0042] The splitting module is used to structurally split the main code to generate functional units for the user end and the calling end, and the functional units include an interface unit for interaction between the user end and the calling end, a business logic unit for determining the interaction logic, a data management unit for determining the interaction between the preset databases of the business logic unit, and a project management unit for interaction between each of the server ends.
[0043] In the embodiments of the present application, compared with the prior art of "redundant cross-development of front-end and back-end, repeated parts of the code, the urgent need to split the front-end and back-end codes, and perform code management and development separately; complicated permission reading and configuration, increased workload of business personnel and developers; poor system availability and scalability, easy to crash when the system fails or is overloaded", the present application provides a solution of "a microservice management system based on car dealers", specifically: "a microservice management system based on car dealers, the system involves a storage end, a user end, a calling end and several service ends, each of the service ends includes an acquisition module, a classification module and a splitting module; the acquisition module is used when When receiving a user request sent by the user end, all source codes are obtained in the storage end; the classification module is used to classify all the source codes to generate code types, wherein the code types include main codes and secondary codes; the splitting module is used to perform structural splitting on the main code to generate functional units for the user end and the calling end, wherein the functional units include an interface unit for interaction between the user end and the calling end, a business logic unit for determining interaction logic, a data management unit for determining interaction between the business logic unit and a preset database, and a project management unit for interaction between each of the service ends. Through the "storage end, user end, calling end and several service ends", the problems of "redundant cross-development of front-end and back-end, duplication of some codes, urgent need to split the front-end and back-end codes, and perform code management and development separately; complicated permission reading and configuration, increased workload of business personnel and developers; poor system availability and scalability, easy to crash when the system fails or is overloaded" were solved, achieving the effect of "microservice architecture greatly reduces the dependence of system configuration on code, facilitating unified management and configuration by administrators, and having a cluster module, reducing the configuration workload and error probability. Through the microservice architecture, the users and user authority management of the car dealer management system are combined with single sign-on and token verification to improve user account security".
[0044] Next, a microservice management system based on a car dealer in this exemplary embodiment will be further described.
[0045] In a specific embodiment of the present invention, the code directory structure of the microservice is divided into two categories, one is business class source code and resource files, and the other is test classes and resource files used in unit testing.
[0046] In one embodiment of the present invention, the interface unit includes an external interface subunit and an internal interface subunit; the external interface subunit is used for docking with an external system; the internal interface subunit is used for interaction between the user end and the calling end.
[0047] In a specific embodiment, the API providing layer is also the external interface subunit: dealer-api; this layer writes the interface for docking with the external system, and the interface defined here can automatically generate a docking document through Swagger.
[0048] In a specific embodiment, the controller layer is also the internal interface subunit: dealer-controller; this layer mainly implements the interface defined by dealer-api, and provides an interface for internal interaction of the system (such as an interface called by the front end).
[0049] In one embodiment of the present invention, when the external system is connected through the external interface subunit, an interface document for the user terminal is generated according to a preset document tool, and the interface document is sent to the user terminal; in a specific embodiment, the system automatically generates an interface document of the RESTFUL interface of Swagger online.
[0050] In one embodiment of the present invention, the business logic unit is used to determine the logic rules between each of the functional units; wherein the logic rules include the logic flow between the interface unit and the data management unit, the logic flow between the interface unit and the project management unit, the logic flow between the interface unit and the user end, the logic flow between the interface unit and the calling end, the logic flow between the project management units and the user end, the logic flow between the project management units and the calling end, the logic flow between the data management units and the user end, and the logic flow between the data management units and the calling end; in a specific embodiment, the business logic layer is also the business logic unit: dealer-service; this layer mainly implements the business logic; in a specific implementation, it includes outlets-outlet information package, project-project information package, claim-claim policy information package, rules-return and repair rules information package, worktable-workbench information package, approve-approval package. The branch information package is used to process the business logic of querying, adding, modifying, and exporting branch information. Users with the role of entering branch information of car dealers can enter and modify the corresponding branch information and submit it for review; the project information package is used to process the business logic of querying, adding, modifying, and exporting branch information. Users with the role of entering project information can enter and modify the corresponding project information and submit it for review; the claim policy package is used to process the business logic of querying, adding, modifying, and exporting claim policies. Users with the role of entering claim policy information can enter and modify the corresponding claim policy information and submit it for review; the rule package is used to manage the query, addition, configuration, and modification of the return repair rule information. , export and other business logics, users with the role of rule information entry can enter, modify the corresponding information of the rules and submit them for review; the workbench package is used for workbench information query, review data of each section, and reminder data display; the review package is used to handle the review operations of related processes such as outlets, claims policies, return repair rules, projects, etc., and the processing personnel of each section add or modify the submission, and the process flows to the branch for review and processing, and then to the head office for review and processing; when the entry role submits, the system temporarily stores the data submitted by the process in the temporary table of the module. At this time, the data is in a pending state. After the process flows and the review is passed, it will be transferred to the formal table and the data will officially take effect.
[0051] In one embodiment of the present invention, the data management unit is used to write the interaction logic between the business logic unit and the preset database; in a specific embodiment, the data layer is also the data management unit: dealer-respsitory; this layer mainly writes the interaction with the database access layer; in a specific implementation, the business logic layer serves as the upper layer of the database access layer, and internally calls the methods provided by the database access layer to complete data storage and reading.
[0052] In one embodiment of the present invention, the project management unit includes a configuration subunit, a packaging subunit and a startup subunit; the configuration subunit is used for initialization configuration of each function, and the function includes configuration files, system parameters, databases and dependent services; the packaging subunit is used to obtain the corresponding target data according to user needs, and integrate the target data to generate an executable file; the startup subunit is responsible for loading the main program framework, creating necessary processes and instantiating key objects; in a specific embodiment, the project startup and configuration layer is the project management unit: dealer-bootstrap; this layer is used to integrate the configuration, packaging and startup functions of the project. In a specific implementation, the configuration subunit is used to process the part of the system initialization settings; such as loading configuration files, setting system parameters, establishing database connections and other dependent services, etc., to ensure that the application can correctly configure itself according to user needs and environment variables before starting or running. In a specific implementation, the packaging subunit is used for the functional module of the software distribution or deployment stage, responsible for integrating different parts of the software (such as source code, resource files, dependent libraries, etc.) into an executable file to facilitate the release, distribution and installation of the software. In a specific implementation, the startup unit is responsible for loading the main program framework, creating necessary processes, instantiating the initial code block of key objects, and can also initialize memory, load core components, check system status and execute the startup sequence.
[0053] In one embodiment of the present invention, it also includes a filtering module, which is used to determine the user rights of the user in the user terminal through preset filtering chain rules when the user accesses the system, wherein the preset filtering chain rules include initializing filtering chain rules and dynamically loading filtering chain rules; in a specific embodiment, a new interface permission filtering layer, i.e., a filtering module, is added to initialize filtering chain rules and dynamically load filtering chain rules to confirm whether the user has permission issues each time the user accesses the system.
[0054] Reference Figure 2 , showing a structural block diagram of a microservice management system based on a car dealer provided by an embodiment of the present application;
[0055] An embodiment of the present application further discloses a microservice management system based on a car dealer, the system involves a storage end, a user end, a calling end and several service ends, the user end includes a basic management module, a login management module, a role management module and a role allocation module;
[0056] The basic management module is used to initialize the user data of newly added users and collect data for known users;
[0057] The login management module is used to receive the interface document sent by the server to generate login information, and perform login verification through the login information;
[0058] The resource management module is used for each of the known users to create a corresponding target role and to authorize functions of the target role;
[0059] The role assignment module is used to assign a target role of a corresponding function type to each of the known users, and the function types include viewing function, maintenance entry function, audit function and management function.
[0060] In a specific embodiment, the system verifies the permissions of each request through the security framework shiro+jwt. After successful login, the client obtains a token. When the user requests, the token is placed in the header node of the message for backend verification. The redis middleware is used to cache the token and manage its validity period.
[0061] In a specific embodiment, the basic data management module initializes user data before the system goes online, collects and imports known users, and handles subsequent user changes such as new users through an agreed process.
[0062] In a specific embodiment, the login management module generates login information by receiving an interface document sent by the server, and performs login verification through the login information.
[0063] In a specific embodiment, the resource management module may allow users to create or edit roles and authorize menus or buttons for each role.
[0064] In a specific embodiment, the role assignment module may assign a role to each user.
[0065] In one embodiment of the present invention, the login module is also used to encrypt the login password in the login information and store it in a preset database; in a specific embodiment, the user's password data is encrypted and then saved in the preset database, providing a user password modification function.
[0066] Reference Figure 3 , showing a structural block diagram of a microservice management system based on a car dealer provided by an embodiment of the present application;
[0067] An embodiment of the present application further discloses a microservice management system based on a car dealer, the system involving a storage end, a user end, a calling end and several service ends, the calling end including a first interaction module and a second interaction module;
[0068] The first interaction module is used for service calling between the user end and the calling end;
[0069] The second interaction module is used for project management of a plurality of target projects in the server, wherein the project management includes adding new projects and modifying projects.
[0070] In a specific embodiment, the jar package, i.e., the second interactive module, is managed through microservices and Maven for addition and modification.
[0071] In a specific embodiment, the associated system can implement service calls between the primary and secondary systems at the Service layer by referencing the relevant jar package under the com.pcic.gr.dealer.api package of the car dealer system, namely the first interactive module. The two systems no longer need to go through other complex and redundant calls, interface conversions, etc. At the same time, when performing interface expansion and interface updates, the system can respond in time, quickly iterate and deploy, and reduce the workload of later operation and maintenance. Even if problems occur later, they can be quickly discovered and quickly responded to and resolved.
[0072] Embodiment 1
[0073] This application is developed based on the car dealer management system, and a microservice framework is developed based on the spring microservice architecture. This framework integrates the company's um system, workbench system, platform system and other framework toolkits. On the basis of integrating these tools, the car dealer system has added Shiro Filter (also known as Java security framework filter verification) in combination with its own business. The new interface permission filter layer is used to initialize the filter chain rules and dynamically load the filter chain rules to confirm whether the user has permission each time he accesses the system. The system combines the interface document of the RESTFUL interface with online automatic generation, which is used to fill the test user login information in the automatically generated interface document for public use, so as to provide the front-end joint debugging call and view, thereby improving the efficiency of joint debugging.
[0074] In the extended implementation class of the shiro framework, the logged-in user information is preloaded first, including name, work number, affiliated organization, affiliated secondary organization, and user's role, etc.; then the user's permissions are loaded; by preloading, relevant data can be added to the cache in advance to speed up the user experience. The jwt solution uses the "stateless" feature of jwt to support the actual needs of accounts that can log in at different locations at the same time; at the same time, jwt combined with the redis tool adds login time control, which can adjust the relevant user login online time configuration without restarting the system, allowing users to achieve repeated login operations within the effective time, improving the user experience.
[0075] Eureka adopts the CS design architecture, which includes two components: Eureka Server and Eureka Client. Eureka Server is the server for service registration function, and it is the service registration center. After each node is started, it will be registered in Eureka Server, so that the service registry in Eureka Server will store the information of all available service nodes, and the information of service nodes can be intuitively seen in the interface. Eureka Client is a Java client used to simplify the interaction with Eureka Server. The client also has a built-in load balancer that uses a polling load algorithm. After the application is started, it will send a heartbeat to Eureka Server (the default period is 3 seconds). If EurekaServer does not receive the heartbeat of a node within multiple heartbeat periods. Eureka Server will remove this service node from the service registry (90 seconds by default).
[0076] The other microservices in the system use Eureka clients to connect to the Eureka Server and maintain a heartbeat connection. In this way, the system maintainer can monitor whether each microservice in the system is running normally through the Eureka Server, and some other modules of Spring Cloud (such as Zuul) can discover other microservices in the system through the Eureka Server and execute related logic.
[0077] The car dealer management system uses the Eureka registration center to develop corresponding jar packages based on the calling specifications for other related systems that need to interact with the car dealer management system.
[0078] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.
[0079] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.
[0080] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.
[0081] The above is a detailed introduction to a microservice management system based on car dealers provided by the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for general technical personnel in this field, according to the idea of the present application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A microservice management system based on car dealers, It is characterized in that The system involves a storage end, a user end, a calling end and several service ends, each of which includes an acquisition module, a classification module and a splitting module; The acquisition module is used to acquire all source codes in the storage end when receiving a user request sent by the user end; The classification module is used to classify all the source codes to generate code types, wherein the code types include primary codes and secondary codes; The splitting module is used to perform structural splitting on the main code to generate functional units for the user end and the calling end, the functional units include an interface unit for interaction between the user end and the calling end, a business logic unit for determining interaction logic, a data management unit for determining interaction between the business logic unit and a preset database, and a project management unit for interaction between each of the service ends; the business logic unit is used to determine the logical rules between each of the functional units; wherein the logical rules include the logical flow between the interface unit and the data management unit, the logical flow between the interface unit and the project management unit, the logical flow between the interface unit and the user end, the logical flow between the interface unit and the calling end, the logical flow between the project management units and the user end, the logical flow between the project management units and the calling end, the logical flow between the data management units and the user end, and the logical flow between the data management units and the calling end; The project management unit includes a configuration subunit, a packaging subunit and a startup subunit; the configuration subunit is used for initialization configuration of each function, including configuration files, system parameters, databases and dependent services; the packaging subunit is used to obtain corresponding target data according to user needs, and integrate each target data to generate an executable file; the startup subunit is responsible for loading the main program framework, creating necessary processes and instantiating key objects; The user end includes a basic management module, a login management module, a role management module and a role allocation module; the basic management module is used to initialize the user data of newly added users and collect data for known users; the login management module is used to receive the interface document sent by the server to generate login information, and perform login verification through the login information; the role management module is used to create a corresponding target role for each known user and perform functional authorization for the target role; the role allocation module is used to allocate a target role of a corresponding functional type to each known user, and the functional type includes viewing function, maintenance entry function, audit function and management function; the login management module is also used to encrypt the login password in the login information and store it in a preset database; The calling end includes a first interaction module and a second interaction module; the first interaction module is used for service calls between the user end and the calling end; the second interaction module is used for project management of several target projects in the service end, wherein the project management includes adding new projects and modifying projects.
2. The system according to claim 1, It is characterized in that The interface unit includes an external interface subunit and an internal interface subunit; The external interface subunit is used for connecting to an external system; The internal interface subunit is used for interaction between the user end and the calling end.
3. The system according to claim 2, It is characterized in that When docking with the external system through the external interface subunit, an interface document for the user terminal is generated according to a preset document tool, and the interface document is sent to the user terminal.
4. The system according to claim 1, It is characterized in that The data management unit is used to write the interaction logic between the business logic unit and the preset database.
5. The system according to claim 1, It is characterized in that It also includes a filtering module, which is used to determine the user rights of the user in the user terminal through preset filtering chain rules when the user in the user terminal accesses, wherein the preset filtering chain rules include initialization filtering chain rules and dynamic loading filtering chain rules.
Citation Information
Patent Citations
Method and device for application separation
CN107391142A
Method, device and equipment for splitting large-scale application service into micro services
CN108279892A
Method for micro service of monolithic application
CN108279926A
Rapid construction system for zero-coding application software
CN110989983A
Business support Saas system, method, medium and device based on micro-service architecture
CN112532413A
