Modular micro-service system

Abstract

The invention provides a modular micro-service system. The system comprises a micro-service module cluster, a registration configuration module, a gateway module, a storage module and a monitoring module, the micro-service module cluster comprises a plurality of business micro-service modules and a plurality of middleware modules, and the business micro-service modules are used for processing business service requests distributed by the gateway module according to service registration information and configuration information acquired from the registration configuration module in advance; a data record composed of the business service request and the corresponding processing result is sent to a storage module, and the data record is sent to a corresponding middleware module according to the configuration information; and the self running state data is periodically sent to the monitoring module. According to the modularized micro-service system, the service integration complexity of the micro-service system can be reduced, the development efficiency, maintainability and version consistency of the micro-service system can be improved, and the performance and operation reliability of the micro-service system can be improved.

Description

Technical Field

[0001] The present application relates to the field of software engineering technology, and in particular to a modular microservice system. Background Art

[0002] With the rapid development of Internet technology, enterprises are gradually adopting microservice architecture in software development to improve the flexibility and maintainability of the system.

[0003] At present, the existing microservice system architecture usually relies on multiple components for service governance, configuration management and messaging. Existing technical solutions mainly include some common microservice architecture components, such as Spring Cloud, Dubbo, etc. However, although these solutions provide certain support for inter-service communication and service governance, they still have deficiencies in component integration, scalability and ease of use. Especially when an enterprise has hundreds of microservices, a unified public basic service library is particularly important. Due to the lack of good modular design in the existing microservice architecture, it will lead to problems such as high code coupling, increased maintenance costs and limited system scalability. Summary of the invention

[0004] In view of this, an embodiment of the present application provides a modular microservice system to eliminate or improve one or more defects existing in the prior art.

[0005] One aspect of the present application provides a modular microservice system, including: a microservice module cluster, a registration configuration module, a gateway module, a storage module, and a monitoring module;

[0006] The microservice module cluster includes multiple business microservice modules and multiple middleware modules, and each of the business microservice modules is communicatively connected to each other, and each of the business microservice modules is communicatively connected to each of the middleware modules respectively;

[0007] Each of the business microservice modules is respectively connected to the registration configuration module, the gateway module, the storage module and the monitoring module in a communication manner;

[0008] The business microservice module is used to process the business service request distributed by the gateway module according to the service registration information and configuration information obtained in advance from the registration configuration module to obtain corresponding processing result data, send a data record consisting of the business service request and the corresponding processing result to the storage module so that the storage module stores the data record, and send the data record to the corresponding middleware module according to the configuration information;

[0009] The business microservice module is also used to periodically send its own operating status data to the monitoring module, so that the monitoring module monitors the operating status data of each of the microservice modules.

[0010] In some embodiments of the present application, the microservice module cluster further includes:

[0011] The flow control and fuse components are respectively connected to the communication between each of the business microservice modules, and are used to monitor the operation status of each of the business microservice modules, and when a business microservice module with an abnormal operation status is detected, at least one of flow limiting, degradation and fuse processing is performed on the business microservice module;

[0012] The load balancing unit is respectively connected to each of the business microservice modules for performing load balancing on each of the business microservice modules.

[0013] In some embodiments of the present application, the storage module includes: a relational database, a time series database, and a cache database; the relational database includes: an Oracle cluster and a MySQL cluster;

[0014] Correspondingly, the microservice module cluster also includes: a persistent interaction interface and a storage interaction interface;

[0015] The persistent interaction interface is used to send the data records of each of the business microservice modules to the Oracle cluster and / or the MySQL cluster for persistent storage;

[0016] The storage interaction interface is used to send the data records of each of the business microservice modules to the time series database for time series storage, and send the data records of each of the business microservice modules to the cache database for distributed cache processing.

[0017] In some embodiments of the present application, the storage module further includes: a distributed document storage database;

[0018] The distributed document storage database includes: a document database and a document retrieval analysis database;

[0019] The document database is used to obtain the semi-structured data or unstructured data corresponding to each of the business microservice modules based on the storage interaction interface for distributed storage;

[0020] The document retrieval and analysis database is used to perform document retrieval and aggregation analysis on the semi-structured data or unstructured data corresponding to each of the business microservice modules obtained based on the storage interaction interface, and store the obtained document retrieval and aggregation analysis result data.

[0021] In some embodiments of the present application, the registration configuration module includes: a registration center unit and a configuration center unit;

[0022] The registration center unit is respectively connected to the gateway module and each of the business microservice modules for communication, and the registration center unit is used to register the service and store the corresponding service registration information, and send the service registration information to the gateway module and each of the business microservice modules respectively;

[0023] The configuration center unit is respectively communicated with the gateway module and each of the business microservice modules, and is used to perform service configuration and store corresponding service configuration information, and send the service configuration information to the gateway module and each of the business microservice modules respectively.

[0024] In some embodiments of the present application, the gateway module includes: a security authentication gateway, a load balancing gateway, and a secure Internet gateway that are sequentially communicatively connected;

[0025] The security authentication gateway is used to receive a business service request and perform security authentication on the business service request. If it is determined that the business service request passes the security authentication, the business service request is forwarded to the load balancing gateway;

[0026] The load balancing gateway is used to perform load balancing processing on the business service request received from the security authentication gateway, and forward the business service request after load balancing processing to the secure Internet gateway;

[0027] The secure Internet gateway is used to perform security checks on the business service requests received from the load balancing gateway. If it is determined that the business service request passes the security check, the business microservice module is selected as the corresponding target business microservice module based on the business type specified by the business service request and the operating status of each business microservice module in the microservice module cluster currently used to process the business type, and the business service request is forwarded to the target business microservice module.

[0028] In some embodiments of the present application, the monitoring module includes: a distributed link tracking unit;

[0029] The distributed link tracking unit is respectively communicated with the gateway module and each of the business microservice modules, and is used to obtain the respective operating status data of the gateway module and each of the business microservice modules, so as to obtain the respective service health status of the gateway module and each of the business microservice modules, as well as the call links and call durations between each of the business microservice modules.

[0030] In some embodiments of the present application, the middleware module includes: a distributed task scheduling unit and a message subscription unit;

[0031] The distributed task scheduling unit is respectively connected to each of the business microservice modules for communication, and the distributed task scheduling unit is used to call each of the business microservice modules to execute preset timed tasks and / or batch tasks;

[0032] The message subscription unit is respectively communicated with each of the business microservice modules, and is used to perform asynchronous message processing between the business microservice modules, so that each of the business microservice modules is decoupled through the message queue in the message subscription unit.

[0033] In some embodiments of the present application, the modular microservice system further includes: a big data module;

[0034] The big data module is respectively communicated with each of the business microservice modules, and is used to extract corresponding result data from the local data warehouse according to the big data call request sent by the business microservice module, and send the result data to the business microservice module; wherein the data warehouse includes a real-time data warehouse and an offline data warehouse.

[0035] In some embodiments of the present application, the modular microservice system further includes: an AI module;

[0036] The AI ​​module is respectively communicated with each of the business microservice modules. The AI ​​module is used to call the local computing unit to obtain the corresponding calculation result data according to the calculation request sent by the business microservice module, and send the calculation result data to the business microservice module.

[0037] The modular microservice system provided by the present application includes a microservice module cluster, a registration configuration module, a gateway module, a storage module and a monitoring module; the microservice module cluster includes multiple business microservice modules and multiple middleware modules, and each of the business microservice modules is communicatively connected, and each of the business microservice modules is communicatively connected with each of the middleware modules; each of the business microservice modules is communicatively connected with the registration configuration module, the gateway module, the storage module and the monitoring module; the business microservice module is used to process the business service request distributed by the gateway module according to the service registration information and configuration information obtained in advance from the registration configuration module to obtain corresponding processing result data, and the business service request and the corresponding The data record consisting of the processing results is sent to the storage module so that the storage module stores the data record, and sends the data record to the corresponding middleware module according to the configuration information; the business microservice module is also used to periodically send its own operating status data to the monitoring module so that the monitoring module monitors the operating status data of each of the microservice modules, thereby realizing a modular microservice system, reducing the service integration complexity of the microservice system, and improving the development efficiency, maintainability and version consistency of the microservice system, improving the performance and operation reliability of the microservice system, and effectively improving the flexibility, convenience and scalability of developers in selecting and combining modules of the microservice system according to specific needs.

[0038] Additional advantages, purposes, and features of the present application will be partially described in the following description, and will become partially apparent to those skilled in the art after studying the following, or may be learned from the practice of the present application. The purposes and other advantages of the present application can be achieved and obtained by the structures specifically pointed out in the specification and the drawings.

[0039] Those skilled in the art will understand that the purposes and advantages that can be achieved by the present application are not limited to the above specific description, and the above and other purposes that can be achieved by the present application will be more clearly understood based on the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The drawings described herein are used to provide a further understanding of the present application, constitute a part of the present application, and do not constitute a limitation of the present application. The components in the drawings are not drawn to scale, but are only for the purpose of illustrating the principles of the present application. In order to facilitate the illustration and description of some parts of the present application, the corresponding parts in the drawings may be enlarged, that is, they may become larger relative to other components in the exemplary device actually manufactured according to the present application. In the drawings:

[0041] Figure 1This is a schematic diagram of a first architecture of a modular microservice system in an embodiment of the present application.

[0042] Figure 2 This is a schematic diagram of the first structure of a microservice module cluster in a modular microservice system in an embodiment of the present application.

[0043] Figure 3 This is a second structural diagram of a microservice module cluster in a modular microservice system in an embodiment of the present application.

[0044] Figure 4 Schematic diagram of the structure of a storage module in a modular microservice system in an embodiment of the present application.

[0045] Figure 5 Schematic diagram of the second architecture of the modular microservice system in one embodiment of the present application.

[0046] Figure 6 Schematic diagram of the data processing flow corresponding to the modular microservice system in one embodiment of the present application.

[0047] Figure 7 This is a third structural diagram of a modular microservice system in an embodiment of the present application.

[0048] Figure 8 Schematic diagram of the functional architecture of the modular microservice system provided for the application example of this application.

[0049] Fig. 9 Application architecture diagram of the modular microservice system provided for the application example of this application.

[0050] Fig.10 Data architecture diagram of the modular microservice system provided for the application example of this application.

[0051] Fig.11 The figure is a schematic diagram of an example of a modular microservice system for executing financing business.

[0052] Reference numerals:

[0053] 1-Microservice module cluster;

[0054] 11-Business microservice module;

[0055] 12-Middleware module;

[0056] 121-distributed task scheduling unit;

[0057] 122-message subscription unit;

[0058] 13-Flow control and fuse components;

[0059] 14- Load balancing unit;

[0060] 15- Third-party services;

[0061] 16-Microservice calling unit;

[0062] 17-Persistent interaction interface;

[0063] 18- Storage interaction interface;

[0064] 2- Storage module;

[0065] 21-Relational database;

[0066] 211-Oracle cluster;

[0067] 212-MySQL cluster;

[0068] 22-Time series database;

[0069] 23-Cache database;

[0070] 24-Distributed document storage database;

[0071] 241- Document database;

[0072] 242- Document retrieval and analysis database;

[0073] 3-Register configuration module;

[0074] 31-Registration center unit;

[0075] 32-Configuration center unit;

[0076] 4- Gateway module;

[0077] 41-Security authentication gateway;

[0078] 42-load balancing gateway;

[0079] 43-Secure Internet Gateway;

[0080] 5- Monitoring module;

[0081] 51-distributed link tracking unit;

[0082] 6- Big data module;

[0083] 7-AI module. DETAILED DESCRIPTION

[0084] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the implementation modes and the accompanying drawings. Here, the illustrative implementation modes and descriptions of the present application are used to explain the present application, but are not intended to limit the present application.

[0085] It should also be noted here that in order to avoid obscuring the present application due to unnecessary details, only the structures and / or processing steps closely related to the scheme according to the present application are shown in the accompanying drawings, while other details that are not very relevant to the present application are omitted.

[0086] It should be emphasized that the term “include / comprises” when used herein refers to the presence of features, elements, steps or components, but does not exclude the presence or addition of one or more other features, elements, steps or components.

[0087] It should also be noted that, unless otherwise specified, the term “connection” herein may refer not only to a direct connection but also to an indirect connection with an intermediate.

[0088] Hereinafter, embodiments of the present application will be described with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0089] The main problems of existing microservice systems are as follows:

[0090] (1) Insufficient modularity: Existing solutions usually mix multiple functional modules together, resulting in poor maintainability.

[0091] (2) Integration complexity: When integrating services, each component needs to be manually configured and managed, which increases system complexity.

[0092] (3) Inconsistent versions: When hundreds of microservices share a common basic service library, it is difficult to achieve consistency in the versions of all JAR packages.

[0093] (4) Middleware fault handling: When a problem occurs in a middleware component, the code of each microservice must be modified one by one, increasing maintenance costs.

[0094] (5) Inconsistent coding style: The lack of consistent coding style and middleware usage specifications leads to low development efficiency.

[0095] In order to solve at least one of the above-mentioned technical problems, an embodiment of the present application provides a modular microservice system, which can reduce the service integration complexity of the microservice system, and can improve the development efficiency, maintainability and version consistency of the microservice system, and can improve the performance and operation reliability of the microservice system.

[0096] The details are described in detail through the following examples.

[0097] Based on this, the present application embodiment provides a modular microservice system, see Figure 1 , the modular microservice system specifically includes the following contents:

[0098] Microservice module cluster 1, registration configuration module 3, gateway module 4, storage module 2 and monitoring module 5;

[0099] The microservice module cluster 1 includes a plurality of business microservice modules 11 and a plurality of middleware modules 12, and each of the business microservice modules 11 is communicatively connected to each other, and each of the business microservice modules 11 is communicatively connected to each of the middleware modules 12;

[0100] Each of the business microservice modules 11 is respectively connected to the registration configuration module 3, the gateway module 4, the storage module 2 and the monitoring module 5 for communication;

[0101] The business microservice module 11 is used to process the business service request distributed by the gateway module 4 according to the service registration information and configuration information obtained in advance from the registration configuration module 3 to obtain corresponding processing result data, and send the data record consisting of the business service request and the corresponding processing result to the storage module 2 so that the storage module 2 stores the data record, and send the data record to the corresponding middleware module 12 according to the configuration information;

[0102] The business microservice module 11 is also used to periodically send its own operating status data to the monitoring module 5, so that the monitoring module 5 monitors the operating status data of each of the microservice modules.

[0103] In one or more embodiments of the present application, microservices is a software architecture style that builds an application as a set of small, independent services, each of which performs a specific function. POM (Project Object Model) is an XML file in Maven projects that manages project configurations such as dependencies, plug-ins, etc. Modularization refers to breaking down a system into multiple small parts (modules), each of which performs a specific function.

[0104] It is understandable that the microservice module cluster 1 can specifically adopt the Springboot service group to automatically configure the Springboot application. The microservice module cluster 1 includes multiple business microservice modules 11, and each business microservice module 11 has its own corresponding business type. These business microservice modules 11 can be remotely called through the Feign client to facilitate communication between business microservice modules 11. Among them, Feign is used to simplify REST calls between microservices and provide a declarative calling method.

[0105] In an example of a modular microservice system for executing financing business, the business types corresponding to each of the business microservice modules 11 include: user center, financing service, document center, investment plan service, bank adaptation service, document review business service, loan business service, financing entity service, document review basic business, loan basic business, quotation inquiry service, file creation business service and file creation basic server (credit-base).

[0106] The gateway module 4 is also connected to the monitoring module 5 and the registration configuration module 3 for communication.

[0107] In one or more embodiments of the present application, the operating status may refer to a network communication status, a data processing status, etc.

[0108] From the above description, it can be seen that the modular microservice system provided in the embodiment of the present application can realize a modular microservice system, reduce the service integration complexity of the microservice system, and improve the development efficiency, maintainability and version consistency of the microservice system, and can improve the performance and operation reliability of the microservice system, and can effectively improve the flexibility, convenience and scalability of developers to select and combine modules of the microservice system according to specific needs.

[0109] In order to further improve the operational reliability, development efficiency, maintainability and version consistency of the microservice module cluster 1, in a modular microservice system provided in an embodiment of the present application, see Figure 2 , the microservice module cluster 1 in the modular microservice system further specifically includes the following contents:

[0110] Flow control and fuse component 13 and load balancing unit 14.

[0111] The flow control and fuse component 13 is respectively connected to each of the business microservice modules 11 for communication. The flow control and fuse component 13 is used to monitor the operating status of each of the business microservice modules 11, and when a business microservice module 11 with an abnormal operating status is detected, at least one of flow limiting, degradation and fuse processing is performed on the business microservice module 11;

[0112] The load balancing unit 14 is respectively connected to each of the business microservice modules 11 for communication, and the load balancing unit 14 is used to perform load balancing processing on each of the business microservice modules 11 .

[0113] It can be understood that at least one of the current limiting, degradation and fuse processing for the business microservice module 11 can be implemented according to a preset exception handling table, which is used to store the correspondence between each operating state exception type and the corresponding processing method (i.e., current limiting, degradation and fuse processing).

[0114] In an example of a modular microservice system, see Figure 3 The modular microservice system may also include a microservice calling unit 16 (such as OpenFeign), which is a declarative, templated HTTP client that is mainly used to simplify remote calls between microservices. It encapsulates the service calling process by defining interfaces, annotations, and dynamic proxies, so that developers can call remote services like calling local methods without having to pay attention to the underlying HTTP request and response processing details.

[0115] In an example of a modular microservice system, see Figure 3 The modular microservice system may also include third-party services 15 such as HTTP units and SDK units. Hypertext Transfer Protocol (HTTP) is a simple request-response protocol that usually runs on TCP. It specifies what messages a client may send to a server and what responses it may get. SDK (Software Development Kit) is a software development kit.

[0116] In one or more embodiments of the present application, the flow control and fuse component 13 can be implemented using Sentinel, which is an open source framework for flow control and fuse, providing flow control and fuse support. As a flow control and fuse degradation component, Sentinel monitors the operation of each microservice, provides current limiting and fuse functions, and ensures that the system can maintain service availability under abnormal circumstances.

[0117] In one or more embodiments of the present application, the load balancing unit 14 can be implemented using a load balancer (LoadBalancer). A load balancer is a network device, service or software application whose main function is to distribute workload among multiple servers to ensure that each server can effectively process requests, thereby improving the overall performance and reliability of the system.

[0118] In one or more embodiments of the present application, the microservice module cluster 1 can be implemented using Springboot application services, which may include: an infrastructure layer (Infrastructure Layer), a domain layer (Domain Layer), an application layer (Application Layer) and an interface layer (User Interface Layer).

[0119] In order to further improve the operation reliability, development efficiency, maintainability and version consistency of the storage module 2, in a modular microservice system provided in an embodiment of the present application, see Figure 4 , the storage module 2 in the modular microservice system includes the following contents:

[0120] A relational database 21, a time series database 22 and a cache database 23; the relational database 21 includes: an Oracle cluster 211 and a MySQL cluster 212;

[0121] Correspondingly, the microservice module cluster 1 further includes: a persistent interaction interface 17 and a storage interaction interface 18;

[0122] The persistent interaction interface 17 is used to send the data records of each of the business microservice modules 11 to the Oracle cluster 211 and / or the MySQL cluster 212 for persistent storage;

[0123] The storage interaction interface 18 is used to send the data records of each of the business microservice modules 11 to the time series database 22 for time series storage, and to send the data records of each of the business microservice modules 11 to the cache database 23 for distributed cache processing.

[0124] It is understandable that persistent storage (MyBatis-parent) is used to integrate MyBatis and simplify database operations. MyBatis, as a persistence framework, is responsible for storing business data in the database. Two different database clusters are used in the architecture. The Oracle cluster 211 is suitable for processing complex business logic and transactions; the MySQL cluster is used for some relatively simple and fast read and write business scenarios.

[0125] The time series database 22 can use TdEngine, which is a big data platform designed and optimized for scenarios such as the Internet of Things and Industrial Internet. Its core module is a high-performance, cluster open source, cloud-native, and minimalist time series database 22.

[0126] The cache database 23 can be implemented using a Redis cluster (distributed cache), which is used for distributed caching to reduce the frequent reading pressure of the service on the database and improve the response speed. Redis can be used to cache some frequently accessed user data and business data to speed up the reading and writing speed. Among them, Redis and Redission are used to encapsulate Redis operations and support distributed services.

[0127] In order to further improve the operation reliability, development efficiency, maintainability and version consistency of the storage module 2, in a modular microservice system provided in an embodiment of the present application, see Figure 4 , the storage module 2 in the modular microservice system also includes the following contents:

[0128] Distributed document storage database 24. The distributed document storage database 24 includes: a document database 241 and a document retrieval analysis database 242;

[0129] The document database 241 is used to obtain the semi-structured data or unstructured data corresponding to each of the business microservice modules 11 based on the storage interaction interface 18 for distributed storage;

[0130] The document retrieval analysis database 242 is used to perform document retrieval and aggregation analysis on the semi-structured data or unstructured data corresponding to each of the business microservice modules 11 obtained based on the storage interaction interface 18, and store the obtained document retrieval and aggregation analysis result data.

[0131] The document database 241 may be implemented using a MongoDB cluster. As a document-type database, MongoDB stores some semi-structured or unstructured data and is suitable for processing flexible data structures, such as user behavior logs, activity configurations, and the like.

[0132] The document retrieval analysis database 242 can be implemented using an ES cluster (Elasticsearch), which provides search services by encapsulating Elasticsearch operations. It is used for full-text retrieval and log analysis. Through ES, log retrieval and aggregation analysis of complex data can be quickly performed, which is convenient for troubleshooting system problems and performing data analysis. Elasticsearch is a search engine based on Lucene that provides distributed full-text search capabilities.

[0133] It is understandable that the storage module 2 may also be provided with a file storage server, which is respectively connected to each database in the storage module 2. The file storage server is a network server that can provide file storage and management services for clients in the network. The file storage server generally adopts a distributed file system, which can support the storage and management of large-capacity data and has good scalability.

[0134] In order to further improve the operation reliability, development efficiency, maintainability and version consistency of the registration configuration module 3, in a modular microservice system provided in an embodiment of the present application, see Figure 5 , the registration configuration module 3 in the modular microservice system includes the following contents:

[0135] A registration center unit 31 and a configuration center unit 32. The registration center unit 31 is respectively connected to the gateway module 4 and each of the business microservice modules 11 for communication, and the registration center unit 31 is used to register services and store corresponding service registration information, and send the service registration information to the gateway module 4 and each of the business microservice modules 11;

[0136] The configuration center unit 32 is respectively communicated with the gateway module 4 and each of the business microservice modules 11, and the configuration center unit 32 is used to perform service configuration and store corresponding service configuration information, and send the service configuration information to the gateway module 4 and each of the business microservice modules 11 respectively.

[0137] It is understandable that the registration center unit 31 and the configuration center unit 32 can be implemented using a Nacos cluster, which is an open source service discovery and configuration management platform that integrates Nacos for service configuration and service discovery. The Nacos cluster is used for the functions of the service registration and configuration center. All microservice instances will register with Nacos, which is responsible for service registration, health checks, and dynamic discovery. Through this mechanism, microservices in the system can dynamically discover and call other services, supporting the elastic scaling of microservices.

[0138] In order to further improve the operational reliability, development efficiency, maintainability and version consistency of the gateway module 4, in a modular microservice system provided in an embodiment of the present application, see Figure 5 , the gateway module 4 in the modular microservice system includes the following contents:

[0139] The security authentication gateway 41, the load balancing gateway 42 and the secure Internet gateway 43 are sequentially connected in communication;

[0140] The security authentication gateway 41 is used to receive a business service request and perform security authentication on the business service request. If it is determined that the business service request passes the security authentication, the business service request is forwarded to the load balancing gateway 42;

[0141] The load balancing gateway 42 is used to perform load balancing processing on the business service request received from the security authentication gateway 41, and forward the business service request after load balancing processing to the secure Internet gateway 43;

[0142] The secure Internet gateway 43 is used to perform security checks on the business service requests received from the load balancing gateway 42. If it is determined that the business service request passes the security check, the business microservice module 11 is selected as the corresponding target business microservice module 11 based on the business type specified by the business service request and the operating status of each business microservice module 11 currently used to process the business type in the microservice module cluster 1, and the business service request is forwarded to the target business microservice module 11.

[0143] It is understandable that the security authentication gateway 41 can be implemented using an SSL gateway; an SSL gateway (Secure Sockets Layer Gateway) is a secure gateway device that can provide encrypted connection and identity authentication services for network applications through SSL and TLS protocols.

[0144] The load balancing gateway 42 can be implemented using an NGINX gateway; the NGINX gateway is a special proxy server that can not only process HTTP requests, but also process requests of multiple other protocols and act as an intermediary for communication between services.

[0145] The secure Internet gateway 43 (gateway) is also called an internetwork connector or a protocol converter. The gateway realizes network interconnection above the network layer and is a complex network interconnection device that is only used for interconnection of two networks with different high-level protocols. The gateway can be used for both wide area network interconnection and local area network interconnection. The secure Internet gateway 43 can also include a file stream gateway and a business stream gateway.

[0146] The entrance of the gateway module 4 architecture is to use the SSL gateway as the unified entrance of traffic, then pass through NGINX to be responsible for load balancing and request forwarding, and then use the gateway to handle the traffic management, authentication, current limiting and log processing of microservices. This design makes the system request first filtered by the gateway to ensure the legitimacy and security of the request.

[0147] In order to further improve the operational reliability, development efficiency, maintainability and version consistency of the monitoring module 5, in a modular microservice system provided in an embodiment of the present application, see Figure 5 , the monitoring module 5 in the modular microservice system includes the following contents:

[0148] Distributed link tracking unit 51.

[0149] The distributed link tracking unit 51 is respectively communicated with the gateway module 4 and each of the business microservice modules 11. The distributed link tracking unit 51 is used to obtain the respective operating status data of the gateway module 4 and each of the business microservice modules 11, so as to obtain the respective service health status of the gateway module 4 and each of the business microservice modules 11, as well as the call links and call durations between each of the business microservice modules 11.

[0150] It is understandable that the distributed link tracking unit 51 can be implemented using Skywalking, which is used for distributed link tracking to monitor the call links between microservices, service health status, call duration, etc. This is very important for fault location and troubleshooting, and helps the development team understand the performance bottlenecks and optimization space of the system.

[0151] In order to further improve the operational reliability, development efficiency, maintainability and version consistency of the middleware module 12, in a modular microservice system provided in an embodiment of the present application, see Figure 5 or Figure 6 , the middleware module 12 in the modular microservice system includes the following contents:

[0152] Distributed task scheduling unit 121 and message subscription unit 122.

[0153] The distributed task scheduling unit 121 is respectively connected to each of the business microservice modules 11 for communication, and the distributed task scheduling unit 121 is used to call each of the business microservice modules 11 to execute preset timed tasks and / or batch tasks;

[0154] The message subscription unit 122 is respectively communicated with each of the business microservice modules 11, and the message subscription unit 122 is used to perform asynchronous message processing between each of the business microservice modules 11, so that each of the business microservice modules 11 is decoupled through the message queue in the message subscription unit 122.

[0155] It is understandable that the distributed task scheduling unit 121 can be implemented using XXL-Job, that is, XXL-Job is integrated for task scheduling. XXL-Job is a distributed task scheduling platform for processing scheduled tasks and batch tasks. In this way, some batch processing logics can be triggered regularly, such as report generation, data synchronization, etc., to ensure unified scheduling and execution of tasks.

[0156] It is understandable that the message subscription unit 122 can be implemented using a RocketMQ cluster (message queue). RocketMQ is a distributed message middleware that integrates RocketMQ to provide asynchronous message processing. Specifically, RocketMQ is used for asynchronous message processing and supports event-driven architecture. Microservices are decoupled through message queues, especially in a high-concurrency environment. Some time-consuming operations can be processed through message queues, such as notifications after order creation, points issuance, etc., to reduce the coupling of services.

[0157] In addition, in one or more embodiments of the present application, common-parent means managing common dependencies, providing infrastructure support, and ensuring that all microservices use a unified version of the jar package. Easyexcel is used to process the read and write operations of Excel files. RPC is used to support remote procedure calls and simplify communication between services. Shardingsphere is used to achieve database sharding and read-write separation.

[0158] It should also be noted that although other configuration management tools (such as Consul) and message middleware (such as Kafka) can be used to replace Nacos and RocketMQ, these alternatives may lack certain functions.

[0159] In one or more embodiments of the present application, the modules in the modular microservice system interact with each other through REST API or RPC to ensure low coupling between modules. Configuration management can be performed through Nacos, which simplifies the management and maintenance of configuration. The upgrade of middleware components such as Redis and RocketMQ only requires modifying the code of the common basic service library, which greatly facilitates the handling of common problems. At the same time, flow control and fuse functions are implemented through sentinel to ensure the stability of the system. The unification of code style and middleware use is built through the service library, and business services can directly call public methods, thereby reducing duplicate code and improving development efficiency. Each module can be upgraded independently, reducing the risk of the overall system, making the complexity controllable, and easy to expand and integrate. New components only need to be configured in the service library to support new business needs.

[0160] That is to say, the modular microservice system provided by the embodiment of the present application provides a component set that is easy to integrate and expand by designing a modular microservice architecture, thereby solving the above shortcomings and improving the performance, maintainability and consistency of the system. The present application decomposes the microservice architecture into multiple independent modules, allowing developers to select and combine these modules according to specific needs to achieve a flexible and scalable architecture design. The common basic service library used by all microservices ensures the consistency of the jar package version and simplifies the upgrade and problem handling of the middleware components.

[0161] In order to further improve the applicability of the modular microservice system, in a modular microservice system provided in an embodiment of the present application, see Figure 7 The modular microservice system may also include the following contents:

[0162] Big data module 6. The big data module 6 is respectively connected to each of the business microservice modules 11 for communication, and is used to extract corresponding result data from a local data warehouse according to a big data call request sent by the business microservice module 11, and send the result data to the business microservice module 11; wherein the data warehouse includes a real-time data warehouse and an offline data warehouse.

[0163] AI module 7. The AI ​​module 7 is respectively connected to each of the business microservice modules 11 for communication. The AI ​​module 7 is used to call the local computing unit to obtain the corresponding calculation result data according to the calculation request sent by the business microservice module 11, and send the calculation result data to the business microservice module 11.

[0164] The local computing unit includes: NLP natural language processing unit, CV image processing unit, LLM large language model, model training unit and model reasoning unit. NLP is an interdisciplinary subject between computer science and linguistics, and its core is to enable computers to process and understand natural language. The research content of NLP includes multiple levels such as characters, words, phrases, sentences, paragraphs and chapters, aiming to enable computers to perform tasks such as language translation, sentiment analysis, and text summarization.

[0165] To further illustrate the above embodiments, the present application also provides a specific application example of a modular microservice system. Figure 8 The functional architecture diagram of the modular microservice system provided by the application example described above further provides the specific functional division of the big data module and the AI ​​module on the basis of the aforementioned embodiment, and also provides the detailed contents of the front end, terminal and infrastructure. Figure 8In the article, Vue means a JavaScript framework for building user interfaces; VueX is a state management tool for Vue; Vue Router means the official routing manager of Vue.js; Axios is a promise-based network request library that works in node.js and browsers, and it is isomorphic (that is, the same set of code can run in browsers and node.js); webpack is a code compilation tool with entry, exit, loader, and plug-in. Webpack is a static module packaging tool for modern JavaScript applications; ElementUI is an open source UI component library based on Vue.js, which provides developers with a set of elegant and flexible UI components; Iframe is an HTML tag that acts as a document in a document, or a floating frame (FRAME). The iframe element creates an inline frame (i.e., an inline frame) that contains another document; a bridge actually refers to a computer bus bridge, which is a hardware device used to connect different types of buses so that different computer subsystems can communicate with each other. UI is the abbreviation of User Interface, which means "user interface" in Chinese. It refers to the totality of all visual and auditory elements such as screens, menus, buttons, icons, text, audio, video, etc. involved in the interaction between people and computers or other electronic devices. UI design is the overall design of the human-computer interaction, operation logic, and beautiful interface of the software, aiming to make the operation of the software simple and comfortable, and fully reflect the positioning and characteristics of the software; Java is an object-oriented programming language; Rxjava is a responsive programming library, which is the Java version of ReactiveX (Reactive Extensions); Object-C is an object-oriented programming language that extends C; Dart is a computer programming language developed by Google, and was later recognized as a standard by Ecma (ECMA-408). It is used for development in the fields of web, server, mobile application and Internet of Things; flutter is Google's open source application development framework; electron is a cross-platform desktop application framework built using JavaScript, HTML and CSS; Swift is a new development language released by Apple at the 2014 WWDC Apple Developer Conference; IOS is a mobile operating system developed by Apple; Utils is a common programming term, which is the abbreviation of Utility.It is usually used to describe a collection of practical tools related to program design, as well as common functional modules required for a program to implement certain tasks; H5 refers to HTML5, the fifth generation hypertext markup language; PC (Personal Computer) refers to a multi-purpose computer with a size, price and performance suitable for personal use; DWD (Data Warehouse Detail) is a level in the data warehouse hierarchy, called the data warehouse detail layer. The main function of this layer is to synchronize ODS layer data from the business database, clean it and integrate it into the corresponding fact table; DWS (data website system) is a network management system and the main hardware device on computers and networks; Pytorch is an open source deep learning framework for machine learning and deep learning; TensorFlow is a symbolic mathematical system based on dataflow programming, which is widely used in the programming implementation of various machine learning algorithms; PaddlePaddle is a feature-rich, open source deep learning platform; DeepSpeed ​​is an open source deep learning training optimization library; TensorRT is a high-performance deep learning inference optimizer and runtime acceleration library, which can provide low-latency, high-throughput deployment inference for deep learning applications; OpenVino (Openvisualinference and neural network optimization) is an open visual inference and neural network optimization toolset; ONNXRuntine is a high-performance inference engine that supports a variety of hardware accelerators; vLLm is an efficient system for optimizing large language model (LLM) inference; On this basis, the application architecture diagram and data architecture diagram of the modular microservice system provided by the application example are as follows. Fig. 9 and Fig.10 shown.

[0166] In an example of a modular microservice system for executing financing operations, see Fig.11 The business types corresponding to each of the business microservice modules include: user center, financing service, document center, investment plan service, bank adaptation service, document review business service, loan business service, financing entity service, basic document review business, basic loan business, quotation inquiry service, file creation business service and file creation basic server (credit-base). The boxes in each business microservice module are examples of the addresses of the corresponding business microservice modules, which are for illustrative purposes only.

[0167] Therefore, the modular microservice system provided by this application has the following core improvements:

[0168] (1) Unified gateway integrated with multi-function modules

[0169] The gateway not only takes on the load balancing of requests, but also integrates multiple functions such as authentication, current limiting, log tracking, and traffic management. Compared with the traditional gateway that only acts as a reverse proxy, the innovation lies in the deep integration of traffic management, authentication, and current limiting functions at the gateway layer.

[0170] A deep integration method between gateway and microservices, especially the architecture design that integrates and uniformly manages multiple functional modules at the gateway layer to reduce system complexity, improve security and response performance.

[0171] (2) Unified solution for dynamic service discovery and configuration management

[0172] NACOS is used to unify service registration, service discovery, and configuration management, avoiding the complexity of manual integration between multiple components. The dynamic retrieval and update of services and configurations ensures the real-time and effectiveness of services in the changing environment of the system.

[0173] By integrating the service registration center and the configuration center, the system flexibility is improved, automatic discovery of service instances and real-time configuration management are supported, the operation and maintenance burden is reduced and scalability is improved.

[0174] (3) Unified gateway control strategy integrating distributed current limiting and fuse breaking

[0175] Integrate Sentinel with gateway to perform current limiting and circuit breaking management on all microservice requests passing through the gateway at the gateway level, avoiding the unavailability of a single microservice caused by overloaded requests and ensuring service quality through flexible strategies.

[0176] By implementing dynamic current limiting and circuit breaker control technology for downstream services at the gateway layer, the current limiting strategy can be flexibly adjusted based on the real-time operating status of the service, thereby improving the stability of the entire system.

[0177] (4) Message-driven microservice decoupling mechanism

[0178] RocketMQ is used to achieve asynchronous decoupling between microservices. Through event-driven architecture and message queues, the processing of high-concurrency requests is decoupled from the execution of core business within the system, improving the scalability of the system.

[0179] Use a message-driven mechanism to decouple the dependencies between microservices, so that calls between services can be processed asynchronously through messages. This can significantly improve the overall response efficiency of the system, especially in high concurrency and high throughput scenarios.

[0180] (5) Diversified storage management solutions and dynamic selection mechanisms

[0181] The system uses a variety of databases (Oracle, MySQL, MongoDB, Elasticsearch, Redis), and dynamically selects the appropriate data storage method according to business needs, using the MyBatis-parent framework to achieve persistence support for different databases.

[0182] Protection point: Diversified database integration methods based on business needs, especially through a unified persistence framework to automatically select and manage different data storage, thereby achieving high efficiency and flexibility in data persistence.

[0183] (6) Service monitoring mechanism based on distributed link tracking

[0184] Key point: Use Skywalking to monitor and track service links in a distributed environment, capture the call status and execution time between microservices, and help the development team quickly locate performance bottlenecks and fault points.

[0185] Protection point: Service monitoring under the microservice architecture is achieved through distributed link tracking, especially integrated into the service gateway and core services, so as to achieve real-time monitoring of service call paths, collection of performance data and fault diagnosis.

[0186] (7) High availability guarantee mechanism based on traffic scheduling and service priority

[0187] Key point: Gateway and sentinel work together to implement service priority management and traffic scheduling, which can ensure priority response of core services during traffic peaks and provide high availability of the system.

[0188] Protection point: Implement a dynamic traffic scheduling mechanism based on service priority in the microservice architecture, especially in the case of traffic peaks and resource shortages, to ensure the stable operation of core business services through intelligent scheduling.

[0189] (8) Unified management of distributed task scheduling

[0190] Key point: xxl-job is used to implement the scheduling management of distributed tasks, ensuring that the scheduled tasks of each business module can be managed and monitored in a unified manner to ensure efficient execution of tasks and abnormal recovery.

[0191] Protection point: Through a unified distributed task scheduling platform, batch tasks in each microservice are scheduled and managed, providing an efficient and reliable task scheduling solution.

[0192] It should be noted that, in one or more embodiments of the present application, English expressions may not be case-sensitive, that is, corresponding words of uppercase letters and lowercase letters have the same meaning.

[0193] It is understandable that each server in the modular microservice system can also be set to be completed in the client device according to actual application requirements. The specific selection can be based on the processing power of the client device and the limitations of the user's usage scenario. This application is not limited to this. If all operations are completed in the client device, the client device may also include a processor for specific processing such as business processing, outbound processing, or data storage processing required in the highway mobile payment process.

[0194] The client device may have a communication module (i.e., a communication unit) that can communicate with a remote server to achieve data transmission with the server. The server may include a server on the task scheduling center side, and other implementation scenarios may also include a server on an intermediate platform, such as a server on a third-party server platform that has a communication link with the task scheduling center server. The server may include a single computer device, or a server cluster consisting of multiple servers, or a server structure of a distributed device.

[0195] The server and the client device may communicate with each other using any suitable network protocol, including network protocols that have not yet been developed on the date of filing this application. The network protocols may include, for example, TCP / IP, UDP / IP, HTTP, HTTPS, etc. Of course, the network protocols may also include, for example, RPC (Remote Procedure Call Protocol) and REST (Representational State Transfer) protocols used on top of the above protocols.

[0196] In one or more embodiments of the present application, the server used in the embodiments of the present application may include a processor, a memory, a receiver and a transmitter, and the processor is used to perform the business processing, outbound processing or data storage processing in the highway mobile payment process mentioned in the above embodiments, wherein the processor and the memory may be connected via a bus or other means, taking the bus connection as an example. The receiver may be connected to the processor and the memory via a wired or wireless manner.

[0197] The processor may be a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0198] As a non-volatile computer-readable storage medium, the memory can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The processor executes various functional applications and data processing of the processor by running the non-volatile software programs, instructions and modules stored in the memory, that is, to realize the business processing, outbound processing or data storage processing in the highway mobile payment process in the above method embodiment.

[0199] The memory may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the processor, etc. In addition, the memory may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0200] In summary, the modular microservice system provided by this application has the following beneficial effects:

[0201] (1) Modular design: Each component is independent, which facilitates management and maintenance and reduces system coupling.

[0202] (2) Simplify integration: Use common-parent public packages to simplify service integration and reduce development complexity.

[0203] (3) Unified version management: Ensure the version consistency of the common basic service library code used by all microservices.

[0204] (4) Efficient fault handling: When a middleware fails, the public basic service library can be modified centrally, reducing maintenance costs.

[0205] (5) Consistent coding style: Standardized coding style and middleware usage standards improve development efficiency.

[0206] (6) Controllable complexity: Ensure that system complexity is controllable through modular and unified interface design.

[0207] (7) Easy to expand and integrate: When adding new components, you only need to add them to the service library, which facilitates system expansion and integration.

[0208] (8) Unified gateway integrates multi-functional modules: The gateway not only serves as a load balancer, but also integrates multiple functional modules such as authentication, flow control, and log processing, which simplifies the overall system structure and improves the gateway's management capabilities and system scalability.

[0209] (9) Dynamic service discovery and configuration center integration: Nacos enables dynamic service discovery and configuration management, which improves service flexibility, reduces the workload of manual maintenance, and enables services to automatically adapt to changes.

[0210] (10) Deep integration of distributed current limiting and circuit breaking: The combination of sentinel and gateway ensures that the interface of each microservice has the ability to control traffic, avoiding the risk of overloading a single service and improving the reliability and availability of the overall system.

[0211] (11) Decoupling design based on message queue: RocketMQ, as a message queue cluster, achieves decoupling between microservices through asynchronous processing and event-driven mode in high-concurrency scenarios, ensuring high availability of the system and improving user experience.

[0212] (12) Diversified storage solutions: Combining different databases such as Oracle, MySQL, MongoDB, Redis, ElasticSearch, etc., and selecting appropriate databases for different data types and access modes not only ensures data security and consistency, but also improves data access efficiency.

[0213] It should be understood by those skilled in the art that the exemplary components, systems and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software or a combination of the two. Whether it is specifically performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link via a data signal carried in a carrier.

[0214] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.

[0215] In the present application, features described and / or illustrated for one embodiment may be used in the same manner or in a similar manner in one or more other embodiments, and / or combined with features of other embodiments or replace features of other embodiments.

[0216] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the embodiments of the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A modular microservice system, characterized in that: include: Microservice module cluster, registration configuration module, gateway module, storage module and monitoring module; The microservice module cluster includes multiple business microservice modules and multiple middleware modules, and each of the business microservice modules is communicatively connected to each other, and each of the business microservice modules is communicatively connected to each of the middleware modules respectively; Each of the business microservice modules is respectively connected to the registration configuration module, the gateway module, the storage module and the monitoring module in a communication manner; The business microservice module is used to process the business service request distributed by the gateway module according to the service registration information and configuration information obtained in advance from the registration configuration module to obtain corresponding processing result data, send a data record consisting of the business service request and the corresponding processing result to the storage module so that the storage module stores the data record, and send the data record to the corresponding middleware module according to the configuration information; The business microservice module is also used to periodically send its own operating status data to the monitoring module, so that the monitoring module monitors the operating status data of each of the microservice modules.

2. The modular microservice system according to claim 1, characterized in that: The microservice module cluster also includes: The flow control and fuse components are respectively connected to the communication between each of the business microservice modules, and are used to monitor the operation status of each of the business microservice modules, and when a business microservice module with an abnormal operation status is detected, at least one of flow limiting, degradation and fuse processing is performed on the business microservice module; The load balancing unit is respectively connected to each of the business microservice modules for performing load balancing on each of the business microservice modules.

3. The modular microservice system according to claim 1, characterized in that: The storage module includes: a relational database, a time series database and a cache database; the relational database includes: an Oracle cluster and a MySQL cluster; Correspondingly, the microservice module cluster also includes: a persistent interaction interface and a storage interaction interface; The persistent interaction interface is used to send the data records of each of the business microservice modules to the Oracle cluster and / or the MySQL cluster for persistent storage; The storage interaction interface is used to send the data records of each of the business microservice modules to the time series database for time series storage, and send the data records of each of the business microservice modules to the cache database for distributed cache processing.

4. The modular microservice system according to claim 3, characterized in that: The storage module also includes: a distributed document storage database; The distributed document storage database includes: a document database and a document retrieval analysis database; The document database is used to obtain the semi-structured data or unstructured data corresponding to each of the business microservice modules based on the storage interaction interface for distributed storage; The document retrieval and analysis database is used to perform document retrieval and aggregation analysis on the semi-structured data or unstructured data corresponding to each of the business microservice modules obtained based on the storage interaction interface, and store the obtained document retrieval and aggregation analysis result data.

5. The modular microservice system according to claim 1, characterized in that: The registration configuration module includes: a registration center unit and a configuration center unit; The registration center unit is respectively connected to the gateway module and each of the business microservice modules for communication, and the registration center unit is used to register the service and store the corresponding service registration information, and send the service registration information to the gateway module and each of the business microservice modules respectively; The configuration center unit is respectively communicated with the gateway module and each of the business microservice modules, and is used to perform service configuration and store corresponding service configuration information, and send the service configuration information to the gateway module and each of the business microservice modules respectively.

6. The modular microservice system according to claim 1, characterized in that: The gateway module includes: a security authentication gateway, a load balancing gateway and a secure Internet gateway that are sequentially connected in communication; The security authentication gateway is used to receive a business service request and perform security authentication on the business service request. If it is determined that the business service request passes the security authentication, the business service request is forwarded to the load balancing gateway; The load balancing gateway is used to perform load balancing processing on the business service request received from the security authentication gateway, and forward the business service request after load balancing processing to the secure Internet gateway; The secure Internet gateway is used to perform security checks on the business service requests received from the load balancing gateway. If it is determined that the business service request passes the security check, the business microservice module is selected as the corresponding target business microservice module based on the business type specified by the business service request and the operating status of each business microservice module in the microservice module cluster currently used to process the business type, and the business service request is forwarded to the target business microservice module.

7. The modular microservice system according to claim 1, characterized in that: The monitoring module includes: a distributed link tracking unit; The distributed link tracking unit is respectively communicated with the gateway module and each of the business microservice modules, and is used to obtain the respective operating status data of the gateway module and each of the business microservice modules, so as to obtain the respective service health status of the gateway module and each of the business microservice modules, as well as the call links and call durations between each of the business microservice modules.

8. The modular microservice system according to claim 1, characterized in that: The middleware module includes: a distributed task scheduling unit and a message subscription unit; The distributed task scheduling unit is respectively connected to each of the business microservice modules for communication, and the distributed task scheduling unit is used to call each of the business microservice modules to execute preset timed tasks and / or batch tasks; The message subscription unit is respectively communicated with each of the business microservice modules, and is used to perform asynchronous message processing between the business microservice modules, so that each of the business microservice modules is decoupled through the message queue in the message subscription unit.

9. The modular microservice system according to claim 1, characterized in that: Also includes: Big data module; The big data module is respectively communicated with each of the business microservice modules, and is used to extract corresponding result data from the local data warehouse according to the big data call request sent by the business microservice module, and send the result data to the business microservice module; wherein the data warehouse includes a real-time data warehouse and an offline data warehouse.

10. The modular microservice system according to claim 1, characterized in that: Also includes: AI module; The AI ​​module is respectively communicated with each of the business microservice modules. The AI ​​module is used to call the local computing unit to obtain the corresponding calculation result data according to the calculation request sent by the business microservice module, and send the calculation result data to the business microservice module.

Images