Receipt engine-based micro-service platform and implementation method

Abstract

The embodiment of the invention provides a micro-service platform based on a receipt engine and an implementation method, and the micro-service platform comprises a micro-service coordinator which is used for actively discovering a receipt engine service in the micro-service platform according to a service identifier through a self-defined service route, the interaction information between the micro front-end engine and the receipt engine service is forwarded based on the service identifier; the search engine service is used for collecting business data in all the receipt engine services, and the business data are used as global data indexes after dimension reduction; the receipt engine service is used for receiving the service request, executing corresponding processing based on the service request, carrying a processing result in a service response and sending the service response to the micro-service coordinator; and the micro-front-end engine is used for isolating UI components of different receipt engine services through the sandbox, interacting with the receipt engine services through the micro-service coordinator based on the service identifier, and rendering the UI components in the sandbox based on the service identifier.

Description

Technical Field

[0001] This document relates to the field of computer technology, and in particular to a microservice platform based on a document engine and an implementation method. Background Art

[0002] Low Code is a visual application development method that uses less code and delivers applications at a faster speed. It automates the code that programmers don’t want to develop, which is called low code.

[0003] Low-code is a set of digital technology tool platforms that enable rapid construction, data orchestration, ecosystem connection, and middle-office services based on more efficient methods such as graphical drag and drop and parameterized configuration. Scenario application innovation in digital transformation is achieved with little or no code; from the perspective of low-code technology paths, it can usually be divided into table-driven, form-driven, data model-driven, domain model-driven, etc.; document engine technology is a low-code implementation of data model-driven. The core of the engine revolves around business data definitions, including data names, data types, etc. It abstracts forms to display and present business processes, establishes business relationships through data models at the practical level, and supports complete business models through forms and processes. It is highly flexible and can meet the needs of complex enterprise scenario development and overall system development. It is suitable for personalized customization of core business innovation scenarios of medium and large enterprises.

[0004] Microservice architecture is a cloud-native architecture approach that includes many loosely coupled and independently deployable small components or services in a single application. These services usually have their own technology stack, including databases and data management models; they communicate with each other through a REST API, event streams, and message brokers; among them, the microservice architecture based on SpringCloud uses the interface REST address as the basic unit of the service, and the microservice gateway is organized according to service capabilities.

[0005] Usually, low-code platforms are based on engines, using data to render UI and execute business logic, and can themselves be developed through a microservice architecture. To implement a business system based on a low-code platform, the platform is generally deployed to the server first, and then the business rules are graphically implanted into the platform database through the system configuration interface. The low-code engine provides user functions for the system, so the implementation results do not have the ability to be split by business modules.

[0006] At present, all large enterprises generally have the demand for multiple business models, and often need to support the deployment of system functions for multiple business lines in a set of system platforms; due to the characteristics of low-code platforms, the result of implementation is that a large number of business logic configurations are integrated into a set of platforms, resulting in a single system with a large amount of data, complex business logic, high maintenance difficulty, and lack of decomposability. Summary of the invention

[0007] The purpose of the present invention is to provide a microservice platform based on a document engine and an implementation method, aiming to solve the above-mentioned problems in the prior art.

[0008] The present invention provides a microservice platform based on a document engine, comprising:

[0009] A microservice coordinator, which is arranged at the server end and connected to the search engine service, is used to actively discover the document engine service in the microservice platform according to the service identifier through a customized service route, and forward the interaction information between the micro front-end engine of the client and the document engine service based on the service identifier;

[0010] A search engine service, arranged at the server end and connected to the document engine service, for collecting business data from all document engine services, reducing the dimension of the business data and using it as a global data index, wherein the data index includes the service identifier;

[0011] The document engine service is provided at the server end and is linked to the microservice coordinator to receive the service request, perform corresponding processing based on the service request, and send the processing result to the microservice coordinator in the service response;

[0012] The micro front-end engine is arranged on the client and is used to isolate the UI components of different document engine services through a sandbox, interact with the document engine service through the micro service coordinator based on the service identifier, and render the UI components in the sandbox based on the service identifier.

[0013] The present invention provides a method for implementing a microservice platform based on a document engine, which is used for the above-mentioned microservice platform, including:

[0014] Based on the customized service routing, the microservice coordinator actively discovers the document engine service in the microservice platform according to the service identifier, and forwards the interaction information between the client's micro front-end engine and the document engine service based on the service identifier;

[0015] Collecting business data from all document engine services through a search engine service, reducing the dimension of the business data and using it as a global data index, wherein the data index includes the service identifier;

[0016] Receive the service request through the document engine service, perform corresponding processing based on the service request, and send the processing result to the microservice coordinator in the service response;

[0017] The micro-frontend engine uses a sandbox to isolate UI components of different document engine services, interacts with the document engine service through the microservice coordinator based on the service identifier, and renders the UI components in the sandbox based on the service identifier.

[0018] An embodiment of the present invention also provides an electronic device, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the above-mentioned method for implementing a microservice platform based on a document engine.

[0019] An embodiment of the present invention further provides a computer-readable storage medium, on which a program for implementing information transmission is stored. When the program is executed by a processor, the steps of the above-mentioned method for implementing a microservice platform based on a document engine are implemented.

[0020] By using the embodiments of the present invention, the dynamic horizontal expansion capability of the low-code platform is supported through the integration of microservices through custom routing. This enables large enterprises to have the ability to deploy low-code platforms separately according to the actual business line situation, implement system business functions, and finally complete the integration of all business lines into a unified large platform. It can greatly improve the flexibility, scalability and stability of using low-code platforms to implement large-scale enterprise software systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0022] Figure 1 is a schematic diagram of a microservice platform based on a document engine according to an embodiment of the present invention;

[0023] Figure 2 is a schematic diagram of an example of a microservice deployment topology according to an embodiment of the present invention;

[0024] Figure 3 is a schematic diagram of microservice front-end integration according to an embodiment of the present invention;

[0025] Figure 4 Schematic diagram of microservice backend request routing in an embodiment of the present invention;

[0026] Figure 5 It is a flow chart of a method for implementing a microservice platform based on a document engine according to an embodiment of the present invention;

[0027] Figure 6 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the following will be combined with the drawings in one or more embodiments of this specification to clearly and completely describe the technical solutions in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0029] Device Example 1

[0030] According to an embodiment of the present invention, a microservice platform based on a document engine is provided. Figure 1 is a schematic diagram of a microservice platform based on a document engine according to an embodiment of the present invention, such as Figure 1 As shown, the microservice platform based on the document engine according to an embodiment of the present invention includes a server 10 and a client 12, specifically:

[0031] The microservice coordinator 101 is provided at the server end 10 and connected to the search engine service 103, and is used to actively discover the document engine service in the microservice platform according to the service identifier through a customized service routing, and forward the interaction information between the micro front-end engine of the client and the document engine service based on the service identifier; the microservice coordinator 101 is specifically used for:

[0032] Through customized service routing, the document engine service in the microservice platform is actively discovered based on the service identifier, the service request carrying the service identifier sent by the client is obtained, and the service request is forwarded to the corresponding document engine service according to the service identifier, and the service response fed back by the document engine service is accepted, and the service identifier is added to the service response and sent to the client, wherein the service identifier is used to distinguish the REST addresses of different document engine services.

[0033] A search engine service 102, which is provided at the server 10 and connected to the document engine service 103, is used to collect business data from all document engine services, and use the business data as a global data index after reducing the dimension, wherein the data index includes the service identifier;

[0034] The document engine service 103 is arranged at the server end 10 and connected to the microservice coordinator 101, and is used to receive the service request, perform corresponding processing based on the service request, and send the processing result to the microservice coordinator in the service response; the document engine service is: a distributed plurality of document engine services.

[0035] The micro front-end engine 121 is provided on the client 12 and is used to isolate UI components of different document engine services through a sandbox, interact with the document engine service through the micro service coordinator based on the service identifier, and render the UI components in the sandbox based on the service identifier. The micro front-end engine 121 is specifically used to:

[0036] The UI components of different document engine services are isolated through the sandbox, a service request carrying a service identifier is initiated to the document engine service on the server side, a service response carrying a service identifier is received from the document engine service, and the UI component of the corresponding document engine service in the sandbox is rendered according to the service identifier in the service response.

[0037] The above technical solution of the embodiment of the present invention is described in detail below in conjunction with the accompanying drawings.

[0038] In the embodiment of the present invention, based on the low-code platform capability of the document engine as the basic unit of microservices, such as Figure 2 As shown in the figure, the entire microservice architecture includes: service coordinator, search engine, and multiple document engine services; among them:

[0039] For each deployed document engine service, set a globally unique service identifier, which is used to distinguish the REST addresses of different document engines;

[0040] The microservice coordinator actively discovers the document engine service in the entire architecture through pre-defined service routes. The service route discovers the document engine service through the microservice coordinator and generates a dynamic proxy to take over the REST service address exposed by the document engine. When the front-end UI initiates a request to the server, it correctly identifies and distributes the request to achieve the coexistence of multiple document engines.

[0041] The search engine service collects business data from all document engine services, reduces the data dimension and uses it as a global data index. The index contains the service identifier.

[0042] like Figure 3As shown, the system UI end (the above-mentioned client) customizes a sandbox, which is managed by the micro-frontend engine. The sandbox isolates the UI components of different document engines. It should be noted that when multiple document engines are deployed, their versions and the degree of secondary development will be different, so the front-end UI must have the ability to distinguish. The sandbox perfectly solves this problem. For example, for the DynamicCard component in the document engine Service1, the name in the sandbox will be adjusted to Server1DynamicCard to distinguish it from DynamicCard in Service2.

[0043] The micro-frontend engine has the ability to initiate requests to the document engine service on the server side and respond to the server-side data; when the micro-frontend engine initiates a request to the document engine service on the server side, it carries the service identifier; when the micro-frontend engine receives the response from the server, it renders the UI component of the corresponding document engine service in the sandbox according to the service identifier of the response;

[0044] like Figure 4 As shown in the figure, the system server customizes the service route to identify the user request. The service route forwards the request to the corresponding document engine service according to the service identifier in the UI request. After receiving the service request from the client, the document engine service executes the final business logic program according to the logic configuration of the implementer in the system; in the response data, the service identifier is added and returned to the UI.

[0045] Compared with the prior art, the technical solution proposed in the embodiment of the present invention greatly improves the flexibility, scalability and stability when using a low-code platform to implement a large-scale enterprise software system, and specifically has the following beneficial effects:

[0046] 1. Each business line can freely conduct secondary development on the low-code platform without affecting the functions of other business lines;

[0047] 2. Upgrading or maintaining system modules of each business line does not require the overall architecture to be shut down;

[0048] 3. The data of each business line is completely physically isolated, which improves data storage capacity, reduces operation and maintenance complexity, and improves system security;

[0049] 4. Each business line can be implemented as needed, split and run independently, or merged into a unified microservice architecture.

[0050] Method Embodiment

[0051] According to an embodiment of the present invention, a method for implementing a microservice platform based on a document engine is provided, which is used for the above-mentioned microservice platform. Figure 5 is a flow chart of a method for implementing a microservice platform based on a document engine according to an embodiment of the present invention. Figure 5As shown, the microservice platform implementation method based on the document engine according to an embodiment of the present invention specifically includes:

[0052] Step S501, through the microservice coordinator based on the customized service routing, actively discovers the document engine service in the microservice platform according to the service identifier, and forwards the interaction information between the client's micro front-end engine and the document engine service based on the service identifier; specifically includes:

[0053] Through the microservice coordinator based on the customized service routing, the document engine service in the microservice platform is actively discovered according to the service identifier, the service request carrying the service identifier sent by the client is obtained, and the service request is forwarded to the corresponding document engine service according to the service identifier, and the service response fed back by the document engine service is accepted, and the service identifier is added to the service response and sent to the client, wherein the service identifier is used to distinguish the REST addresses of different document engine services.

[0054] Step S502, collecting business data in all document engine services through a search engine service, reducing the dimension of the business data and using it as a global data index, wherein the data index includes the service identifier;

[0055] Step S503, receiving the service request through the document engine service, performing corresponding processing based on the service request, and sending the processing result to the microservice coordinator in the service response; wherein the document engine service is: a distributed plurality of document engine services.

[0056] Step S504, using the sandbox to isolate UI components of different document engine services through the micro front-end engine, interacting with the document engine service through the micro service coordinator based on the service identifier, and rendering the UI components in the sandbox based on the service identifier. Specifically including:

[0057] The micro-frontend engine uses a sandbox to isolate the UI components of different document engine services, initiates a service request carrying a service identifier to the document engine service on the server side, receives a service response carrying a service identifier fed back by the document engine service, and renders the UI component of the corresponding document engine service in the sandbox according to the service identifier in the service response.

[0058] The embodiment of the present invention is a method embodiment corresponding to the above-mentioned device embodiment. The specific operation of each step can be understood by referring to the description of the device embodiment, which will not be repeated here.

[0059] Device Example 2

[0060] An embodiment of the present invention provides an electronic device, such as Figure 6As shown, it includes: a memory 60, a processor 62, and a computer program stored in the memory 60 and executable on the processor 62. When the computer program is executed by the processor 62, the steps described in the method embodiment are implemented.

[0061] Device Example 3

[0062] An embodiment of the present invention provides a computer-readable storage medium, on which a program for implementing information transmission is stored. When the program is executed by the processor 62, the steps described in the method embodiment are implemented.

[0063] The computer-readable storage medium in this embodiment includes, but is not limited to, ROM, RAM, magnetic disk or optical disk, etc.

[0064] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A microservice platform based on a document engine, characterized in that: It includes server and client, where: A microservice coordinator, which is arranged at the server end and connected to the search engine service, is used to actively discover the document engine service in the microservice platform according to the service identifier through a customized service route, and forward the interaction information between the micro front-end engine of the client and the document engine service based on the service identifier; A search engine service, arranged at the server end and connected to the document engine service, for collecting business data from all document engine services, reducing the dimension of the business data and using it as a global data index, wherein the data index includes the service identifier; The document engine service is arranged at the server end and connected to the microservice coordinator, and is used to receive the service request, perform corresponding processing based on the service request, and send the processing result to the microservice coordinator in the service response; The micro front-end engine is arranged on the client and is used to isolate the UI components of different document engine services through a sandbox, interact with the document engine service through the micro service coordinator based on the service identifier, and render the UI components in the sandbox based on the service identifier.

2. The microservice platform according to claim 1, characterized in that: The document engine service is: distributed multiple document engine services.

3. The microservice platform according to claim 1, characterized in that: The microservices coordinator is specifically used for: Through customized service routing, the document engine service in the microservice platform is actively discovered based on the service identifier, the service request carrying the service identifier sent by the client is obtained, and the service request is forwarded to the corresponding document engine service according to the service identifier, and the service response fed back by the document engine service is accepted, and the service identifier is added to the service response and sent to the client, wherein the service identifier is used to distinguish the REST addresses of different document engine services.

4. The microservice platform according to claim 1, characterized in that: The micro front-end engine is specifically used for: The UI components of different document engine services are isolated through the sandbox, a service request carrying a service identifier is initiated to the document engine service on the server side, a service response carrying a service identifier is received from the document engine service, and the UI component of the corresponding document engine service in the sandbox is rendered according to the service identifier in the service response.

5. A method for implementing a microservice platform based on a document engine, characterized in that: For use in a microservice platform according to any one of claims 1 to 4, the method specifically comprises: Based on the customized service routing, the microservice coordinator actively discovers the document engine service in the microservice platform according to the service identifier, and forwards the interaction information between the client's micro front-end engine and the document engine service based on the service identifier; Collecting business data from all document engine services through a search engine service, reducing the dimension of the business data and using it as a global data index, wherein the data index includes the service identifier; Receive the service request through the document engine service, perform corresponding processing based on the service request, and send the processing result to the microservice coordinator in the service response; The micro-frontend engine uses a sandbox to isolate UI components of different document engine services, interacts with the document engine service through the microservice coordinator based on the service identifier, and renders the UI components in the sandbox based on the service identifier.

6. The method according to claim 5, characterized in that The document engine service is: distributed multiple document engine services.

7. The method according to claim 5, characterized in that The microservice coordinator actively discovers the document engine service in the microservice platform based on the service identifier based on the customized service routing, and forwards the interaction information between the client's micro-frontend engine and the document engine service based on the service identifier, specifically including: Through the microservice coordinator based on the customized service routing, the document engine service in the microservice platform is actively discovered according to the service identifier, the service request carrying the service identifier sent by the client is obtained, and the service request is forwarded to the corresponding document engine service according to the service identifier, and the service response fed back by the document engine service is accepted, and the service identifier is added to the service response and sent to the client, wherein the service identifier is used to distinguish the REST addresses of different document engine services.

8. The method according to claim 5, characterized in that Using a sandbox to isolate UI components of different document engine services through a micro front-end engine, interacting with the document engine service through the micro service coordinator based on the service identifier, and rendering the UI components in the sandbox based on the service identifier specifically includes: The micro-frontend engine uses a sandbox to isolate the UI components of different document engine services, initiates a service request carrying a service identifier to the document engine service on the server side, receives a service response carrying a service identifier fed back by the document engine service, and renders the UI component of the corresponding document engine service in the sandbox according to the service identifier in the service response.

9. An electronic device, characterized in that include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the method for implementing a microservice platform based on a document engine as described in any one of claims 5 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores an implementation program for information transmission, and when the program is executed by the processor, the steps of the implementation method of the microservice platform based on the document engine as described in any one of claims 5 to 8 are implemented.

Images