Audit service system realized based on micro-service architecture

Abstract

The invention relates to an audit service system realized based on a micro-service architecture, and relates to the technical field of computers. The auditing business system comprises a plurality of sub-auditing systems realized based on a pre-constructed standard micro-service architecture; each sub-auditing system comprises a plurality of standard micro-services for realizing different business functions; the standard micro-service architecture provides a unified service interface standard for different standard micro-services; for any two sub-auditing systems in the auditing service system, data exchange between the two sub-auditing systems is realized through a data exchange channel between the two sub-auditing systems and provided by a standard micro-service architecture. According to the auditing business system, unified standard constraint can be carried out on the services of the sub-auditing systems, standard unification and protocol unification of the services are guaranteed, negotiation between the sub-auditing systems is not needed for data exchange between the services, the sub-auditing systems do not need to develop and negotiate data exchange standards respectively, and therefore the data exchange efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an audit business system implemented based on a microservice architecture. Background Art

[0002] With the rapid development of information technology, audit informatization has become an important means of audit work. As a supporting platform for audit work, the data exchange capability of the audit information system directly affects the quality and efficiency of audit work. At present, my country's audit informatization construction has achieved remarkable results, but most companies still mainly use single application architecture, stand-alone system, and stand-alone tool application in audit informatization, and there are certain difficulties in data exchange.

[0003] In traditional technology, data interaction between different audit systems is mainly achieved through traditional microservice architecture. However, traditional microservice architecture only provides the ability to integrate different systems, and does not impose unified normative constraints on system services, resulting in inconsistent standards and protocols. Data exchange between services requires negotiation between business systems, and each business system needs to develop and negotiate data exchange standards, resulting in low data exchange efficiency. Summary of the invention

[0004] Based on this, it is necessary to provide an audit business system based on microservice architecture that can improve data exchange efficiency in response to the above technical problems. Specifically, the audit business system based on microservice architecture can uniformly regulate and constrain the services of the sub-audit systems, ensuring the uniformity of service standards and protocols. Data exchange between services does not require negotiation between the sub-audit systems, nor does it require the sub-audit systems to develop and negotiate data exchange standards, thereby improving data exchange efficiency.

[0005] The present application provides an audit business system implemented based on a microservice architecture, wherein the audit business system includes multiple sub-audit systems implemented based on a pre-built standard microservice architecture; each of the sub-audit systems includes multiple standard microservices for implementing different business functions; the standard microservice architecture provides a unified service interface standard for different standard microservices;

[0006] For any two sub-audit systems in the audit business system, data exchange between the two sub-audit systems is achieved through a data exchange channel between the two sub-audit systems and provided by the standard microservice architecture.

[0007] In one embodiment, the data exchange channel includes an unstructured data exchange channel; the unstructured data exchange channel is used to support the unstructured data exchange between the two sub-audit systems.

[0008] In one embodiment, the data exchange channel is implemented based on a message queue; the message queue is used to temporarily cache the unstructured data involved in the unstructured data exchange process between the two sub-audit systems.

[0009] In one embodiment, the data exchange channel further includes a distributed storage network; when it is determined that there is a sharing demand for the unstructured data, the unstructured data is permanently stored in the distributed storage network.

[0010] In one embodiment, the unstructured data includes at least one of text data, audio data and video data.

[0011] In one embodiment, the standard microservices include basic services and public services; the basic services include a user login service for implementing the user login function of the sub-audit system, and a role maintenance service for implementing the role maintenance function of the sub-audit system; the public services include a unified to-do service for implementing the to-do task reminder function of the sub-audit system, and a unified message service for implementing the message reminder function of the sub-audit system.

[0012] In one embodiment, the role maintenance service is used to maintain the system role and business role of the sub-audit system; one logged-in user of the sub-audit system corresponds to one system role; and one logged-in user corresponds to at least one business role.

[0013] In one embodiment, the user login service is implemented based on a token verification mechanism; the user login service is used to implement secure login to the sub-audit system based on the token verification mechanism.

[0014] In one embodiment, the front-end page of the audit business system is implemented based on a preset front-end application framework; the front-end application framework includes multiple application sandboxes; each application sandbox is used to implement a front-end page of the sub-audit system.

[0015] In one embodiment, the standard microservice architecture is implemented based on springboot, java8, mysql and redis.

[0016] The above-mentioned audit business system implemented based on the microservice architecture includes multiple sub-audit systems implemented based on the pre-built standard microservice architecture; each sub-audit system includes multiple standard microservices for implementing different business functions; the standard microservice architecture provides a unified service interface standard for different standard microservices; for any two sub-audit systems in the audit business system, the data exchange between the two sub-audit systems is realized through the data exchange channel between the two sub-audit systems and provided by the standard microservice architecture. Compared with the traditional audit business system implemented based on the traditional microservice architecture, the multiple sub-audit systems contained in the audit business system of this application are all implemented based on the standard microservice architecture, each sub-audit system includes multiple standard microservices for implementing different business functions, and the standard microservice architecture provides a unified service interface standard for different standard microservices. The standard microservice architecture proposed in this application not only provides the ability to integrate different sub-audit systems, but also uniformly regulates and constrains the services of the sub-audit systems, ensuring the standardization and protocol unification of services, and the data exchange between services does not require negotiation between the sub-audit systems, nor does it require each sub-audit system to develop and negotiate data exchange standards, thereby improving the efficiency of data exchange. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A system block diagram of an audit business system implemented based on a microservice architecture in one embodiment;

[0018] Figure 2 is a schematic diagram of a data exchange channel in one embodiment;

[0019] Figure 3 A schematic diagram of a data exchange channel in another embodiment;

[0020] Figure 4 A schematic diagram of system role maintenance in one embodiment;

[0021] Figure 5 A schematic diagram of a login based on a token authentication mechanism in one embodiment;

[0022] Figure 6 A schematic diagram of a login based on a token authentication mechanism in another embodiment;

[0023] Figure 7 A schematic diagram of a front-end application framework in an embodiment;

[0024] Figure 8 is an internal structure diagram of a computer device in one embodiment;

[0025] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in another embodiment. DETAILED DESCRIPTION

[0026] 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 accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0027] In traditional technology, data interaction between different audit systems is mainly achieved through traditional microservice architecture. However, traditional microservice architecture only provides the ability to integrate different systems, and does not impose unified normative constraints on system services, resulting in inconsistent standards and protocols. Data exchange between services requires negotiation between business systems, and each business system needs to develop and negotiate data exchange standards, resulting in low data exchange efficiency.

[0028] The audit business system proposed in this application includes multiple sub-audit systems implemented based on a pre-built standard microservice architecture; each sub-audit system includes multiple standard microservices for implementing different business functions; the standard microservice architecture provides a unified service interface standard for different standard microservices; for any two sub-audit systems in the audit business system, the data exchange between the two sub-audit systems is realized through the data exchange channel between the two sub-audit systems and provided by the standard microservice architecture. Compared with the traditional audit business system implemented based on the traditional microservice architecture, the multiple sub-audit systems contained in the audit business system of this application are all implemented based on the standard microservice architecture, each sub-audit system includes multiple standard microservices for implementing different business functions, and the standard microservice architecture provides a unified service interface standard for different standard microservices. The standard microservice architecture proposed in this application not only provides the ability to integrate different sub-audit systems, but also uniformly regulates and constrains the services of the sub-audit systems, ensuring the standard unification of services, the unified protocol, and the data exchange between services does not require negotiation between the sub-audit systems, nor does it require each sub-audit system to develop and negotiate data exchange standards, thereby improving the efficiency of data exchange.

[0029] In one embodiment, Figure 1 As shown, an audit business system based on a microservice architecture is proposed. The audit business system includes multiple sub-audit systems implemented based on a pre-built standard microservice architecture; each sub-audit system includes multiple standard microservices for implementing different business functions; the standard microservice architecture provides a unified service interface standard for different standard microservices; for any two sub-audit systems in the audit business system, data exchange between the two sub-audit systems is achieved through a data exchange channel between the two sub-audit systems and provided by the standard microservice architecture.

[0030] Among them, the standard microservice architecture not only provides the ability to integrate different sub-audit systems, but also uniformly regulates and constrains the services of the sub-audit systems, provides a unified service interface standard, and ensures the standard and protocol uniformity of services. The standard microservice architecture adopts a decentralized architecture mode. Each standard microservice is an independent and independently deployable unit. They interact directly through lightweight communication mechanisms (such as HTTP / REST API, message queues, etc.). Each standard microservice is usually small and is responsible for only a small part of the functions in the sub-audit system, that is, the single responsibility principle. Due to its decentralized nature, the standard microservice architecture is usually more flexible and easy to expand. A single standard microservice can be independently expanded or updated according to demand. Standard microservices encourage the use of the technology stack that best suits the needs, which means that different standard microservices can use different programming languages ​​and data storage technologies. In terms of deployment, each standard microservice can be independently deployed and operated, and is usually used in combination with containerization and automated deployment tools (such as Docker and Kubernetes) to improve the flexibility and automation of deployment. It is suitable for fast-growing Internet companies and innovative projects, and scenarios that require rapid iteration and frequent deployment.

[0031] In one embodiment, the data exchanged between the two sub-audit systems may be structured data, semi-structured data, and unstructured data, wherein the semi-structured data may include data in the form of html, JSON, and XML, and the unstructured data may include data of the type of text, audio, and video.

[0032] In the above-mentioned audit business system implemented based on the microservice architecture, the audit business system includes multiple sub-audit systems implemented based on the pre-built standard microservice architecture; each sub-audit system includes multiple standard microservices for implementing different business functions; the standard microservice architecture provides a unified service interface standard for different standard microservices; for any two sub-audit systems in the audit business system, the data exchange between the two sub-audit systems is realized through the data exchange channel between the two sub-audit systems and provided by the standard microservice architecture. Compared with the traditional audit business system implemented based on the traditional microservice architecture, the multiple sub-audit systems contained in the audit business system of this application are all implemented based on the standard microservice architecture, each sub-audit system includes multiple standard microservices for implementing different business functions, and the standard microservice architecture provides a unified service interface standard for different standard microservices. The standard microservice architecture proposed in this application not only provides the ability to integrate different audit systems, but also uniformly regulates and constrains the services of the sub-audit systems, ensuring the standard unification of services, the unified protocol, and the data exchange between services does not require negotiation between the sub-audit systems, nor does it require each sub-audit system to develop and negotiate data exchange standards, thereby improving the efficiency of data exchange.

[0033] In one embodiment, the data exchange channel includes an unstructured data exchange channel; the unstructured data exchange channel is used to support unstructured data exchange between two sub-audit systems.

[0034] Among them, unstructured data can include text, audio, video and other types of data.

[0035] In the above embodiment, the standard microservice architecture can realize the unstructured data exchange between the two sub-audit systems by providing an unstructured data exchange channel.

[0036] In one embodiment, the data exchange channel is implemented based on a message queue; the message queue is used to temporarily cache the unstructured data involved in the unstructured data exchange process between the two sub-audit systems.

[0037] Among them, message queue (MQ) is a method of asynchronous communication between services, which allows a time delay between sending and receiving messages (ie data), and provides functions such as reliable message delivery, buffering, and persistence.

[0038] In one embodiment, common message queue (MQ) products include RabbitMQ, Apache Kafka, ActiveMQ, etc.

[0039] In one embodiment, Figure 2 As shown in the figure, sub-audit system 1 and sub-audit system 2 are connected to the message queue service through the message queue (MQ) and create messages to send to the specified topic. The message monitoring service calls the unified to-do cache service to consume messages according to the topic, and finally processes the to-do tasks or other different topic contents uniformly and stores them in a temporary table. The user logs in to the unified portal or refreshes to display the specific content.

[0040] In the above embodiments, the data exchange channel is implemented based on the message queue, which can allow a time delay between sending and receiving data and provide functions such as reliable message delivery, buffering, and persistence.

[0041] In one embodiment, the data exchange channel further includes a distributed storage network; when it is determined that there is a sharing demand for the unstructured data, the unstructured data is permanently stored in the distributed storage network.

[0042] In one embodiment, Figure 3As shown in the figure, the data exchange channel is implemented using MQ (message queue) and IPFS (distributed storage network) technologies, which mainly solves the coordination of business and unstructured data exchange between sub-audit systems through asynchronous calls, especially when the application is deployed at multiple levels or attachments have sharing requirements. The data exchange channel process is: use MQ to design message topics that require coordination or asynchronous calls, build an IPFS cluster, and use the IPFS distributed storage capabilities to achieve the storage of unstructured data in each sub-audit system. Build a message consumption service and determine whether there is a need to share unstructured data in the consumption service. When processing messages with unstructured data sharing requirements, send get commands to the nearest node of the IPFS network to synchronize data and implement permanent storage of files through pin add.

[0043] In the above embodiment, by introducing a distributed storage network in the data exchange channel, permanent storage of unstructured data can be achieved.

[0044] In one embodiment, the unstructured data includes at least one of text data, audio data, and video data.

[0045] In the above embodiment, by limiting the unstructured data to include at least one of text data, audio data and video data, the audit business system can support the interaction of diverse unstructured data.

[0046] In one embodiment, the standard microservices include basic services and public services; the basic services include a user login service for implementing the user login function of the sub-audit system, and a role maintenance service for implementing the role maintenance function of the sub-audit system; the public services include a unified to-do service for implementing the to-do task reminder function of the sub-audit system, and a unified message service for implementing the message reminder function of the sub-audit system.

[0047] In the above embodiment, basic services and public services are provided through a standard microservice architecture, which provides powerful native support capabilities for the development of the audit business system and the collaborative interaction of various sub-audit systems.

[0048] In one embodiment, the role maintenance service is used to maintain the system roles and business roles of the sub-audit system; one logged-in user of the sub-audit system corresponds to one system role; and one logged-in user corresponds to at least one business role.

[0049] In one embodiment, Figure 4As shown in the figure, the system role is used to clarify the use or management rights of the user relative to the sub-audit system (i.e., sub-application) through role authorization. The business role is used to clarify the role of the user when handling business in the sub-audit system (for example, auditor, statistician, toll collector, manager, supervisor, etc.). A user can only have one "system role" but can have multiple "business roles" to ensure the correct operation of the business process.

[0050] In the above embodiment, a user is limited to have only one system role but multiple business roles, thereby ensuring the correct operation of the audit business process in the audit business system.

[0051] In one embodiment, the user login service is implemented based on a token verification mechanism; the user login service is used to implement secure login to the sub-audit system based on the token verification mechanism.

[0052] In one embodiment, Figure 5 As shown in the figure, all services use the same token verification mechanism. The design also considers supporting a large number of users and service expansion, so that users can log in and out easily. After the user logs in and authenticates with the username, password, and verification code, the service generates a token and returns it to the client, and saves the token in the server's secure storage. In subsequent service access, token validity verification can be used to determine whether the user has access rights, ensuring the security requirements for service access.

[0053] In one embodiment, Figure 6 As shown in the figure, when the client calls the service, the basic library of the standard microservice framework will intercept the service request and actively verify the validity of the token.

[0054] In the above embodiment, the user login service is implemented based on the token verification mechanism, which can ensure the secure login of the sub-audit system.

[0055] In one embodiment, the front-end page of the audit business system is implemented based on a preset front-end application framework; the front-end application framework includes multiple application sandboxes; each application sandbox is used to implement the front-end page of a sub-audit system.

[0056] In one embodiment, Figure 7As shown, the front-end application framework can be built based on the Alibaba Qiankun framework. The front-end application framework allows the main application (i.e., the audit business system) to maintain a global state, which can be read and updated by all sub-applications (i.e., the sub-audit system). In addition to the above functions, the front-end application framework mainly implements the "To-Do Center", "Message Center", "News Center", "Unified Sub-Application Portal" and "Unified Permission Management Visual Management Module" functions. The unified permission management visual management module implements the management and maintenance of users, roles, organizations, and role permissions, as well as the authorization of the sub-audit system function menu. The To-Do Center and Message Center provide a unified visual display and processing portal for the sub-audit system. The unified sub-application portal displays the system icon, and the sub-audit system can be directly entered by double-clicking. The front-end application framework provides the sub-audit system with the ability to integrate front-end applications.

[0057] In the above embodiment, the sandbox technology ensures that the styles and global variables between the sub-audit systems will not interfere with each other, maintaining the independence and stability of the sub-audit systems. In addition, the routing management is convenient for easily handling routing jumps and nesting between the audit business system and the sub-audit system. The front-end application framework of this application provides the sub-audit system with the ability to integrate front-end applications.

[0058] In one embodiment, the standard microservice architecture is implemented based on springboot, java8, mysql and redis.

[0059] In one embodiment, an audit business system based on a microservice architecture is proposed, wherein the audit business system includes multiple sub-audit systems implemented based on a pre-built standard microservice architecture; each sub-audit system includes multiple standard microservices for implementing different business functions; the standard microservice architecture provides a unified service interface standard for different standard microservices; for any two sub-audit systems in the audit business system, the data exchange between the two sub-audit systems is realized through a data exchange channel between the two sub-audit systems and provided by the standard microservice architecture. The data exchange channel includes an unstructured data exchange channel; the unstructured data exchange channel is used to support the unstructured data exchange between the two sub-audit systems. The data exchange channel is implemented based on a message queue; the message queue is used to temporarily cache the unstructured data involved in the unstructured data exchange process between the two sub-audit systems. The data exchange channel also includes a distributed storage network; when it is determined that there is a sharing demand for the unstructured data, the unstructured data is permanently stored in the distributed storage network. The unstructured data includes at least one of text data, audio data and video data. Standard microservices include basic services and public services; basic services include user login services for implementing the user login function of the sub-audit system, and role maintenance services for implementing the role maintenance function of the sub-audit system; public services include unified to-do services for implementing the to-do task reminder function of the sub-audit system, and unified message services for implementing the message reminder function of the sub-audit system. The role maintenance service is used to maintain the system roles and business roles of the sub-audit system; a logged-in user of the sub-audit system corresponds to a system role; a logged-in user corresponds to at least one business role. The user login service is implemented based on the token verification mechanism; the user login service is used to implement secure login of the sub-audit system based on the token verification mechanism. The front-end page of the audit business system is implemented based on the preset front-end application framework; the front-end application framework contains multiple application sandboxes; each application sandbox is used to implement the front-end page of a sub-audit system. The standard microservice architecture is implemented based on springboot, java8, mysql and redis.

[0060] In the above-mentioned audit business system implemented based on the microservice architecture, the audit business system includes multiple sub-audit systems implemented based on the pre-built standard microservice architecture; each sub-audit system includes multiple standard microservices for implementing different business functions; the standard microservice architecture provides a unified service interface standard for different standard microservices; for any two sub-audit systems in the audit business system, the data exchange between the two sub-audit systems is realized through the data exchange channel between the two sub-audit systems and provided by the standard microservice architecture. Compared with the traditional audit business system implemented based on the traditional microservice architecture, the multiple sub-audit systems contained in the audit business system of this application are all implemented based on the standard microservice architecture, each sub-audit system includes multiple standard microservices for implementing different business functions, and the standard microservice architecture provides a unified service interface standard for different standard microservices. The standard microservice architecture proposed in this application not only provides the ability to integrate different audit systems, but also uniformly regulates and constrains the services of the sub-audit systems, ensuring the standard unification of services, the unified protocol, and the data exchange between services does not require negotiation between the sub-audit systems, nor does it require each sub-audit system to develop and negotiate data exchange standards, thereby improving the efficiency of data exchange.

[0061] It can be understood that the data exchange channel provided by the standard microservice architecture in this application solves the problem that data cannot be exchanged smoothly due to inconsistent data formats and interface standards between sub-audit systems. A large amount of unstructured data no longer requires auditors to spend a lot of time and energy to process due to synchronization problems. This application unifies the data access standard through the standard microservice architecture, provides a unified authentication mechanism for service access, avoids illegal access to data, and ensures data security risks. This application uses IPFS (distributed storage network) to process data through asynchronous requests through the standard microservice architecture, ensuring the efficiency and accuracy of data exchange. This application provides basic services and public services through the standard microservice architecture, providing strong native support capabilities for enterprise and audit system development and collaborative interaction of various audit systems.

[0062] It should be understood that, although each step in the flow chart of the above-mentioned embodiments is shown in order, these steps are not necessarily performed in order. Unless there is a clear explanation in this article, the execution of these steps does not have strict order restrictions, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the above-mentioned embodiments may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these sub-steps or stages is not necessarily performed in order, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0063] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 8 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements the data exchange steps between any two sub-audit systems in the audit business system.

[0064] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as follows: Fig. 9 As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, it implements the data exchange steps between any two sub-audit systems in the audit business system. The display unit of the computer device is used to form a visually visible image, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covered on the display screen, or a button, trackball or touchpad set on the computer device casing, or an external keyboard, touchpad or mouse, etc.

[0065] Those skilled in the art will understand that Figure 8 and Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0066] In one embodiment, a computer device is also provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, a data exchange step between any two sub-audit systems in the above-mentioned audit business system is implemented.

[0067] In one embodiment, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a processor, the data exchange steps between any two sub-audit systems in the above-mentioned audit business system are implemented.

[0068] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements the data exchange steps between any two sub-audit systems in the above-mentioned audit business system.

[0069] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0070] A person of ordinary skill in the art can understand that the implementation of all or part of the process of the data exchange step between any two sub-audit systems in the above-mentioned audit business system can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the process of the data exchange step between any two sub-audit systems in the above-mentioned audit business system. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0071] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0072] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. An audit business system based on microservice architecture, characterized in that: The audit business system includes multiple sub-audit systems implemented based on a pre-built standard microservice architecture; each of the sub-audit systems includes multiple standard microservices for implementing different business functions; The standard microservice architecture provides a unified service interface standard for different standard microservices; For any two sub-audit systems in the audit business system, data exchange between the two sub-audit systems is achieved through a data exchange channel between the two sub-audit systems and provided by the standard microservice architecture.

2. The audit business system according to claim 1, characterized in that: The data exchange channel includes an unstructured data exchange channel; the unstructured data exchange channel is used to support the unstructured data exchange between the two sub-audit systems.

3. The audit business system according to claim 2, characterized in that: The data exchange channel is implemented based on a message queue; the message queue is used to temporarily cache the unstructured data involved in the unstructured data exchange process between the two sub-audit systems.

4. The audit business system according to claim 3, characterized in that: The data exchange channel also includes a distributed storage network; when it is determined that there is a sharing demand for the unstructured data, the unstructured data is permanently stored in the distributed storage network.

5. The audit business system according to claim 2, characterized in that: The unstructured data includes at least one of text data, audio data and video data.

6. The audit business system according to claim 1, characterized in that: The standard microservices include basic services and public services; the basic services include a user login service for implementing the user login function of the sub-audit system, and a role maintenance service for implementing the role maintenance function of the sub-audit system; the public services include a unified to-do service for implementing the to-do task reminder function of the sub-audit system, and a unified message service for implementing the message reminder function of the sub-audit system.

7. The audit business system according to claim 6, characterized in that: The role maintenance service is used to maintain the system role and business role of the sub-audit system; one logged-in user of the sub-audit system corresponds to one system role; and one logged-in user corresponds to at least one business role.

8. The auditing business system according to claim 6, characterized in that: The user login service is implemented based on a token verification mechanism; the user login service is used to implement secure login to the sub-audit system based on the token verification mechanism.

9. The audit business system according to claim 1, characterized in that: The front-end page of the audit business system is implemented based on a preset front-end application framework; the front-end application framework includes multiple application sandboxes; each application sandbox is used to implement a front-end page of the sub-audit system.

10. The audit business system according to any one of claims 1 to 9, characterized in that: The standard microservice architecture is implemented based on springboot, java8, mysql and redis.

Images