CN111488145A - Micro-service code generation system and method based on service domain data model base - Google Patents

Abstract

The invention discloses a microservice code generation system and method based on a business domain data model library, and relates to the technical field of microservices; the system includes a module for establishing a business domain data model library, a module for establishing a MOM object file, and a module for establishing a business domain data model library , which is used to establish the business domain data model library and the MOM object file module, which is used to refer to the business model entity object in the business domain data model library and convert it into a MOM object file; the method is to refer to the business model in the business domain data model library. The model entity object is converted into a MOM object file; it improves the development efficiency of microservices by establishing a business domain data model library module and a MOM object file module.

Description

A microservice code generation system and method based on business domain data model library

technical field

The invention relates to the technical field of microservices, in particular to a microservice code generation system and method based on a business domain data model library.

Background technique

In recent years, microservice architecture technology has developed rapidly, and more and more enterprises have adopted microservice architecture technology. Compared with the traditional monolithic application architecture, the microservice architecture emphasizes flexible delivery. Microservices are small and autonomous services that can work together and have the advantages of independent deployment, loose coupling, technical isolation, and easy expansion. Some microservice architecture applications are split and transformed from the monolithic application architecture, and some microservices are newly developed based on actual business applications. Micro Object Model Micro Object Model, hereinafter referred to as MOM.

In the practice process of microservice architecture application, the following problems will be faced: In the early stage of microservice development, software design and developers need to have a lot of close communication with the business experts of the enterprise, which requires a lot of communication costs to carry out the microservice business domain. Analysis is used to determine the business granularity of each microservice. The granularity of microservice splitting is controlled by developers and designers. In the development of a large number of enterprise microservices, businesses in the same field will meet in different microservice design and development. Faced with the problem of inconsistent splitting standards, in the construction of microservices in enterprises, it will lead to repeated development and uneven quality of the same type of business in the construction of microservices. When using traditional methods to develop microservices, when there are a large number of microservices, there are problems such as long delivery cycles.

Patent applications related to the prior art:

(1) A method for monolithic application microservices: the name of the patent application is a method for monolithic application microservices, the application number is 2018100240484, the patent application is based on the developed monolithic application, according to all requests The starting point and end point of the call analyzes the business related modules in the application, and needs to be corrected manually to determine the granularity of the microservice. The technical solution of this application is to analyze the existing single application system, and is not applicable to the granularity analysis of newly developed microservices, and the technical solution does not involve the development of microservices.

(2) A method and device for generating micro-services: The patent application name is a method and device for generating micro-services, and the application number is 2017103920714. , to generate the microservice framework code. The technical solution of the application does not introduce content related to the microservice business, and does not generate code related to the business logic of the microservice.

Existing technical problems and thinking: how to solve the technical problem of low efficiency of microservice development.

SUMMARY OF THE INVENTION

The technical problem to be solved by the present invention is to provide a microservice code generation system and method based on a business domain data model library, which improves the development of microservices by establishing a business domain data model library module and a MOM object file module, etc. efficiency.

In order to solve the above-mentioned technical problems, the technical solution adopted by the present invention is: a microservice code generation system based on a business domain data model library includes establishing a business domain data model library module and a MOM object file module, and establishing a business domain data model library. The module is used to establish the business domain data model library; the MOM object file module is established to refer to the business model entity object in the business domain data model library and convert it into a MOM object file.

A further technical solution is: it also includes generating a microservice code module, and generating a microservice code module for inputting the converted MOM object file into a source code generator, and in the source code generator, successively by parsing the MOM object file and selecting a page style , Bind page attributes, match the pre-generated technical framework and output source code, and output the generated micro-application or micro-service source code structure information; establish a business domain data model library module, which is also used for business model entities in the business domain data model library The data of the object is stored in the database, and the business model entity object is stored in the database with the structured information of the data table. Structured data tables for authorization management, entity reference records, entity text attributes, and entity history records.

Further technical scheme is: described establishing MOM object file module comprises opening model tool module, introducing model object module, converting MOM object module, revising model module and storing MOM object, opening model tool module, for opening model in development tool Tool; import model object module, which is used to import business model entity objects through API interface; convert MOM object module, which is used for business model entity converter to convert imported business model entity objects into MOM object files; It is required to modify and improve the entity object information of the business model in the model tool; store the MOM object module, which is used to save the information of the MOM object and form the MOM object file; establish the MOM object file module, which is also used to store the information of the MOM object file in XML format.

A further technical solution is: open the model tool module, which is also used to open the local development tool, and configure the business domain data model library information in the attribute configuration, including the model library address, port and user information; The local development tool menu wizard, open the business domain data model library, in the query conditions, enter the query conditions of the basic personnel information, select the basic personnel information entity object in the query result, and click the import button to import the personnel basic information entity object into In the model tool; the MOM object module is converted, and when the import button is clicked, the basic information entity object information of the personnel can be obtained through the interface API service of the business domain data model library, which can be read or Maintained MOM object file; Modification model module, also used for MOM object file modification and conversion, the model tool loads the MOM object file, displays the imported business model entity object information, and adjusts the model attribute information according to business needs, including adding business attributes. Or modify the data type; after adjusting the business model entity object information, synchronize the adjusted business model entity object to the business domain data model library by calling the business domain data model library interface API service; store the MOM object module, and also The information used in the MOM object file is stored in XML structure. During the process of introducing the business model entity object, it is converted into an XML structure for storage through the business model entity converter; the XML structure is divided into two parts, the first part is the model tool page. The required information includes version information, basic information and style information. The second part is the introduced business model entity object information, which includes the business domain to which the business model entity object belongs and the business model entity object attribute information; MOM object file information and The information of business model entity objects is a one-to-many relationship, and according to business needs, multiple business model entity objects are introduced at one time or business model entity object information is introduced multiple times.

A further technical solution is: the generating microservice code module includes parsing MOM object file module, selecting page style module, binding page attribute module, matching pre-generated technical framework module and output source code module, parsing MOM object file module, using To input the MOM object file information into the source code generator, the source code generator obtains the MOM object file information and parses the MOM object file according to the XML tag definition; selects the page style module, which is used to select the page display style according to business needs; binds the page attribute module, It is used to bind page attributes with business model entity object attribute information; it matches the pre-generated technical framework module, which is used to match the technical framework according to the project technical framework requirements; the output source code module is used to generate business application source code information.

A further technical solution is: parsing the MOM object file module is also used to select the MOM object file in the development tool project directory, right-click the mouse to select the conversion source code in the menu, and enter the service name and the service directory structure in the pop-up interface. information; the source code generator will obtain the MOM object file information, parse the MOM object file according to the XML tag definition and put it into the cache; select the page style module, which is also used to generate the wizard according to the source code, and select the business display interface style; bind the page attribute module, It is also used for binding with the business model entity object attributes extracted by parsing the MOM object file after the interface display style is confirmed; matching the pre-generated technical framework module, and also used for binding the business model entity object attributes according to the project technical framework. Requirements, matching the source code generation structure; outputting the source code module is also used to output the source code structure information through the source code generator.

A microservice code generation method based on a business domain data model library is to refer to a business model entity object in the business domain data model library and convert it into a MOM object file.

A further technical solution is: specifically comprising the steps of S1 establishing a business domain data model library and S2 establishing a MOM object file, S1 establishing a business domain data model library, and the data of the business model entity objects in the business domain data model library is stored in the database, Business model entity objects are stored in the database with structured information in data tables, including business categories, business sub-categories, entity basic information, entity structured attributes, entity relationship information, entity version information, entity authorization management, entity reference records, entity Structured data table of text attributes and entity history; S2 establishes a MOM object file, refers to the business model entity object in the business domain data model library, and converts it into a MOM object file; the information of the MOM object file is stored in XML format.

Further technical scheme is: the step that described S2 establishes MOM object file specifically comprises the step of S201 opening model tool, S202 introducing model object, S203 converting MOM object, S204 revising model and S205 storing the step of MOM object, S201 opening model tool, in developing. Open the model tool in the tool; open the local development tool, and configure the business domain data model library information in the property configuration, including the model library address, port and user information; S202 introduces the model object, and introduces the business model entity object through the API interface; through the local development Tools menu wizard, open the business domain data model library, in the query conditions, enter the query conditions of the basic personnel information, select the basic personnel information entity object in the query result, and click the import button to import the basic personnel information entity object into the model tool middle; S203 converts the MOM object, and the business model entity converter converts the imported business model entity object into a MOM object file; when the import button is clicked, the basic information entity object information of the personnel is obtained through the interface API service of the business domain data model library. The business model entity converter converts the MOM object file that the model tool can read or maintain; S204 corrects the model, and corrects and improves the business model entity object information in the model tool according to business requirements; after the MOM object file is corrected and converted, the model tool loads the MOM object file to display the imported business model entity object information, adjust model attribute information according to business needs, including operations to add business attributes or modify data types; after adjusting the business model entity object information, call the business domain data model library interface API service , synchronize the adjusted business model entity object into the business domain data model library; S205 store the MOM object, save the information of the MOM object and form a MOM object file; the information of the MOM object file is stored in an XML structure, and when the business model entity object is introduced In the process, the business model entity converter is used to convert it into an XML structure for storage; the XML structure is divided into two parts, the first part is the information required by the model tool page, including version information, basic information and style information, and the second part is The introduced business model entity object information includes information about the business domain to which the business model entity object belongs and the attribute information of the business model entity object; the information of the MOM object file and the information of the business model entity object are in a one-to-many relationship. A business model entity object or the business model entity object information is introduced multiple times.

A further technical solution is: it also includes step S3 to generate the microservice code, input the converted MOM object file into the source code generator, and successively analyze the MOM object file, select the page style, bind the page attributes, and match the source code generator in the source code generator. Pre-generated technical framework and output source code, outputting the generated micro-application or micro-service source code structure information; the step of generating micro-service code in S3 specifically includes S301 parsing the MOM object file, S302 selecting page style, S303 binding page attributes, S304 matches the pre-generated technical framework and S305 outputs the source code, S301 parses the MOM object file, inputs the MOM object file information into the source code generator, and the source code generator obtains the MOM object file information and parses the MOM object file according to the XML tag definition; In the tool project directory, select the MOM object file, right-click the mouse and select Convert Source Code in the menu, and enter the service name and service directory structure information in the pop-up interface; the source code generator will obtain the MOM object file information and parse it according to the XML tag definition The MOM object file is put into the cache; S302 selects the page style, and selects the page display style according to the business needs; according to the source code generation wizard, selects the business display interface style; S303 binds the page attributes, and binds the page attributes to the attribute information of the business model entity object After the interface display style is confirmed, it is bound to the business model entity object attributes extracted by parsing the MOM object file; S304 matches the pre-generated technical framework, and matches the technical framework according to the project technical framework requirements; after the business model entity object attribute binding is completed , and match the source code generation architecture according to the project technical architecture requirements; S305 outputs the source code to generate the business application source code information; outputs the source code structure information through the source code generator.

The beneficial effects produced by the above technical solutions are:

A microservice code generation system based on a business domain data model library, which improves the development efficiency of microservices by establishing a business domain data model library module and a MOM object file module.

A microservice code generation method based on a business domain data model library, which improves the development efficiency of microservices by referencing business model entity objects in the business domain data model library and converting them into MOM object files.

For details, please refer to the description in the detailed description.

Description of drawings

Fig. 1 is the principle block diagram of establishing MOM object file module in the embodiment of the present invention 1;

Fig. 2 is a schematic block diagram of generating a microservice code module in Embodiment 1 of the present invention;

3 is a flowchart of Embodiment 2 of the present invention;

Fig. 4 is the principle block diagram of the business domain data model library Web system;

Fig. 5 is the principle block diagram of the business domain data model;

Figure 6 is a screenshot of the data table structure properties;

Fig. 7 is the screen shot of the data table in the database;

Figure 8 is a screenshot of configuring service address, port and user information;

Figure 9 is a screen shot of selecting a business model entity object;

Figure 10 is a screenshot of the MOM object file information;

Figure 11 is a screen shot of adjusting business model entity information;

Fig. 12 is the format diagram of MOM object file;

Figure 13 is a detailed format diagram of the MOM object file;

Fig. 14 is the screen shot of generating source code to MOM object file input link based on MOM object file;

Figure 15 is a screenshot of selecting an interface style;

Figure 16 is a screenshot of binding data;

Figure 17 is a screenshot of the generated microservice source code structure.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the application, its application, or uses. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In the following description, many specific details are set forth to facilitate a full understanding of the present application, but the present application can also be implemented in other ways different from those described herein, and those skilled in the art can do so without departing from the connotation of the present application Similar promotion, therefore, the present application is not limited by the specific embodiments disclosed below.

Example 1:

As shown in Figures 1 and 2, the present invention discloses a microservice code generation system based on a business domain data model library, including establishing a business domain data model library module, establishing a MOM object file module and generating a microservice code module. The establishment of MOM object file module includes opening model tool module, introducing model object module, converting MOM object module, revising model module and storing MOM object, and described generating microservice code module includes parsing MOM object file module, selecting page style module, binding Define the page attribute module, match the pre-generated technical framework module and output the source code module.

The establishment of a business domain data model library module is used to establish a business domain data model library. The data of the business model entity objects in the business domain data model library are stored in the database, and the business model entity objects are stored in the database with data table structured information. There are mainly business categories, business sub-categories, entity basic information, entity structured attributes, entity relationship information, entity version information, entity authorization management, entity reference records, entity text attributes and entity history records.

As shown in Figure 1, a MOM object file module is established to refer to the business model entity object in the business domain data model library, and convert it into a MOM object file, and the information of the MOM object file is stored in XML format. The building MOM object file module includes opening the model tool module, importing the model object module, converting the MOM object module, revising the model module and storing the MOM object.

Open the model tool module, which is used to open the local development tool and configure the business domain data model library information in the property configuration, including the model library address, port and user information.

Introduce the model object module, which is used to introduce business model entity objects through the API interface; open the business domain data model library through the local development tool menu wizard, enter the query conditions for the basic information of personnel in the query conditions, and select the personnel basic information in the query results. Information entity object, by clicking the import button, import the personnel basic information entity object into the model tool.

Convert MOM object module, used for business model entity converter to convert the imported business model entity object into MOM object file; when clicking the import button, through the interface API service of the business domain data model library, obtain the basic information of personnel information entity object information, through The Business Model Entity Converter converts the MOM object file that the Model Tool can read or maintain.

The revision model module is used to revise and improve the entity object information of the business model in the model tool according to business requirements; after the revision and conversion of the MOM object file is completed, the model tool loads the MOM object file, displays the imported business model entity object information, and adjusts it according to business needs Model attribute information, including operations to add business attributes or modify data types; after adjusting the business model entity object information, synchronize the adjusted business model entity objects to the business domain data model library by calling the business domain data model library interface API service middle.

The MOM object storage module is used to save the information of the MOM object and form the MOM object file; the information of the MOM object file is stored in the XML structure. During the process of introducing the business model entity object, it is converted into the XML structure through the business model entity converter. storage. The XML structure is divided into two parts. The first part is the information required by the model tool page, which includes version information, basic information and style information; the second part is the imported business model entity object information, which includes the business domain to which the business model entity object belongs and Information about business model entity object properties. The information of the MOM object file and the information of the business model entity objects are in a one-to-many relationship. According to business needs, multiple business model entity objects are introduced at one time or business model entity object information is introduced multiple times.

As shown in Figure 2, a microservice code module is generated, which is used to input the converted MOM object file into the source code generator. Generated technical framework and output source code, and output the source code structure information of the generated micro-application or micro-service. The generating microservice code module includes a MOM object file parsing module, a page style selection module, a page attribute binding module, a matching pre-generated technical framework module and an output source code module.

The module for parsing MOM object files is used to input the MOM object file information into the source code generator. The source code generator obtains the MOM object file information and parses the MOM object file according to the XML tag definition; in the development tool project directory, select the MOM object file, right-click Select the conversion source code in the menu with the mouse, and enter the service name and service directory structure information in the pop-up interface; the source code generator will obtain the MOM object file information, parse the MOM object file according to the XML tag definition, and put it into the cache.

Select the page style module, which is used to select the page display style according to business needs; according to the source code generation wizard, select the business display interface style.

The page attribute binding module is used to bind the page attributes with the business model entity object attribute information; after the interface display style is confirmed, it is bound with the business model entity object attributes extracted by parsing the MOM object file.

Matching the pre-generated technical framework module is used to match the technical framework according to the project technical framework requirements; after the business model entity object attribute binding is completed, the source code generation framework is matched according to the project technical framework requirements.

The output source code module is used to generate business application source code information; the source code structure information is output through the source code generator.

Example 2:

As shown in FIG. 3 , the present invention discloses a microservice code generation method based on a business domain data model library, comprising the following steps:

S1 establishes the business domain data model library

The data of the business model entity objects in the business domain data model library is stored in the database, and the business model entity objects are stored in the database with data table structured information, mainly including business categories, business sub-categories, entity basic information, and entity structured information. Structured data tables for attributes, entity relationship information, entity version information, entity authorization management, entity reference records, entity text attributes, and entity history records.

S2 creates a MOM object file

Refer to the business model entity object in the business domain data model library and convert it into a MOM object file.

The information of the MOM object file is stored in XML format.

S201 Open Model Tool

Open the Model tool in Developer Tools. Open the local development tool and configure the business domain data model library information in the property configuration, including the model library address, port and user information.

S202 Introduce model objects

Introduce business model entity objects through API interface. Open the business domain data model library through the local development tool menu wizard, enter the query conditions for the basic information of personnel in the query conditions, select the basic personnel information entity object in the query result, and click the import button to import the basic personnel information entity object. into the model tool.

S203 Convert MOM objects

The business model entity converter converts the incoming business model entity objects into MOM object files. When the import button is clicked, the basic information entity object information of personnel is obtained through the interface API service of the business domain data model library, and the MOM object file that can be read or maintained by the model tool is converted through the business model entity converter.

S204 Revised Model

Modify and improve the entity object information of the business model in the model tool according to the business requirements. After the MOM object file is corrected and converted, the model tool loads the MOM object file, displays the imported business model entity object information, and adjusts the model attribute information according to business needs, including adding business attributes or modifying data types.

After adjusting the business model entity object information, synchronize the adjusted business model entity object to the business domain data model library by calling the business domain data model library interface API service.

S205 stores MOM objects

The information of the MOM object is saved and a MOM object file is formed. The information of MOM object file is stored in XML structure. During the process of introducing business model entity object, it is converted into XML structure for storage through business model entity converter. The XML structure is divided into two parts. The first part is the information required by the model tool page, which includes version information, basic information and style information; the second part is the imported business model entity object information, which includes the business domain to which the business model entity object belongs and Information about business model entity object properties. The information of the MOM object file and the information of the business model entity objects are in a one-to-many relationship. According to business needs, multiple business model entity objects are introduced at one time or business model entity object information is introduced multiple times.

S3 generates microservice code

Input the converted MOM object file into the source code generator, and in the source code generator successively analyze the MOM object file, select the page style, bind the page attributes, match the pre-generated technical framework and output the source code, and output the generated micro-application Or microservice source code structure information. Specifically include the following steps:

S301 Parse MOM object file

Input the MOM object file information into the source code generator, and the source code generator obtains the MOM object file information and parses the MOM object file according to the XML tag definition. In the development tool project directory, select the MOM object file, right-click the mouse and select Convert Source in the menu, and enter the service name and service directory structure information in the pop-up interface. The source code generator will obtain the MOM object file information, parse the MOM object file according to the XML tag definition, and put it into the cache.

S302 Select page style

Choose the page display style according to your business needs. According to the source code generation wizard, select the business display interface style, such as tree structure, multi-tab structure or list form structure, and click Next.

S303 Binding page properties

Bind page properties to business model entity object property information. After the interface display style is confirmed, it is bound to the business model entity object properties extracted by parsing the MOM object file. For example, the user name corresponds to user_name. After the binding is completed, click Next.

S304 Matching pre-generated technical frameworks

Match the technical architecture according to the project technical architecture requirements. After the business model entity object attribute binding is completed, the source code generation architecture is matched according to the project technical architecture requirements, such as the framework of microservices, microapplications or monolithic structures.

S305 output source code

Generate business application source code information. Finally, the source code structure information is output through the source code generator.

Purpose of this application:

This application reduces the communication cost between designers or developers and business experts through the standard or reused business domain data model library, and provides an automatic code generation method based on the microservice object model MOM, which improves the development efficiency of microservices .

1. Convert the adopted business domain data model library into an identifiable MOM object file: refer to the model information in the business domain data model library, and convert it into a MOM object file read and maintained by the model tool. R&D personnel need to further sort out the model attributes, compare the MOM object file attributes identified by the model tool, and formulate the MOM object file information that the model tool can read and maintain.

2. Generate the required microservice source code with architectural characteristics according to the MOM object file: the MOM object file converted from the basic business model entity object is input into the source code generator, and the MOM object file information is parsed in the source code generator to match the framework. Templates that generate source code for the architecture the developer needs.

Technical contributions of this application:

The present application provides a microservice code generation system and method based on a business domain data model library, which improves the efficiency of microservice design and microservice development.

First, the business domain model library is a business domain model library built to meet the needs of the enterprise's own business development by combining general domain knowledge, enterprise business domain knowledge and existing application systems for analysis and sorting. This application mainly refers to the model object in the business domain model library, and converts it into a MOM object, which is easy to modify the model in the model tool, which solves the problem of accurate correspondence between business and business domain models, and reduces business experts and business model. The communication cost of designers has been improved, and the communication efficiency has been improved.

Second, the MOM object information of the present application is stored in an XML format through a model converter during the process of introducing a business model object, which facilitates the entry, expansion and maintenance of the business model. MOM object information and business model object information have a one-to-many relationship. Multiple business models can be introduced at one time or business model information can be introduced multiple times according to business needs, which improves the flexibility of code generation for business scenarios.

Third, the present application flexibly accesses the converted MOM object information to the source code generator for rapid development of business applications. In the source code generator, parse the MOM file, select the page style, bind the page attributes, match the pre-generated frameworks such as microservices, and finally output the generated microapplication or microservice code structure, and now provide a complete data access layer, business Logic layer, control layer, and presentation layer code templates are available for developers to choose. Developers can choose to generate only the back-end service code, including the code of the data access layer and business logic layer, or generate the complete front-end display code and back-end service code according to the usage scenario of the microservice. The front-end display code includes the display layer, Control layer code. The flexible code generation method improves the development quality and reduces the development cost.

The inventive concept of this application:

Software technology is an industry with rapid development and changes. There are relatively many software development methods. The existing development methods include page construction method, menu wizard method, model wizard method and direct coding. In the previous development methods, the menu-guided method was mostly used for development. Although the source code structure that the developer wanted could be generated, it could not promote the business standardization and the precise correspondence between the business and the business domain model. The inventor found that by referencing the model in the business domain data model library, the MOM object required by the model tool is converted, and then the MOM object is input into the source code generator to generate the source code structure required by the developer. The MOM object is maintained in the model tool, and the model in the business domain data model library can also be revised. Not only the business becomes more and more standard, it also further solves the problem of accurate correspondence between business and business domain models.

After the application has been run confidentially for a period of time, the benefits of feedback from on-site technicians are:

1. Develop microservices based on the business domain data model library, which simplifies the analysis and design phase of the application of the microservice architecture. By using a highly reusable business domain data model library, microservice developers and designers are freed from heavy business analysis work, and only need to focus on the development of microservices.

2. The business domain data model library is an important resource that can be updated and accumulated for enterprises. It solves the problem of accurate correspondence between business and business domain data models. In the development and construction of microservices, it will promote the business domain data model. The library is further developed towards the standardization.

3. Provide visual business domain data model import tool and data model design tool, which improves the design efficiency of MOM model.

4. Provide a rich code framework template library to support the rapid code generation of the microservice architecture, which greatly improves the efficiency of microservice development.

illustrate:

1. Business domain data model library

The business domain data model library in this application takes the business model entity object-driven development as the guiding ideology, mainly combines general domain knowledge, enterprise business domain knowledge and existing application systems for analysis and precipitation, and forms a business built for the needs of the enterprise's own business development. Domain data model library.

As shown in Figure 4 to Figure 7, the model entity object data in the business domain data model library is stored in the database, such as: MySql database, business personnel or technical personnel in the business domain data model system functions, add, modify, delete Maintain entity data of the business domain data model repository. Business model entity objects are stored in the database with structured information in data tables, which mainly include business categories, business sub-categories, entity basic information, entity structured attributes, entity relationship information, entity version information, entity authorization management, entity reference records, Structured data tables such as entity text attributes and entity history records, and basic entity information is the business model entity object.

2. Convert MOM object files based on business model entity objects

This application refers to the business model entity object in the business domain data model library, and converts it into a MOM object file, which is easy to modify the business model entity object in the model tool, and solves the exact correspondence between the business and the business model entity object. The problem is that the MOM object file information of the present application is stored in the local workspace in XML format, which realizes the platform independence and portability of the present application.

1) As shown in Figure 8, first, open a local development tool, such as Eclipse, and configure the business domain data model library information in the property configuration, such as: model library address, port, user information, etc.

2) As shown in Figure 9, secondly, through the local development tool menu wizard, open the business domain data model library, in the query conditions, enter the query conditions, such as: personnel basic information, select the personnel basic information entity object in the query result, By clicking the import button, the entity object of the basic information of the person is imported into the model tool.

3) As shown in Figure 10, when the import button is clicked, the basic information entity object information of personnel is obtained through the interface API service of the business domain data model library, and the MOM object that can be read or maintained by the model tool is converted through the business model entity converter. document.

4) As shown in Figure 11, after the MOM object file conversion is completed, the model tool will load the MOM object file and display the imported business model entity object information. Designers or technicians can adjust the model attribute information according to business needs, such as adding business operations such as properties or modifying data types.

5) After adjusting the business model entity object information, synchronize the adjusted business model entity object to the business domain data model library by calling the business domain data model library interface API service.

6) Save the MOM object file information.

3. MOM object file storage format

As shown in Figure 12 and Figure 13, the entire MOM object file information is stored in an XML structure. During the process of introducing the business model entity object, it is converted into an XML structure for storage through the business model entity converter. The XML structure is divided into two parts. The first part is the information required by the model tool page, such as version information, basic information, style information, etc., and the second part is the imported business model entity object information, such as the business domain to which the business model entity object belongs. , business model entity object attribute information, etc. The MOM object file information and the business model entity object information have a one-to-many relationship. Multiple business model entity objects can be introduced at one time or business model entity object information can be introduced multiple times according to business needs. The present application provides a maintenance system for the business domain data model library, which can facilitate the entry, expansion and maintenance of business model entity object information.

4. Generate microservice code based on MOM object file

As shown in Figure 14, after the business model entity object is adjusted according to business needs, the MOM object file is transferred to the source code generator through the right-click menu for rapid development of business applications. Input the converted MOM object file into the source code generator, in the source code generator successively by parsing the MOM object file, selecting the page style, binding the page attributes, and matching the pre-generated technical framework, such as: microservice, and finally outputting the generated The source code structure information of the micro-application or micro-service is as follows:

1) First, in the development tool project directory, select the MOM object file, right-click the mouse and select Convert Source Code in the menu, and enter the service name, service directory structure and other information in the pop-up interface.

2) As shown in Figure 15, secondly, the source code generator will obtain the MOM object file information, parse the MOM object file according to the XML tag definition, put it into the cache, and select the business display interface style according to the source code generation wizard, such as: tree structure, Create a multi-tab structure or a list form structure, click Next.

3) As shown in Figure 16, after the interface display style is confirmed, it is bound to the business model entity object attributes extracted by parsing the MOM object file, for example: the user name corresponds to user_name, click Next after the binding is completed.

4) After the business model entity object attribute binding is completed, according to the project technical architecture requirements, match the source code generation architecture, such as: microservices, microapplications, monolithic structures and other frameworks.

5) As shown in Figure 17, the source code structure information is finally output through the source code generator.

By using the MOM object file converted by the business model entity converter to generate the application code of the microservice architecture, the development efficiency of the microservice is improved. The code generation engine in this application is based on the template method, and the templates provided are: micro-service, micro-application, and monolithic structure. Now, a complete data access layer, business logic layer, control layer, and presentation layer code templates are provided for development. Personnel selection. Developers can choose to generate only the back-end service code, including the code of the data access layer and business logic layer, or generate complete front-end display code and back-end service code according to the usage scenario of the microservice. The front-end display code includes the display layer, control layer code.

Claims (10)

1. A micro service code generation system based on a service domain data model base is characterized in that: the method comprises the steps of establishing a service domain data model base module and an MOM object file establishing module, wherein the service domain data model base module is used for establishing a service domain data model base; and establishing an MOM object file module for referencing the service model entity object in the service domain data model base and converting the service model entity object into an MOM object file.

2. The micro service code generation system based on the service domain data model base as claimed in claim 1, wherein: the system also comprises a micro-service code generation module which is used for inputting the converted MOM object file into a source code generator, and outputting the generated micro-application or micro-service source code structure information in the source code generator by analyzing the MOM object file, selecting the page style, binding the page attribute, matching the pre-generated technical framework and outputting the source code;

and establishing a service domain data model base module, and storing the data of the service model entity object in the service domain data model base in the database, wherein the service model entity object is stored in the database by using data table structured information, and the structured data table comprises service major categories, service detailed categories, entity basic information, entity structured attributes, entity relation information, entity version information, entity authorization management, entity reference records, entity text attributes and entity history records.

3. The micro service code generation system based on the service domain data model base as claimed in claim 1, wherein: the MOM object file establishing module comprises an opening model tool module, a model object introducing module, a MOM object converting module, a model correcting module and a MOM object storing module,

an open model tool module for opening a model tool in a development tool;

the model object introducing module is used for introducing a business model entity object through an API (application programming interface);

the MOM object conversion module is used for converting the introduced service model entity object into an MOM object file by the service model entity converter;

the model modification module is used for modifying and perfecting the entity object information of the business model in the model tool according to the business requirements;

the MOM object storage module is used for storing the information of the MOM object and forming an MOM object file;

and establishing an MOM object file module, and storing the information of the MOM object file in an XM L format.

4. The micro service code generation system based on the service domain data model base as claimed in claim 3, wherein: the model tool opening module is also used for opening a local development tool and configuring the information of a business domain data model base in attribute configuration, wherein the information comprises a model base address, a port and user information;

the model object introducing module is also used for opening a business domain data model library through a local development tool menu guide, inputting the query condition of the basic information of personnel in the query condition, selecting the basic information entity object of the personnel in the query result, and introducing the basic information entity object of the personnel into the model tool by clicking an introducing button;

the MOM object conversion module is also used for acquiring the basic information entity object information of personnel through an interface API (application programming interface) service of a service domain data model library when an introduction button is clicked, and converting an MOM object file which can be read or maintained by a model conversion tool of a service model entity converter;

the model modification module is also used for loading the MOM object file by the model tool after the MOM object file is modified and converted, displaying the introduced entity object information of the business model, and adjusting the attribute information of the model according to the business requirement, wherein the operation comprises the operation of adding business attributes or modifying data types; after the business model entity object information is adjusted, synchronizing the adjusted business model entity object into a business domain data model library by calling a business domain data model library interface API service;

the system comprises a storage MOM object module and a service model entity converter, wherein the storage MOM object module is also used for storing the information of an MOM object file in an XM L structure, the information is converted into an XM L structure for storage through the service model entity converter in the process of introducing a service model entity object, the XM L structure is divided into two parts, the first part is the information required by a model tool page and comprises version information, basic information and style information, the second part is introduced service model entity object information and comprises a service domain to which the service model entity object belongs and information of service model entity object attributes, the information of the MOM object file and the information of the service model entity object are in a one-to-many relationship, and a plurality of service model entity objects are introduced at one time or the service model entity object information is introduced for a plurality of times according to service.

5. The micro service code generation system based on the service domain data model base as claimed in claim 2, wherein: the micro-service code generation module comprises an MOM object file analysis module, a page style selection module, a page property binding module, a technical frame matching pre-generation module and an output source code module,

the MOM object file analyzing module is used for inputting MOM object file information into the source code generator, and the source code generator acquires the MOM object file information and analyzes the MOM object file according to XM L label definition;

the page style selecting module is used for selecting a page display style according to business needs;

the binding page attribute module is used for binding the page attribute with the service model entity object attribute information;

the matching pre-generated technical framework module is used for matching the technical framework according to the requirements of the project technical framework;

and the output source code module is used for generating service application source code information.

6. The system of claim 5, wherein the parsing MOM object file module is further configured to select an MOM object file in a development tool project directory, select a conversion source code in a menu by right-clicking a mouse, and input information of a service name and a service directory structure in a popped-up interface;

the page style selecting module is also used for generating a guide according to the source code and selecting the style of the service display interface;

the binding page attribute module is also used for binding the interface display style with the service model entity object attribute extracted by analyzing the MOM object file after the interface display style is confirmed;

the matching pre-generated technical framework module is also used for matching a source code generation framework according to the requirements of the project technical framework after the binding of the business model entity object property is finished;

and the output source code module is also used for outputting the source code structure information through the source code generator.

7. A micro service code generation method based on a service domain data model base is characterized in that: and referencing the service model entity object in the service domain data model library, and converting the service model entity object into an MOM object file.

8. The micro service code generation method based on the service domain data model base according to claim 7, wherein: particularly comprises the steps of S1 establishing a service domain data model base and S2 establishing an MOM object file,

s1 establishing business domain data model base

The data of the business model entity object in the business domain data model base is stored in the database, the business model entity object is stored in the database by data table structured information, and the structured data table comprises business major categories, business detailed categories, entity basic information, entity structured attributes, entity relationship information, entity version information, entity authorization management, entity reference records, entity text attributes and entity history records;

s2 creating MOM object file

A service model entity object in a service domain data model base is quoted and converted into an MOM object file;

the information of the MOM object file is stored in XM L format.

9. The method for generating microservice codes based on the service domain data model base according to claim 8, wherein: the step of S2 creating the MOM object file specifically includes the steps of S201 opening a model tool, S202 introducing a model object, S203 converting the MOM object, S204 modifying the model, and S205 storing the MOM object,

s201 model opening tool

Opening a model tool in a development tool; opening a local development tool, and configuring business domain data model base information in attribute configuration, wherein the business domain data model base information comprises a model base address, a port and user information;

s202 introducing model objects

Introducing a business model entity object through an API (application programming interface); opening a business domain data model base through a local development tool menu guide, inputting query conditions of basic information of personnel in the query conditions, selecting basic information entity objects of the personnel in query results, and introducing the basic information entity objects of the personnel into a model tool by clicking an introduction button;

s203 transforming MOM objects

The business model entity converter converts an introduced business model entity object into an MOM object file; when the lead-in button is clicked, acquiring basic information entity object information of personnel through an interface API (application programming interface) service of a service domain data model library, and converting an MOM (machine object model) object file which can be read or maintained by a model tool through a service model entity converter;

s204 correction model

Correcting and perfecting the entity object information of the business model in the model tool according to the business requirements; after the MOM object file is corrected and converted, loading the MOM object file by a model tool, displaying introduced business model entity object information, and adjusting model attribute information according to business needs, wherein the operation comprises the operation of adding business attributes or modifying data types;

after the business model entity object information is adjusted, synchronizing the adjusted business model entity object into a business domain data model library by calling a business domain data model library interface API service;

s205 storing MOM objects

The method comprises the steps of storing information of MOM objects and forming MOM object files, wherein the information of the MOM object files is stored in an XM L structure, and is converted into an XM L structure for storage through a business model entity converter in the process of introducing business model entity objects, the XM L structure is divided into two parts, the first part is information required by a model tool page and comprises version information, basic information and style information, the second part is introduced business model entity object information and comprises business domains to which the business model entity objects belong and business model entity object attribute information, the information of the MOM object files and the information of the business model entity objects are in one-to-many relation, and a plurality of business model entity objects are introduced at one time or the business model entity object information is introduced for a plurality of times according to business needs.

10. The method for generating microservice codes based on the service domain data model base according to claim 8, wherein: step S3 is also included to generate micro service code, the MOM object file after conversion is input into a source code generator, and the source code generator outputs the micro application or micro service source code structure information after generation by analyzing the MOM object file, selecting page style, binding page attribute, matching pre-generated technical frame and outputting source code;

the step of S3 generating the microservice code specifically includes the steps of S301 parsing the MOM object file, S302 selecting the page style, S303 binding the page property, S304 matching the pre-generated technical framework and S305 outputting the source code,

s301 parsing MOM object file

The MOM object file information is input into a source code generator, the source code generator acquires the MOM object file information and analyzes the MOM object file according to XM L label definition, the MOM object file is selected from a development tool project directory, a right click mouse selects a conversion source code from a menu, and information of a service name and a service directory structure is input into a popup interface;

s302 selecting a page style

Selecting a page display style according to business needs; generating a guide according to the source code, and selecting a service display interface style;

s303 binding page property

Binding the page attribute with the service model entity object attribute information; after the interface display style is confirmed, binding the interface display style with the service model entity object attribute extracted by analyzing the MOM object file;

s304 matching pre-generated technical framework

Matching the technical architecture according to the project technical architecture requirement; after the business model entity object property binding is completed, matching a source code generation framework according to the project technical framework requirement;

s305 output source code

Generating service application source code information; and outputting the source code structure information through a source code generator.

Images