A low-code development system for a data model combining microservice architecture

Abstract

This invention discloses a low-code data model development system based on a microservice architecture, comprising a business model library module and a low-code development platform module. The business model library module provides functions for editing and reusing business data models, generating a data model system that is editable and reusable. The low-code development platform module is used to develop business software based on drag-and-drop configuration of the business data model and / or the data model system, generating editable front-end and back-end code. This system significantly improves data model reusability, greatly reduces development cycles and labor costs, meets the rapid iteration needs of business systems, and generates a high-performance, highly available system.

Description

Technical Field

[0001] This invention belongs to the field of microservices and low-code development technology, and in particular relates to a low-code development system for a data model that combines a microservices architecture. Background Technology

[0002] Business system development teams commonly face challenges such as rapidly changing requirements, short deployment times, and slow progress in streamlining business processes for new software. Currently available low-code platforms suffer from the following shortcomings, making it difficult to support rapid deployment of business software: Traditional low-code development platforms exhibit high coupling between software components when reusing functional modules from older software. Modifications to older software do not automatically affect the same business modules in the new software, resulting in unclear boundaries between software components and hindering multi-team collaboration. Furthermore, traditional low-code platforms generate business models from physical tables; if foreign keys are not used to represent relationships between tables, the platform cannot recognize them, requiring manual joins after generation. Summary of the Invention

[0003] Purpose of the invention: The technical problem to be solved by the present invention is to provide a low-code development system for a data model that combines a microservice architecture, addressing the shortcomings of the existing technology.

[0004] To address the aforementioned technical issues, this invention discloses a low-code development system for data models that incorporates a microservice architecture. The system includes a business model library module and a low-code development platform module. The business model library module provides functions for editing and reusing business data models, generating a data model system that can be edited and reused. The low-code development platform module is used to develop business software based on drag-and-drop configuration of the data model and / or the data model system, generating editable front-end and back-end code. This allows for rapid development, even by non-R&D personnel.

[0005] Furthermore, the business model library module includes a business data model library and a data model system.

[0006] The business data model library is used to extract common, rarely changed fields from business data models to form a data model library; this greatly improves model reusability and enables rapid iteration of software functions.

[0007] The aforementioned data model system is used to represent business data that cannot be expressed by a single business data model, and where there are fixed master-slave table relationships between the business data models. This data model system can more completely represent the business and is more suitable for the rapid development of new systems.

[0008] Furthermore, the low-code development platform module performs the following steps:

[0009] Drag-and-drop development allows users to create forms and workflows by dragging and dropping business data models and / or data model systems, thus completing software configuration. This process does not involve specific code and can be completed by non-development personnel. It greatly improves model reusability and enables rapid iteration of software functions.

[0010] Generate multi-platform code, turning the compiled software into editable code, and simultaneously generating Java backend, web frontend, and app source code. The generated Java backend, web frontend, and app source code can be used for breakpoint debugging.

[0011] The generated Java backend code can be deployed independently of a low-code development platform and can be integrated into microservices as a service provider or consumer, reusing software functionality as services to form business systems. This reduces code coupling and improves performance and disaster recovery capabilities.

[0012] Furthermore, it also includes a service discovery and configuration center module, which is used for service registration and discovery, as well as distributed configuration.

[0013] Furthermore, the service discovery and configuration center module performs the following steps:

[0014] Service discovery uses Nacos to complete service registration and subscription. Service providers and consumers register their addresses with the registry center when they start up.

[0015] Service health monitoring uses a heartbeat mechanism to perform health checks on service providers, promptly removing unhealthy service instances and avoiding sending requests to unhealthy service instances.

[0016] The dynamic configuration service centrally manages all service configurations, providing centralized and dynamic management of application and service configurations across all environments. Configuration changes take effect without requiring a service restart.

[0017] Furthermore, it also includes a service gateway module, which provides authentication, load balancing, circuit breaking and degradation to provide security protection for the system.

[0018] Furthermore, the service gateway module performs the following steps:

[0019] Authentication: The business system uses a gateway to uniformly authenticate and log in to external requests, and service providers can directly obtain the information and permissions of the currently logged-in user.

[0020] Load balancing involves the gateway forwarding requests to the service provider while using load balancing algorithms and rate limiting measures to prevent excessive traffic from causing system crashes. Configuring and using load balancing allows for seamless switching during system upgrades, so users do not experience any service interruption.

[0021] Circuit breaking and degradation are used to switch to other predefined emergency measures when a service provider is unhealthy, thus avoiding expanding the scope of downtime.

[0022] Furthermore, it also includes an attribute-based access control module, which is used to configure data access rules and perform data access control.

[0023] Furthermore, the attribute-based access control module performs the following steps:

[0024] Identify the functionalities involving fine-grained control of data permissions and add data permissions to the pages;

[0025] Configure custom data permission rules;

[0026] Assign data permission rules to roles or departments.

[0027] Beneficial effects: Compared with the prior art, the significant advantages of this invention are: This invention reuses software in the form of microservices, defines standardized service call interfaces, shields service consumers from internal modifications by service providers, and each service only needs to focus on its own module, reducing communication costs.

[0028] 1. Complete and systematic business models: Unlike single-table models, for more mature business systems, the relationships between basic models are relatively fixed. Commonly used business models and the relationships between them can be systematically saved to support the rapid construction of new business systems.

[0029] 2. The generated software supports multiple deployment methods: it supports deployment on low-code platforms, it supports being generated as a standalone web application or app, and it supports running as a service provider or consumer in a microservice.

[0030] 3. Combining low-code platforms and microservice architecture: On the one hand, non-R&D personnel can complete the software construction; on the other hand, the constructed products have high performance and high availability, and software functions can be reused in the form of services. Standardized service call interfaces are defined, which shields service consumers from internal modifications by service providers. Each service only needs to focus on its own module, reducing communication costs between teams.

[0031] 4. Fine-grained attribute-based access control: This approach utilizes the attributes of relevant entities (such as subjects, objects, and environments) as the basis for authorization to study how to implement access control. In attribute-based access control, access decisions are based on the attributes possessed by the requester and the resource. Requesters and resources are identified through characteristics, offering sufficient flexibility and scalability, which is crucial in large-scale distributed environments. Attached Figure Description

[0032] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments, and the advantages of the present invention in the above and / or other aspects will become clearer.

[0033] Figure 1 This is a flowchart of the rapid deployment of newly developed software in Example 1.

[0034] Figure 2 This is the user interface of the software built from the business model in Example 1.

[0035] Figure 3 This is a list of models that have been constructed in Example 1.

[0036] Figure 4 This is the interface for viewing and testing the generated software in Example 1.

[0037] Figure 5 This is the first page in Example 2 where data permissions are added to the page.

[0038] Figure 6 This is the second operation page for adding data permissions to the page in Example 2.

[0039] Figure 7 This is the operation page for configuring custom data permission rules in Example 2.

[0040] Figure 8 This is the operation page for assigning data permission rules to roles in Example 2.

[0041] Figure 9 This is a schematic diagram of the structure of a low-code development system for a data model that combines a microservice architecture, as provided in an embodiment of this application. Detailed Implementation

[0042] The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0043] This application provides a low-code development system for data models that combines a microservice architecture. It can provide a high-performance, highly available development platform that supports the accumulation and rapid iteration of business data models for business system development teams.

[0044] This application discloses a low-code development system for a data model that incorporates a microservices architecture, such as... Figure 9 As shown, it includes a business model library module and a low-code development platform module. The business model library module is used to provide business data model editing and reuse functions, and generate a data model system that can be edited and reused. The low-code development platform module is used to develop business software based on the business data model and / or the data model system through drag-and-drop configuration, and generate editable front-end and back-end code.

[0045] The business model library module includes a business data model library and a data model system.

[0046] The business data model library is used to extract common, rarely changing fields from business data models to form a data model library; the business data model can be a data table structure, the relationship between data tables, the calculation formula of data table fields, etc.

[0047] The data model system is used to form a data model system composed of multiple business data models with fixed relationships, where certain business data cannot be expressed by a single business data model and there is a fixed master-slave table relationship between the business data models.

[0048] The low-code development platform module performs the following steps:

[0049] Drag and drop development: drag and drop business data models and / or data model systems to form forms and workflows, and complete software configuration.

[0050] Generate multi-platform code, turning the compiled software into editable code, and simultaneously generating Java backend, web frontend, and app source code. The generated Java backend, web frontend, and app source code can be used for breakpoint debugging.

[0051] Microservices are generated, and the generated Java backend code can be deployed independently of the low-code development platform. It can be integrated into the microservice as a service provider or consumer, reusing software functions in the form of services to form a business system.

[0052] This embodiment also includes a service discovery and configuration center module, which is used for service registration and discovery, as well as distributed configuration. The service discovery and configuration center module performs the following steps:

[0053] Service discovery uses Nacos to complete service registration and subscription. Service providers and consumers register their addresses with the registry center when they start up.

[0054] Service health monitoring uses a heartbeat mechanism to perform health checks on service providers, promptly removing unhealthy service instances and avoiding sending requests to unhealthy service instances.

[0055] The dynamic configuration service centrally manages all service configurations, providing centralized and dynamic management of application and service configurations across all environments. Configuration changes take effect without requiring a service restart.

[0056] This embodiment also includes a service gateway module, which provides authentication, load balancing, circuit breaking, and degradation to provide security protection for the system. The service gateway module performs the following steps:

[0057] Authentication: The business system uses a gateway to uniformly authenticate and log in to external requests, and service providers can directly obtain the information and permissions of the currently logged-in user.

[0058] Load balancing involves the gateway forwarding requests to the service provider while simultaneously using load balancing algorithms and rate limiting measures to prevent excessive traffic from causing system crashes. This is configured to use load balancing.

[0059] Circuit breaking and degradation are implemented when a service provider becomes unhealthy, switching to other predefined emergency measures.

[0060] This embodiment also includes an attribute-based access control module, which is used to configure data access rules and perform data access control. The attribute-based access control module performs the following steps:

[0061] Identify the functionalities involving fine-grained control of data permissions and add data permissions to the pages;

[0062] Configure custom data permission rules;

[0063] Assign data permission rules to roles or departments.

[0064] Example 1:

[0065] like Figure 1 As shown, during the rapid deployment of newly developed software:

[0066] (1) Search for business data models that meet the requirements in the business model library according to the business type and requirements.

[0067] (2) Search the data model system to which the business data model belongs. If a data model system similar to the requirements of the newly developed software exists, it can be directly dragged and dropped for reuse, such as... Figure 2 As shown.

[0068] (3) Non-R&D personnel, based on the data model system, use a low-code development platform to add detailed fields, configure the display interface, and configure business processes. Click on the function test, such as... Figure 3 As shown, you can view and test the generated software page, such as... Figure 4 As shown.

[0069] (4) Generate Java backend, web frontend, and Android app source code, and complete packaging and testing.

[0070] (5) Newly developed software is generated and added to the microservice system as a service provider or service consumer, and service testing and release are completed, such as... Figure 4 As shown.

[0071] Example 2:

[0072] Implementing fine-grained attribute-based access control:

[0073] (1) Identify the functionalities involving fine-grained control of data permissions, and add data permissions to the relevant pages, such as... Figure 5 and Figure 6 As shown.

[0074] (2) Configure custom data permission rules, supporting selection from preset rules. Complex rules support SQL-level customization, such as restricting viewing only data created by this department, for example... Figure 7 As shown.

[0075] (3) Assign data permission rules to roles or departments, such as Figure 8 As shown, without configuration, global data is visible by default. The more data permission rules configured, the less data can be viewed. Data permissions based on "rule-role / department-user" are supported. More granular data permission control is implemented based on the RBAC (Role-Based Access Control) concept, supporting list data permissions. Row data is controlled through data permissions, allowing different people to have different data viewing rules. For example: sales staff can only see their own data; sales managers can see the data of all their subordinate sales staff; finance personnel can only see data with amounts greater than 5000, etc.

[0076] In its specific implementation, this application provides a computer storage medium and a corresponding data processing unit. The computer storage medium is capable of storing a computer program, which, when executed by the data processing unit, can run the invention's content and some or all of the steps in its various embodiments regarding a low-code development system for a data model combining a microservice architecture. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0077] Those skilled in the art will clearly understand that the technical solutions in the embodiments of the present invention can be implemented using computer programs and their corresponding general-purpose hardware platforms. Based on this understanding, the technical solutions in the embodiments of the present invention, or the parts that contribute to the prior art, can be embodied in the form of computer programs, i.e., software products. These computer program software products can be stored in a storage medium and include several instructions to cause a device containing a data processing unit (which may be a personal computer, server, microcontroller, MUU, or network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments of the present invention.

[0078] This invention provides a low-code development system for a data model combined with a microservice architecture. Many methods and approaches exist for implementing this technical solution; the above descriptions are merely specific embodiments of this invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this invention, and these improvements and modifications should also be considered within the scope of protection of this invention. All components not explicitly stated in this embodiment can be implemented using existing technologies.

Claims

1. A low-code development system for a data model combining a microservice architecture, characterized in that: It includes a business model library module and a low-code development platform module. The business model library module is used to provide business data model editing and business data model reuse functions to generate a data model system. The data model system can be edited and reused. The low-code development platform module is used to develop business software based on a drag-and-drop configuration of a business data model and / or a data model system, generating editable front-end and back-end code. The business model library module includes a business data model library and a data model system. The business data model library is used to extract common, rarely changed fields from business data models to form a data model library; The data model system is used to form a data model system when certain business data cannot be expressed by a single business data model and there is a fixed master-slave table relationship between the business data models. The low-code development platform module performs the following steps: Drag and drop development: drag and drop business data models and / or data model systems to form forms and workflows, and complete software configuration. Generate multi-platform code, turning the compiled software into editable code, and simultaneously generating Java backend, web frontend, and app source code. The generated Java backend, web frontend, and app source code can be used for breakpoint debugging. Microservices are generated, and the generated Java backend code can be deployed independently of the low-code development platform. It can be integrated into the microservice as a service provider or consumer, reusing software functions in the form of services to form a business system.

2. The low-code development system for a data model combining a microservice architecture as described in claim 1, characterized in that: It also includes a service discovery and configuration center module, which is used for service registration and discovery, as well as distributed configuration.

3. A low-code development system for a data model combining a microservice architecture as described in claim 2, characterized in that: The service discovery and configuration center module performs the following steps: Service discovery uses Nacos to complete service registration and subscription. Service providers and consumers register their addresses with the registry center when they start up. Service health monitoring uses a heartbeat mechanism to perform health checks on service providers, promptly removing unhealthy service instances and avoiding sending requests to unhealthy service instances. The dynamic configuration service centrally manages all service configurations, providing centralized and dynamic management of application and service configurations across all environments. Configuration changes take effect without requiring a service restart.

4. A low-code development system for a data model combining a microservice architecture as described in claim 3, characterized in that: It also includes a service gateway module, which provides authentication, load balancing, circuit breaking and degradation to provide security protection for the system.

5. A low-code development system for a data model combining a microservice architecture as described in claim 4, characterized in that: The service gateway module performs the following steps: Authentication: The business system uses a gateway to uniformly authenticate and log in to external requests, and service providers can directly obtain the information and permissions of the currently logged-in user. Load balancing involves the gateway forwarding requests to the service provider while simultaneously using load balancing algorithms and rate limiting measures to prevent excessive traffic from causing system crashes; configure and use load balancing. Circuit breaking and degradation are implemented when a service provider becomes unhealthy, switching to other predefined emergency measures.

6. A low-code development system for a data model combining a microservice architecture as described in claim 5, characterized in that: It also includes an attribute-based access control module, which is used to configure data access rules and perform data access control.

7. A low-code development system for a data model combining a microservice architecture as described in claim 6, characterized in that: The attribute-based access control module performs the following steps: Identify the functionalities involving fine-grained control of data permissions and add data permissions to the pages; Configure custom data permission rules; Assign data permission rules to roles or departments.

Images