A software development platform based on microservice inheritance

Abstract

The present invention discloses a software development platform based on microservice inheritance, and relates to the field of computer technology. The platform includes an identity authentication center, a data modeling module, and an application construction module; the data modeling module is used to abstract business entities into a number of digital models with unified data specifications; the application construction module constructs business applications by secondary development of the digital models; the identity authentication center is used to manage user identities and permissions; the permissions are specifically permissions for users to access resources and perform operations through business applications. This application constructs a digital model through a data modeling module, a low-level model provides general attributes and behaviors, and a high-level model realizes business specialization through inheritance and extension, thereby improving the flexibility of data modeling to support efficient data management and rapid business expansion and technology iteration, thereby responding to the rich business needs of users.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a software development platform based on microservice inheritance. Background Art

[0002] In existing software development practices, with the increase in business complexity and the rapid changes in market demand, enterprises or organizations are faced with the challenge of how to respond quickly to business changes and efficiently develop and maintain software applications. Microservice architecture has gradually become one of the mainstream architectural patterns to meet this challenge due to its highly decoupled and modular characteristics. However, existing microservice architectures also have some common challenges. Monolithic applications in the development process usually go through a process of business entity expansion from simple to complex. Existing microservice applications are insufficient in scalability and flexibility in data modeling, and the customization cost is high. In addition, the construction and maintenance of microservice applications requires processing dozens or even hundreds of services, and each service may have its own data model and business logic, resulting in complex management. Summary of the invention

[0003] In order to solve the problems existing in the above background technology, the present invention adopts the following technical solutions:

[0004] A software development platform based on microservice inheritance, including identity authentication center, data modeling module and application building module;

[0005] The data modeling module is used to abstract business entities into a number of digital models with unified data specifications; the digital models include the first to Nth level digital models, N is an integer greater than 1; the i-th level digital model inherits the (i-1)th level digital model, i is an integer greater than 1 and less than or equal to N; wherein the first level digital model is a root parent class model; the second level digital model is an agent digital model, which is used to support instantiation of objects; the third level digital model is a work item digital model, which is used to support version management; the fourth level digital model is a business item digital model, which is used to support version management; the fifth level digital model is a structured business item digital model, which is used to support main object management;

[0006] The application construction module constructs business applications by secondary development of the digital model;

[0007] The identity authentication center is used to manage user identities and permissions; the permissions specifically refer to the user's permissions to access resources and perform operations through business applications; the identity authentication center includes an identity management module, an authentication management module, a permission management module, a monitoring and early warning module, and a compliance audit module; the identity management module is used to centrally manage user identity information, and user identity information includes user ID, organizational structure, position and role information.

[0008] As a preferred solution of the present application, the fields of the digital model include basic data, attribute data, message data, layout data and relationship data.

[0009] As a preferred solution of the present application, the identity management module stores user identity information through a user information storage model, and performs life cycle management on the user identity information through an identity synchronization mechanism.

[0010] As a preferred solution of the present application, the identity synchronization mechanism specifically establishes a synchronization mechanism between a user information source and a user information storage model, and synchronizes the user identity information from the user information source to the user information storage model in real time.

[0011] As a preferred solution of the present application, the permission management module includes a permission model and a permission service middleware. The permission model is used to configure the mapping relationship between user ID, organizational structure, position and / or role information and permissions, and the permission service middleware is used to obtain the permissions stored in the permission model based on user identity information.

[0012] As a preferred solution of the present application, the business application includes a front-end application model and a back-end service model; the application construction module constructs the front-end application model through the secondary development digital model, and the process of constructing the front-end application model is specifically as follows: the developer obtains the digital model through a visualization tool, generates a customized component by configuring the fields of the digital model; registers the front-end application model and configures the user rights of the front-end application model through the identity authentication center; binds the customized component to the front-end application model;

[0013] The application construction module constructs a backend service model through secondary development of the digital model. The construction of the backend service model is specifically as follows: the developer evaluates the digital model based on business needs; if the digital model can meet the requirements, the digital model is directly called; if the digital model cannot meet the requirements, the relevant methods in the digital model are rewritten or a new custom message is created.

[0014] As a preferred solution of the present application, the role information includes system administrator, security officer and security auditor; the permissions mapped to the system administrator include executing system installation, system configuration, operating environment configuration, system model setting, coding management, process configuration, creating new users and modifying user basic information; the permissions mapped to the security officer include viewing and configuring the mapping relationship between user identity information and permissions, browsing ordinary users and auditing administrator operation logs; the permissions mapped to the security auditor include audit tracking analysis and supervision and inspection of the audit logs of system administrators, security officers and security auditors.

[0015] As a preferred solution of this application, the business applications include product data management applications, logistics control applications, production management applications and quality traceability applications; among them, the product data management application is used to manage product data throughout its life cycle; the logistics control application is used for supply chain management, procurement management, warehouse management and distribution management; the production management application is used to manage production planning, production control, production quality and production equipment; the quality traceability application is used to trace product quality data.

[0016] As a preferred solution of the present application, it also includes an operation and maintenance monitoring module; the operation and maintenance monitoring module monitors the business application and generates an operation and maintenance report by non-invasively collecting operation and maintenance data.

[0017] As the preferred solution of this application, the operation and maintenance report is used to display application KPI, slow SQL analysis and intelligent alarm, provide key indicator views of SQL statements, and provide JVM memory and thread indicator data; the application KPI includes business throughput, error rate, latency and load status.

[0018] Compared with the prior art, the present invention has the following beneficial effects:

[0019] The software development platform of this application can provide complete support from the bottom-level data model structure to the top-level business entity implementation. Digital models are built through data modeling modules. Each level of digital models is a logical extension based on the combination of microservice architecture and data modeling. Low-level models provide common attributes and behaviors, and high-level models achieve business specialization by inheriting and extending low-level models, which improves the flexibility of data modeling to support efficient data management and rapid business expansion and technology changes, thereby responding to users' rich business needs.

[0020] This application provides a secure, flexible and maintainable access control mechanism through an identity authentication center. For business applications built through secondary development of digital models, administrators only need to centrally configure one item of user identity information, without having to configure the permissions of each user one by one, thereby simplifying the configuration process of permission management. In addition, this embodiment can make the system more flexible to expand by decoupling user identity information and permissions. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the embodiments of the present invention 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 of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0022] Figure 1A schematic diagram of the structure of a software development platform based on microservice inheritance provided by an embodiment of the present invention.

[0023] Figure 2 A schematic diagram of the hierarchical relationship of a digital model provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The technical solution of the present invention will be clearly and completely described below in conjunction with the embodiments. Obviously, the described embodiments are only part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention. It should be noted that relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0025] See also Figure 1 The present invention provides a software development platform based on microservice inheritance, including an identity authentication center, a data modeling module and an application building module. The data modeling module is used to abstract business entities into a number of digital models with unified data specifications.

[0026] The application construction module constructs business applications by secondary developing the digital model.

[0027] The identity authentication center is used to manage user identities and permissions; the permissions specifically refer to the permissions of users to access resources and perform operations through business applications.

[0028] The digital model includes the first to Nth level digital models, and the i-th level digital model inherits the (i-1)th level digital model; wherein N is an integer greater than 1, and i is an integer greater than 1 and less than or equal to N. The first-level digital model is the root parent model of the foundation, the second-level digital model inherits the first-level digital model, and so on. It can be seen that the complex data relationships in business entities can be gradually refined from general abstract concepts (usually at a low level) to specific business models (at a high level). The process of business entity modeling allows the use of existing models to quickly develop new business entities by combining, dynamically rendering, and dynamically inheriting them, thereby improving the flexibility and efficiency of development.

[0029] See also Figure 2 , further, N is greater than or equal to 5; wherein the second to fifth level digital models are as follows:

[0030] The second-level digital model is the proxy digital model, which is used to support instantiated objects. The proxy digital model acts as a proxy for the business instance, reflecting the state and behavior of the entity in the system. This application provides ORM (object-relational mapping) support to facilitate the persistence of model instances in the database.

[0031] The third-level digital model is the work item digital model, which is used to support version management. Among them, version (Iteration) is used in agile and iterative development processes. It is a collection of all work in the iteration cycle and a stage in the project plan. In a version, the development team usually implements an evolving software version and makes related improvements. After each version, developers usually reflect on this iteration cycle, reviewing the successful aspects and aspects that need improvement. Then design the next version of the iteration. Version management is performed for work items (such as tasks, events, work orders, etc.). Work items usually need to track change history for audit and backtracking.

[0032] The fourth-level digital model is the business item digital model, which is used to support version management. Versions are used to represent different software codes. When developers update the code, they mark the version number and record specific changes. Versions are used to mark major nodes in the software life cycle, such as when the software has made significant improvements, overcome major bugs, or support new features. Usually, multiple versions must be completed before a higher-level software version is released. Tracking and managing various versions of business items that evolve over a long period of time (such as contracts, policies, design documents, etc.) can maintain the integrity and consistency of the versions.

[0033] The fifth level digital model is the structured business item digital model, which is used to support the management of primary objects. For different components or modules contained in the same business item, the structured business item digital model provides structured management and identifies a primary object as the contact point. The primary object can be a clear digital model, whose instance can connect all related structured data. By defining the primary objects of the digital model, it helps to improve the maintainability, queryability and consistency of data, and enhance the management capabilities of complex business items in an enterprise or system.

[0034] Through the above scheme, the software development platform of this application can achieve perfect support from the bottom-level data model structure to the top-level business entity implementation. Each level of digital model is a logical extension based on the combination of microservice architecture and data modeling. The low-level model provides common attributes and behaviors, and the high-level model achieves business specialization through inheritance and extension, which improves the flexibility of data modeling to support efficient data management and rapid business expansion and technology changes, thereby responding to the rich business needs of users.

[0035] As a preferred embodiment, the fields of the digital model include basic data, attribute data, message data, layout data and relationship data. Among them, the basic data includes the general data of the digital model such as the class name, display name, class constants of the digital model. The attribute data is the basic field in the digital model, which represents the characteristics or properties of the digital model. The message data is the external interface of the digital model, which represents the communication method between the instantiated objects of the digital model. The instantiated objects of the digital model perform specific operations or trigger specific behaviors through message data. The layout data is the arrangement and presentation method of the objects on the interface or page. The layout data determines the position, size, alignment, etc. of each object. In the graphical interface design or web page design, the layout data can determine the aesthetics and usability of the user interface. The relationship data includes the unique ID and connection relationship of the related model. The relationship data can represent the one-to-one relationship, one-to-many relationship and many-to-many relationship between the digital models, and specifically represents the relationship such as dependency and inheritance.

[0036] As a preferred embodiment, the identity authentication center includes an identity management module, an authentication management module, a permission management module, a monitoring and early warning module and a compliance audit module.

[0037] The identity management module is used to centrally manage user identity information, which includes user ID, organizational structure, position and role information, and other related attributes. In one embodiment, the identity management module stores user identity information through a centralized user information storage model, and performs life cycle management of user identity information through an identity synchronization mechanism. The user information storage model transmits user identity information through a directory access protocol. Directory access protocols include protocols such as LDAP and RESTful API.

[0038] Furthermore, the identity synchronization mechanism specifically establishes a synchronization mechanism between the user information source and the user information storage model, and synchronizes the user identity information from the user information source to the user information storage model in real time through API calls, message queues, asynchronous tasks, etc., to ensure the data consistency and accuracy of the user identity information.

[0039] The authentication management module provides single sign-on service through the authentication interface protocol. The authentication interface protocol includes OAuth, SAML, CAS and OIDC protocols. Single Sign-On (SSO) is an authentication and authorization technology that uses the same authentication mechanism in multiple application systems. Users only need to log in once to access all mutually trusted application systems. Using the single sign-on service, users only need to authenticate in one application system, and they can be automatically authenticated in all other application systems, avoiding the problem of repeated authentication in multiple systems and improving user efficiency and experience.

[0040] The permission management module includes a permission model and a permission service middleware. The permission model is used to configure the mapping relationship between user identity information and permissions, and the permission service middleware is used to obtain permissions stored in the permission model according to the user identity information. When a user attempts to access a specific resource, the permission service middleware determines whether the user has the permission to perform the operation based on the user's user identity information. In the judgment process, the judgment follows the principle of least privilege, and only grants the user the minimum privilege required to perform necessary operations to improve the security and controllability of the system.

[0041] Based on the user identity information related content of the aforementioned embodiment, the mapping relationship between the configuration of user identity information and permissions is specifically the mapping relationship between the configuration of user ID, organizational structure, position and / or role information and permissions. Accordingly, the administrator only needs to centrally configure a certain item of user identity information, without having to configure the permissions of each user one by one, thereby simplifying the configuration process of permission management. In addition, this embodiment can make the system more flexible to expand by decoupling user identity information and permissions. If new identity information or permissions need to be added, only the corresponding mapping relationship needs to be added to the permission model without affecting the existing identity information and permissions.

[0042] The monitoring and early warning module is used to monitor the user access mode in real time and prevent abnormal access from being authorized to ensure the user's login security in real time. Specifically, the monitoring and early warning module analyzes login events in real time through event monitoring and analysis tools. Abnormal access includes abnormal time, location, device, and blacklist access.

[0043] The compliance audit module is used to record sensitive operation data such as abnormal accounts, user logins, access, authentication, etc. through audit logs, and provides tools for searching, monitoring and reporting audit logs to facilitate security reviews and compliance audits.

[0044] The above five modules constitute the identity authentication center under the microservice architecture, which aims to provide a secure, flexible and maintainable access control mechanism. By implementing these technical solutions, the microservice platform can ensure the security of the system and meet the ever-changing business needs and compliance standards.

[0045] In one embodiment, the role information of the user identity information includes system administrator, security officer and security auditor. The permissions mapped by the system administrator include executing system installation, system configuration, operating environment configuration, system model setting, coding management, process configuration, creating new users and modifying basic user information, but cannot modify the mapping relationship between user identity information and permissions. The permissions mapped by the security officer include viewing and configuring the mapping relationship between user identity information and permissions, browsing ordinary users and auditing administrator operation logs. The permissions mapped by the security auditor include audit tracking analysis and supervision and inspection of the audit logs of system administrators, security officers and security auditors. In this embodiment, the three different role information assume different responsibilities and permissions, and restrict each other, making the allocation and management of permissions more strict and controllable. This helps to improve the efficiency of system management, reduce abuse of permissions and risks, and ensure the security and compliance of user identity information and system resources.

[0046] In one embodiment, the business application includes a front-end application model and a back-end service model. The application construction module constructs the front-end application model through secondary development of the digital model. The process of constructing the front-end application model is as follows: the developer obtains the digital model through a visualization tool, generates a customized component by configuring the fields of the digital model; registers the front-end application model and configures the user permissions of the front-end application model through the identity authentication center to ensure that the correct user can access and operate the application and its functions; and binds the customized component to the front-end application model.

[0047] The application construction module constructs the backend service model through secondary development of the digital model. The specific steps of constructing the backend service model are as follows: the developer evaluates the digital model based on business needs; if the digital model meets the requirements, the digital model is directly called; if the digital model does not meet the requirements, the relevant methods in the digital model are rewritten or new custom messages are created.

[0048] In one embodiment, the business applications include product data management applications, logistics control applications, production management applications, and quality traceability applications. Among them, the product data management application is a system for managing product-related information, specifically for managing product design, manufacturing, testing and other full life cycle data; the logistics control application is a system for managing the company's logistics system, used for supply chain management, procurement management, warehouse management and distribution management; the production management application is a system for managing the company's production process, used to manage production planning, production control, production quality and production equipment; the quality traceability application is used to trace product quality data throughout the entire process of product production and sales. This embodiment uses low-code, visually developed and deployed business applications to make enterprise management more flexible and efficient, and can be adjusted and optimized at any time.

[0049] As a preferred embodiment, the software development platform of the present application also includes an operation and maintenance monitoring module; the operation and maintenance monitoring module monitors the business application and generates an operation and maintenance report by non-invasively collecting operation and maintenance data. Through non-invasive data collection, the operation and maintenance monitoring module will not interfere with the operation of the business application to achieve real-time monitoring. The operation and maintenance report is generated based on the operation and maintenance data, and is used to display application KPIs (including business throughput, error rate, latency and load status), slow SQL analysis, intelligent alarm and other data, provide key indicator views such as the number of SQL statement calls, response time, number of errors, and provide JVM memory and thread indicator data. The operation and maintenance monitoring module of the present application provides a comprehensive performance monitoring and analysis tool for business applications, strengthens the capabilities of the operation and maintenance team, and thus achieves more efficient fault diagnosis, problem solving and system optimization.

[0050] In the several embodiments provided in the present application, it should be understood that the disclosed units can be implemented in other ways. For example, the unit embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another unit, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of modules, which can be electrical, mechanical or other forms.

[0051] The units described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment.

[0052] In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules.

[0053] If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

Claims

1. A software development platform based on microservice inheritance, characterized by: Including identity authentication center, data modeling module and application building module, The data modeling module is used to abstract business entities into a number of digital models with unified data specifications, and the digital models include first to fifth level digital models; wherein, The first-level digital model is the root parent model; The second-level digital model is the proxy digital model, which is used to support instantiated objects. The proxy digital model acts as a proxy for business instances, reflecting the state and behavior of entities in the system. It provides ORM support to facilitate the persistence of model instances in the database. The third-level digital model is the work item digital model, which is used to support version management. Versions are used in agile and iterative development processes. They are a collection of all work in an iteration cycle and a stage in a project plan. Work items include tasks, events, and work orders. Work items track change history for auditing and backtracking. The fourth-level digital model is the business item digital model, which is used to support version management. Versions are used to represent different software codes. When developers update the code, they mark the version number and record specific changes. The version marks the main nodes in the software life cycle. Version management is used to track and manage various versions of business items that evolve over a long period of time, including contracts, policies, and design documents. The fifth level digital model is the structured business item digital model, which is used to support the management of main objects. For different components or modules contained in the same business item, the structured business item digital model provides structured management and identifies a main object as the contact point. The main object is a clear digital model, and its instance can connect all related structured data. The application construction module constructs business applications by secondary development of the digital model; The identity authentication center is used to manage user identities and permissions. The permissions specifically refer to the user's permissions to access resources and perform operations through business applications. The identity authentication center includes an identity management module, an authentication management module, a permission management module, a monitoring and early warning module, and a compliance audit module. The identity management module is used to centrally manage user identity information. User identity information includes user ID, organizational structure, position and role information.

2. The software development platform based on microservice inheritance according to claim 1, characterized in that: The fields of the digital model include basic data, attribute data, message data, layout data and relationship data.

3. The software development platform based on microservice inheritance according to claim 1, characterized in that: The identity management module stores user identity information through a user information storage model, and performs life cycle management on the user identity information through an identity synchronization mechanism.

4. The software development platform based on microservice inheritance according to claim 3, characterized in that: The identity synchronization mechanism specifically establishes a synchronization mechanism between a user information source and a user information storage model, and synchronizes user identity information from the user information source to the user information storage model in real time.

5. The software development platform based on microservice inheritance according to claim 1, characterized in that: The permission management module includes a permission model and a permission service middleware. The permission model is used to configure the mapping relationship between user ID, organizational structure, position and / or role information and permissions. The permission service middleware is used to obtain the permissions stored in the permission model according to user identity information.

6. The software development platform based on microservice inheritance according to claim 1, characterized in that: The business application includes a front-end application model and a back-end service model; the application construction module constructs the front-end application model through the secondary development digital model, and the process of constructing the front-end application model is specifically as follows: The developer obtains the digital model through a visualization tool, generates a custom component by configuring the fields of the digital model; registers the front-end application model and configures the user rights of the front-end application model through the identity authentication center, and binds the custom component to the front-end application model; The application construction module constructs a backend service model through secondary development of the digital model, and the construction of the backend service model is specifically: Developers evaluate the digital model based on business requirements; if the digital model meets the requirements, the digital model is called directly; if the digital model does not meet the requirements, the relevant methods in the digital model are rewritten or new custom messages are created.

7. The software development platform based on microservice inheritance according to claim 1, characterized in that: The role information includes system administrator, security officer and security auditor. The permissions mapped to the system administrator include executing system installation, system configuration, operating environment configuration, system model setting, coding management, process configuration, creating new users and modifying user basic information; the permissions mapped to the security officer include viewing and configuring the mapping relationship between user identity information and permissions, browsing ordinary users and auditing administrator operation logs; the permissions mapped to the security auditor include audit tracking analysis and supervision and inspection of the audit logs of system administrators, security officers and security auditors.

8. The software development platform based on microservice inheritance according to claim 1, characterized in that: The business applications include product data management applications, logistics control applications, production management applications and quality traceability applications; among them, product data management applications are used to manage product data throughout its life cycle; logistics control applications are used for supply chain management, procurement management, warehouse management and distribution management; production management applications are used to manage production plans, production control, production quality and production equipment; quality traceability applications are used to trace product quality data.

9. The software development platform based on microservice inheritance according to claim 1, characterized in that: It also includes an operation and maintenance monitoring module, which monitors the business application and generates an operation and maintenance report by non-invasively collecting operation and maintenance data.

10. The software development platform based on microservice inheritance according to claim 9, characterized in that: The operation and maintenance report is used to display application KPIs, slow SQL analysis and intelligent alarms, provide key indicator views of SQL statements, and provide JVM memory and thread indicator data; the application KPIs include business throughput, error rate, latency and load status.

Images