CN116679910B

CN116679910B - Engineering scaffold generation method, device and equipment based on field driving design

Info

Publication number: CN116679910B
Application number: CN202310592514.XA
Authority: CN
Inventors: 李欢; 甘霖
Original assignee: Zhongdian Jinxin Software Co Ltd
Current assignee: Zhongdian Jinxin Software Co Ltd
Priority date: 2023-05-23
Filing date: 2023-05-23
Publication date: 2024-04-05
Anticipated expiration: 2043-05-23
Also published as: CN116679910A

Abstract

The invention provides a method, a device and equipment for generating engineering scaffolds based on field driving design, wherein the method comprises the following steps: the method comprises the steps of obtaining system information, interface information, application service information, field model information and data model information of a target micro-service system, generating an interface packet of a target engineering scaffold corresponding to the target micro-service system according to the interface information of the target micro-service system, generating an application packet of the target engineering scaffold according to the application service information of the target micro-service system, generating a field packet of the target engineering scaffold according to the field service information and the field model information of the target micro-service system, generating a logic implementation packet of the target engineering scaffold according to the interface packet, the application packet and the field packet, and generating an infrastructure packet of the target engineering scaffold according to the system information and the data model information of the target engineering scaffold, so that separation of service logic and system design is realized by adding the logic implementation packet, and code migration is facilitated.

Description

Engineering scaffold generation method, device and equipment based on field driving design

Technical Field

The invention relates to the technical field of computers, in particular to an engineering scaffold generation method, device and equipment based on field driving design.

Background

The Domain driver Design (Domain Driven Design, abbreviated as DDD) is a Design concept for solving business complexity, which is proposed by Eric Evans (Eric Evans) in the literature of Domain driver Design (Domain-driver Design-Tackling Complexity in the Heart of software) published in 2004.

In the related art, a micro service may be designed using a DDD mode. As shown in fig. 1, the micro-service designed using the DDD mode is layered using a four-layer architecture, including: an interface layer, an application layer, a domain layer, and an infrastructure layer. The interface layer is responsible for exposing the interface of the micro service outwards and providing related functional services; the application layer is responsible for providing application services and performing object conversion of the interface layer and the domain layer; the domain layer is a core layer, and all business models and business logics are isolated in the domain layer; the infrastructure layer is responsible for providing general technology and basic services to other layers including intermediate adapters, third party tools, common technology components, database adapters, event buses, southbound gateways, etc. as shown in fig. 1.

However, since the micro-service design is allowed to be updated iteratively, when a new engineering scaffold needs to be generated, the service codes completed in the old engineering scaffold need to be correspondingly migrated to the new engineering scaffold, if the new engineering scaffold is much more changed in terms of the micro-service design than the old engineering scaffold, the cost of code migration is high, and the freshness of the code architecture becomes a problem of reducing the development efficiency and preventing the development progress, so how to realize smoother migration of the codes between different engineering scaffolds is worth researching.

Disclosure of Invention

The present invention aims to solve at least one of the technical problems in the related art to some extent.

Therefore, a first object of the present invention is to provide a method for generating engineering scaffolds based on domain driver design, so as to provide relevant definitions in interface packages, application packages and domain packages in engineering scaffolds by adding logic implementation packages including interface packages, application packages and domain packages in the generated engineering scaffolds, and implement business logic in interface packages, application packages and domain packages included in the logic implementation packages, so as to separate the business logic from system design, and facilitate smooth code migration between engineering scaffolds of different versions.

The second object of the invention is to provide an engineering scaffold generating device based on field driving design.

A third object of the present invention is to propose an electronic device.

A fourth object of the present invention is to propose a computer readable storage medium.

A fifth object of the invention is to propose a computer programme product.

To achieve the above object, an embodiment of a first aspect of the present invention provides a method for generating an engineering scaffold based on a domain driving design, including:

acquiring system information, interface information, application service information, domain model information and data model information of a target micro-service system;

generating an interface packet of a target engineering scaffold corresponding to the target micro-service system according to the interface information of the target micro-service system; wherein the interface package is used for providing interface definition of the target micro-service system;

generating an application package of the target engineering scaffold according to the application service information of the target micro service system; the application package is used for providing application service definition of the target micro-service system;

generating a domain packet of the target engineering scaffold according to the domain service information and the domain model information of the target micro-service system; the domain package is used for providing domain service definition and domain model definition of the target micro-service system;

Generating a logic implementation package of the target engineering scaffold according to the interface package, the application package and the domain package; the logic implementation package is used for implementing service logic in the interface package, the application package and the domain package included in the logic implementation package;

generating an infrastructure package of the target engineering scaffold according to the system information and the data model information of the target engineering scaffold; wherein the infrastructure package is used to provide system definition, data model definition, and implementation business logic for the target micro-service system.

To achieve the above object, a second aspect of the present invention provides an engineering scaffold generating device based on a domain driving design, including:

the acquisition module is used for acquiring system information, interface information, application service information, domain model information and data model information of the target micro-service system;

the first generation module is used for generating an interface packet of a target engineering scaffold corresponding to the target micro-service system according to the interface information of the target micro-service system; wherein the interface package is used for providing interface definition of the target micro-service system;

The second generation module is used for generating an application package of the target engineering scaffold according to the application service information of the target micro-service system; the application package is used for providing application service definition of the target micro-service system;

the third generation module is used for generating a domain packet of the target engineering scaffold according to the domain service information and the domain model information of the target micro-service system; the domain package is used for providing domain service definition and domain model definition of the target micro-service system;

the fourth generation module is used for generating a logic implementation package of the target engineering scaffold according to the interface package, the application package and the domain package; the logic implementation package is used for implementing service logic in the interface package, the application package and the domain package included in the logic implementation package;

a fifth generation module, configured to generate an infrastructure package of the target engineering scaffold according to the system information and the data model information of the target engineering scaffold; wherein the infrastructure package is used to provide system definition, data model definition, and implementation business logic for the target micro-service system.

To achieve the above object, an embodiment of a third aspect of the present invention provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the field driven design based engineering scaffold generation method of the first aspect described above.

To achieve the above object, a fourth aspect of the present invention provides a computer-readable storage medium storing computer instructions for causing the computer to execute the method for generating an engineering scaffold based on the domain-driven design of the first aspect.

In order to achieve the above object, an embodiment of a fifth aspect of the present invention proposes a computer program product comprising a computer program which, when executed by a processor, implements the field driven design based engineering scaffold generation method of the first aspect described above.

The technical scheme provided by the embodiment of the invention comprises the following beneficial effects:

The method comprises the steps of obtaining system information, interface information, application service information, domain model information and data model information of a target micro service system, generating an interface package of a target engineering scaffold corresponding to the target micro service system according to the interface information of the target micro service system, wherein the interface package is used for providing interface definition of the target micro service system, generating an application package of the target engineering scaffold according to the application service information of the target micro service system, generating a domain package of the target engineering scaffold according to the domain service information and the domain model information of the target micro service system, wherein the domain package is used for providing domain service definition and domain model definition of the target micro service system, and generating a logic implementation package of the target engineering scaffold according to the interface package, the application package and the domain package, wherein the logic implementation package is used for implementing service logic in the interface package, the application package and the domain package, and generating an infrastructure package of the target engineering scaffold according to the system information and the data model information of the target engineering scaffold, wherein the infrastructure package is used for providing system definition, the logic implementation service definition and the data model of the target micro service system. Therefore, through newly adding a logic realization package comprising an interface package, an application package and a domain package in the generated engineering scaffold, relevant definition is provided in the interface package, the application package and the domain package in the engineering scaffold, business logic is realized in the interface package, the application package and the domain package which are included in the logic realization package, the business logic is separated from system design, and codes can be smoothly migrated between engineering scaffolds of different versions.

Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.

Drawings

The foregoing and/or additional aspects and advantages of the invention will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:

fig. 1 is a system level structure diagram of a DDD mode in the related art according to an embodiment of the present invention;

fig. 2 is a schematic flow chart of an engineering scaffold generation method based on field driving design according to an embodiment of the present invention;

fig. 3 is a schematic flow chart of another engineering scaffold generation method based on field driving design according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a micro service management page of a target platform according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of an editing system information window of a target platform according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a micro-server system overview of a target platform according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of an interface design page of a micro-server system of a target platform according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of an interface class method design page of a target platform according to an embodiment of the present invention;

FIG. 9 is a schematic diagram of an editing interface method information window of a target platform according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of a data standard page of a target platform according to an embodiment of the present invention;

FIG. 11 is a schematic diagram of an application service design page of a micro-service system of a target platform according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of an application service class method design page of a target platform according to an embodiment of the present invention;

FIG. 13 is a schematic diagram of an information window of an editing application service class method of a target platform according to an embodiment of the present invention;

FIG. 14 is a schematic diagram of a domain services design page of a micro-service system of a target platform according to an embodiment of the present invention;

FIG. 15 is a schematic diagram of a domain service class method design page of a target platform according to an embodiment of the present invention;

FIG. 16 is a schematic diagram of an editing domain service class method information window of a target platform according to an embodiment of the present invention;

FIG. 17 is a schematic diagram of a domain modeling design page of a micro-server system of a target platform according to an embodiment of the present invention;

FIG. 18 is a schematic diagram of a domain object window in editing entity information of a target platform according to an embodiment of the present invention;

FIG. 19 is a schematic diagram of a behavior list window in editing entity information of a target platform according to an embodiment of the present invention;

FIG. 20 is a schematic diagram of a domain modeling design page of a micro-server system of another target platform according to an embodiment of the present invention;

FIG. 21 is a schematic diagram of a value object property window in editing value object information of a target platform according to an embodiment of the present invention;

fig. 22 is a schematic flow chart of another engineering scaffold generation method based on field driving design according to an embodiment of the present invention;

FIG. 23 is a schematic diagram of a domain model derivation page of a micro-server system of a target platform according to an embodiment of the present invention;

FIG. 24 is a schematic diagram of a field design page of a target platform according to an embodiment of the present invention;

FIG. 25 is a diagram of a target platform table index design page according to an embodiment of the present invention;

FIG. 26 is a schematic diagram of a preview DDL page of a target platform according to an embodiment of the present invention;

FIG. 27 is a schematic diagram of a plug-in selection page of a target platform according to an embodiment of the present invention;

FIG. 28 is a schematic diagram of a parameter configuration item page of a target platform according to an embodiment of the present invention;

FIG. 29 is a schematic diagram of an initialization system page of a target platform according to an embodiment of the present invention;

fig. 30 is a schematic diagram of a framework of an engineering scaffold according to an embodiment of the present invention;

fig. 31 is a schematic view of a foundation structure of an engineering scaffold according to an embodiment of the present invention;

FIG. 32 is a system level block diagram of a DDD mode provided by an embodiment of the present invention;

fig. 33 is a schematic structural diagram of an engineering scaffold generating device based on field driving design according to an embodiment of the present invention;

fig. 34 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

Embodiments of the present invention are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are illustrative and intended to explain the present invention and should not be construed as limiting the invention.

Aiming at the problem of high code migration cost between engineering scaffolds of different versions in the related art, the embodiment of the invention provides an engineering scaffold generation method based on a domain drive design, which is used for providing related definitions in an interface packet, an application packet and a domain packet in the engineering scaffold by newly adding the logic implementation packet comprising the interface packet, the application packet and the domain packet in the generated engineering scaffold, realizing business logic in the interface packet, the application packet and the domain packet included in the logic implementation packet, separating the business logic from the system design, and thus, when the system design is changed, only the logic implementation packet in the original engineering scaffold is required to be migrated into the newly generated engineering scaffold, and the migrated logic implementation packet is correspondingly modified based on the related definitions provided by the interface packet, the application packet and the domain packet in the newly generated engineering scaffold, thereby being convenient for relatively smooth code migration between the engineering scaffolds of different versions.

The method, the device and the equipment for generating the engineering scaffold based on the field driving design are described below with reference to the accompanying drawings.

Fig. 2 is a schematic flow chart of an engineering scaffold generation method based on field driving design according to an embodiment of the present invention.

It should be noted that, the execution subject of the engineering scaffold generation method based on the domain driving design in the embodiment of the present invention is the engineering scaffold generation device based on the domain driving design in the embodiment of the present invention, and the engineering scaffold generation device based on the domain driving design may be configured in an electronic device, so that the electronic device may execute the engineering scaffold generation function based on the domain driving design.

As shown in fig. 2, the engineering scaffold generation method based on the domain driving design comprises the following steps:

step 201, system information, interface information, application service information, domain model information and data model information of a target micro service system are acquired.

The target micro service system may be any micro service system including system information, interface information, application service information, domain model information, and data model information.

Optionally, the system information may include system parameters, such as a system name, a system code, a system description, a system port, a service framework, a groupId prefix, an artifactId prefix, a packet path, whether a data source is set, etc., technical components, such as a database driver, a log component, etc., and micro-service parameters, such as an interface implementation start check flag, a transaction success response code, transaction success response information, a service log level, an architecture log level, a log generation path, etc.

Optionally, the interface information may include interface class information and interface class method information, where the interface class information may include an interface class name, an interface class identifier, an interface class description, and the interface class method information may include an interface class method name, an interface class method identifier, an error code, an interface class method description, an interface class method entry parameter name, an interface class method exit parameter name, an interface class method input field, an interface class method output field, and the like.

Alternatively, the application service information may include application service class information and application service class method information, where the application service class information may include an application service class name, an application service class identifier, an application service class description, and the like, and the application service class method information may include an application service class method name, whether the application service class method identifier records a stream, an application service class method description, whether an interface class method input/output is used, an application service class method input field, an application service class method output field, and the like.

Optionally, the domain service information may include domain service class information and domain service class method information, where the domain service class information may include a domain service class name, a domain service class identifier, a domain service class description, and the like, and the domain service class method information may include a domain service class method name, a domain service class method identifier, a domain service class method description, a domain service class method entry parameter name, a domain service class method exit parameter name, a domain service class method input field, a domain service class method output field, and the like.

Alternatively, the domain model information may include aggregate information, entity information, and value object information, wherein the aggregate information may include an aggregate name, an aggregate identifier, an aggregate description, etc., the entity information may include an entity name, an entity identifier, an entity number, an entity description, a domain object, a behavior list, etc., and the value object information may include a value object name, a value object identifier, a value object number, a value object description, a value object attribute, etc.

Alternatively, the domain object may include a solid model, an attribute type, an entity unique identifier, etc., where the solid model may include an anemia model, a hyperemia model, etc., and the attribute type may include a base type, an entity, a value object, etc. It should be noted that the entity unique identifier is an attribute type of an entity, and is used for uniquely identifying the entity, where the entity identifier refers to a character string for identifying the entity in the engineering scaffold code, and is used for distinguishing different entities.

Alternatively, the behavior list may include a behavior name, a behavior encoding behavior input field, a behavior output field, whether a behavior is newly added, and the like.

Alternatively, the data model information may include table names, table fields, table indexes, and DDL (Data Definition Language, database schema definition language) statements.

In a possible implementation manner of this embodiment, the engineering scaffold generating device based on the domain driver design according to the embodiment of the present invention may acquire the system information, interface information, application service information, domain model information and data model information of the target micro service system in real time when the user designs the system information, interface information, application service information, domain model information and data model information of the target micro service system, or may acquire the system information, interface information, application service information, domain model information and data model information of the target micro service system from other devices storing the system information, interface information, application service information, domain model information and data model information of the target micro service system, or may acquire the system information, interface information, application service information, domain model information and data model information of the target micro service system in other public, legal and compliant manners, which is not limited in this embodiment.

Step 202, generating an interface packet of a target engineering scaffold corresponding to the target micro-service system according to the interface information of the target micro-service system.

Wherein the interface package is used for providing interface definition of the target micro-service system. It should be noted that, the interface package in the target engineering scaffold corresponding to the target micro-service system generated by the present invention is only used for providing the interface definition of the target micro-service system, and does not relate to specific functional logic implementation. Also, in this embodiment, the interface package does not allow modification, but may be derived in full and then replaced or overridden.

Optionally, an interface packet of the target engineering scaffold corresponding to the target micro service system can be generated according to interface class information and interface class method information in the interface information of the target micro service system.

And 203, generating an application package of the target engineering scaffold according to the application service information of the target micro service system.

Wherein the application package is used for providing application service definition of the target micro-service system. It should be noted that, the application package in the target engineering scaffold corresponding to the target micro-service system generated by the present invention is only used for providing the application service definition of the target micro-service system, and does not relate to specific functional logic implementation. Also, in the present embodiment, the application package does not allow modification, but can be derived in full quantity and then replaced or overlaid.

Optionally, an application package of the target engineering scaffold corresponding to the target micro service system may be generated according to the application service class information and the application service class method information in the application service information of the target micro service system.

And 204, generating a domain packet of the target engineering scaffold according to the domain service information and the domain model information of the target micro service system.

Wherein the domain package is used for providing domain service definition and domain model definition of the target micro-service system. It should be noted that, the domain package in the target engineering scaffold corresponding to the target micro-service system generated by the present invention is only used for providing the domain service definition and the domain model definition of the target micro-service system, and does not relate to specific functional logic implementation. Also, in the present embodiment, the domain package does not allow modification, but can be derived in full and then replaced or overlaid.

Optionally, a domain packet of the target engineering scaffold corresponding to the target micro service system may be generated according to domain service class information and domain service class method information in the domain service information of the target micro service system, and aggregate information, entity information and value object information in the domain model information.

And step 205, generating a logic implementation package of the target engineering scaffold according to the interface package, the application package and the domain package.

The logic implementation package is used for implementing service logic in an interface package, an application package and a domain package included in the logic implementation package. That is, the logic implementation package in the target engineering scaffold corresponding to the target micro service system generated by the invention includes an interface package, an application package and a domain package, and the logic implementation package relates to specific functional logic implementation of the interface package, the application package and the domain package.

It should be noted that, the logic implementation package in the target engineering scaffold corresponding to the target micro-service system generated by the invention can be independently adjusted and migrated. Therefore, when the system design is changed, compared with the prior art, the logic implementation in the interface package, the application package and the field package in the original engineering scaffold are required to be correspondingly migrated into the corresponding package in the newly generated engineering scaffold.

In one possible implementation manner of this embodiment, the generated interface packet may be added to the logic implementation packet of the target engineering scaffold while the interface packet of the target engineering scaffold corresponding to the target micro service system is generated, the generated application packet may be added to the logic implementation packet of the target engineering scaffold while the application packet of the target engineering scaffold corresponding to the target micro service system is generated, and the generated application packet may be added to the logic implementation packet of the target engineering scaffold while the domain packet of the target engineering scaffold corresponding to the target micro service system is generated, thereby obtaining the logic implementation packet including the interface packet, the application packet, and the domain packet.

In another possible implementation manner of this embodiment, after the interface package, the application package, and the domain package of the target engineering scaffold corresponding to the target micro service system are generated, a logic implementation package including the interface package, the application package, and the domain package may be generated based on the generated interface package, application package, and domain package.

And 206, generating an infrastructure package of the target engineering scaffold according to the system information and the data model information of the target engineering scaffold.

Wherein the infrastructure package is used to provide system definition, data model definition, and implementation business logic for the target microservice system. That is, in the target engineering scaffold corresponding to the target micro-service system generated by the invention, the service implementation of the interface package, the application package and the domain package are all in the logic implementation package and the infrastructure package. Also, the logical implementation package and the infrastructure package may be individually adapted and migrated.

Optionally, an infrastructure package of the target engineering scaffold corresponding to the target micro service system may be generated according to the system parameters, the technical components and the micro service parameters in the system information of the target micro service system, and the table name, the table field, the table index and the DDL statement in the data model information.

According to the engineering scaffold generation method based on the domain drive design, the interface package of the target engineering scaffold corresponding to the target micro service system is generated according to the interface information of the target micro service system by acquiring the system information, the interface information, the application service information, the domain model information and the data model information of the target micro service system, the application package of the target engineering scaffold is generated according to the application service information of the target micro service system, the domain package of the target engineering scaffold is generated according to the domain service information and the domain model information of the target micro service system, the logic implementation package of the target engineering scaffold is generated according to the interface package, the application package and the domain package, and the infrastructure package of the target engineering scaffold is generated according to the system information and the data model information of the target engineering scaffold. Therefore, through newly adding a logic implementation package comprising an interface package, an application package and a domain package in the generated engineering scaffold, relevant definitions are provided in the interface package, the application package and the domain package in the engineering scaffold, business logic is realized in the interface package, the application package and the domain package which are included in the logic implementation package, the business logic is separated from system design, the problem of high code migration cost in the related technology is solved, and the code is conveniently and smoothly migrated.

In order to clearly explain how to obtain system information, interface information, application service information, domain service information and domain model information in the present invention, the present embodiment provides another method for generating engineering scaffolds based on domain driving design, and fig. 3 is a schematic flow diagram of another method for generating engineering scaffolds based on domain driving design according to the embodiment of the present invention.

It should be noted that, the engineering scaffold generation method based on the domain driving design in the embodiment of the present invention is applied to a target platform, where the target platform is used for designing an engineering architecture of a micro-service system.

As shown in fig. 3, the engineering scaffold generation method based on the domain driving design may include the steps of:

step 301, in response to the operation of the newly added micro service system of the user, acquiring the system name, the system port, the groupId prefix, the artifactId prefix and the packet path of the target micro service system input by the user, the service framework of the target micro service system selected by the user, and the system code generated based on the system name of the target micro service system input by the user.

In this embodiment, the target platform provides the query and new functions of the micro service system, as shown in fig. 4, the user may add the micro service system by clicking a new micro service system button in the micro service management page of the target platform, so that the target platform may provide the window for editing the system information as shown in fig. 5 to the user in response to the operation of the new micro service system of the user, to obtain the system name, the system port, the groupId prefix, the artifactId prefix and the packet path of the target micro service system input by the user, the service frame of the target micro service system selected by the user, and the system code generated based on the system name of the target micro service system input by the user.

As shown in fig. 5, the system information further includes a system description and whether a data source is set, and correspondingly, in case that the user selects the set data source, the system information further includes a reference source, so that the system description of the target micro service system input by the user can be acquired in response to the operation of the newly added micro service system of the user, and in case that the user selects the set data source, the reference source of the target micro service system input by the user can be acquired.

Step 302, in response to the operation of creating the interface class by the user, the interface class name and the interface class identification of any interface class input by the user are obtained.

In this embodiment, the target platform provides the design function of the micro service system, as shown in fig. 6, when the user clicks into the micro service system for commodity service, the related design assets of the micro service system for commodity service can be seen: 2 interfaces, 2 application services, 0 domain services, 2 entities and 2 value objects. So that the user can click on the design button to enter the interface design page as shown in fig. 7 to design the interface of the goods service.

As shown in fig. 7, the user may create an interface class by clicking a create class button in the interface design page, so that the target platform may edit a window of interface class information provided to the user in response to the user's create interface class operation, to obtain interface class information of any interface class input by the user.

As a possible implementation manner, the interface class information may include an interface class name and an interface class identifier, so that the interface class name and the interface class identifier of any interface class input by the user may be obtained in response to the user's operation of creating the interface class.

As another possible implementation manner, the interface class information may include an interface class name, an interface class identifier, and an interface class description, so that the interface class name, the interface class identifier, and the interface class description of any interface class input by the user may be acquired in response to the user's operation of creating the interface class.

Step 303, responding to the operation of the user for creating the interface class method of any target interface class, and acquiring the interface class method name and the interface class method identification of any interface class method input by the user.

In this embodiment, the target platform provides the design functionality of the interface class method, and when the user clicks into the modify order inventory interface class, the user can see the related design assets of the modify order inventory interface class, as shown in FIG. 8. Thus, the user can create the interface class method by clicking the create method button, so that the target platform can provide the user with a window for editing the interface class method information as shown in fig. 9 in response to the user's create interface class method operation to acquire the interface class method information input by the user.

As a possible implementation manner, the interface class method information includes an interface class method name and an interface class method identifier, so that the interface class method name and the interface class method identifier of any interface class method input by a user can be obtained in response to the operation of the user on creating the interface class method of any target interface class.

As another possible implementation manner, as shown in fig. 9, the interface class method information includes an interface class method name, an interface class method identifier, an error code, an interface class method description, an interface class method entry parameter name, an interface class method exit parameter name, an interface class method input field, and an interface class method output field, so that the interface class method name, the interface class method identifier, the error code, the interface class method description, the interface class method entry parameter name, the interface class method exit parameter name, and the interface class method input field and the interface class method output field of any interface class method selected by the user of any interface class can be obtained in response to the user operation of creating the interface class method for any target interface class. The optional interface class method input field and the interface class method output field shown in fig. 9 are fields that the target platform newly adds or imports in the data standard page in response to the user operation. The data standard page of the target platform is shown in fig. 10.

Step 304, in response to the operation of creating the application service class, the application service class name and the application service class identification of any application service class input by the user are obtained.

In this embodiment, the target platform provides an application service design function, as shown in fig. 11, after the user switches to the application service design page, the application service class may be created by clicking the create class button, so that the target platform may respond to the user create application service class operation, and provide a window for editing application service class information to the user, so as to obtain application service class information of any application service class input by the user.

As a possible implementation manner, the application service class information may include an application service class name and an application service class identifier, so that the application service class name and the application service class identifier of any application service class input by the user may be obtained in response to an operation of creating the application service class by the user.

As another possible implementation manner, the application service class information may include an application service class name, an application service class identifier, and an application service class description, so that the application service class name, the application service class identifier, and the application service class description of any application service class input by the user may be acquired in response to the user's operation of creating the application service class.

In step 305, in response to the user operation of creating the application service class method for any target application service class, the application service class method name and the application service class method identifier of any application service class method input by the user are obtained.

In this embodiment, the target platform provides the design function of the application service class method, and when the user clicks into the test application service class, as shown in fig. 12, the user can see the related design asset of the application service class, which is the test application. The user can create the application service class method by clicking the create method button, so that the target platform can provide the user with a window for editing application service class method information as shown in fig. 13 in response to the user's create application service class method operation to acquire the application service class method information input by the user.

As a possible implementation manner, the application service class method information includes an application service class method name and an application service class method identifier, so that the application service class method name and the application service class method identifier of any application service class method input by a user can be obtained in response to the user operation of creating the application service class method for any target application service class.

As another possible implementation manner, as shown in fig. 13, the application service class method information includes an application service class method name, an application service class method identifier, whether to record stream, an application service class method description, whether to use interface class method input and output, an application service class method input field, and an application service class method output field, so that an application service class method name, an application service class method identifier, an application service class method description of any application service class method input by a user can be obtained in response to a user operation of creating an application service class method for any target application service class, whether to record stream, whether to use interface class method input and output of any application service class method selected by the user, and an application service class method input field and an application service class method output field of any application service class method selected by the user can be obtained in case that the user selects to not use interface class method input and output. The optional application service class method input field and the application service class method output field shown in fig. 13 are fields that are newly added or imported on the data standard page by the target platform in response to the user operation. The data standard page of the target platform is shown in fig. 10.

And step 306, responding to the operation of creating the domain service class of the user, and acquiring the domain service class name and the domain service class identification of any domain service class input by the user.

In this embodiment, the target platform provides an application service design function, as shown in fig. 14, after the user switches to the domain service design page, the domain service class may be created by clicking the create class button, so that the target platform may respond to the user create domain service class operation, and provide the user with a window for editing domain service class information, so as to obtain domain service class information of any domain service class input by the user.

As a possible implementation manner, the domain service class information may include a domain service class name and a domain service class identifier, so that the domain service class name and the domain service class identifier of any domain service class input by the user may be acquired in response to the user's operation of creating the domain service class.

As another possible implementation manner, the domain service class information may include a domain service class name, a domain service class identifier, and a domain service class description, so that the domain service class name, the domain service class identifier, and the domain service class description of any domain service class input by the user may be acquired in response to the user's creation of the domain service class operation.

Step 307, in response to the user operation of creating the domain service class method for any target domain service class, obtaining the domain service class method name and the domain service class method identifier of any domain service class method input by the user.

In this embodiment, the target platform provides a design function of the domain service class method, and as shown in fig. 15, when the user clicks to enter the domain service class for checking the account, the user can see the related design asset of the domain service class for checking the account. The user can create the domain service class method by clicking the create method button, so that the target platform can provide the user with a window for editing the domain service class method information as shown in fig. 16 in response to the user's create domain service class method operation, so as to acquire the domain service class method information input by the user.

As a possible implementation manner, the domain service class method information includes a domain service class method name and a domain service class method identifier, so that the domain service class method name and the domain service class method identifier of any domain service class method input by a user can be obtained in response to the user operation of creating the domain service class method for any target domain service class.

As another possible implementation manner, as shown in fig. 16, the domain service method information includes a domain service method name, a domain service method identifier, a domain service method description, a domain service method entry parameter name, a domain service method exit parameter name, a domain service method input field, and a domain service method output field, so that a domain service method name, a domain service method identifier, a domain service method description, a domain service method entry parameter name, a domain service method exit parameter name, and a domain service method input field and a domain service method output field of any domain service method selected by a user can be acquired in response to a user operation for creating a domain service method of any target domain service.

Step 308, responding to the newly built aggregation operation of the user, and acquiring the aggregation name and the aggregation identifier of any aggregation input by the user.

In this embodiment, the target platform provides a domain modeling design function, through which a user can design domain model information. Wherein the domain model information includes aggregation information, entity information, and value object information.

As shown in fig. 17, after the user switches to the domain modeling design page, the new aggregation button may be clicked to create an aggregation, so that the target platform may respond to the new aggregation operation of the user and provide a window for editing the aggregation information to the user, so as to obtain any aggregation information input by the user.

As a possible implementation manner, the aggregation information may include an aggregation name and an aggregation identifier, so that any aggregation name and aggregation identifier input by a user may be acquired in response to a user's creation aggregation operation.

As another possible implementation manner, the aggregation information may include an aggregation name, an aggregation identifier, and an aggregation description, so that any aggregation name, aggregation identifier, and aggregation description input by the user may be acquired in response to a user's create aggregation operation.

Step 309, in response to the user operating on any of the first aggregated newly added entities, obtaining the entity name and entity identifier of any entity input by the user, the entity model, attribute type and entity unique identifier of any entity selected by the user, and the behavior name and behavior code of any behavior of any entity input by the user.

As shown in fig. 17, the user may also create an entity in the domain modeling design page by clicking a new entity button on the entity page under any aggregation, so that the target platform may respond to the new entity operation of the user for any first aggregation, and provide a window for editing entity information for the user, so as to obtain entity information of any entity input by the user.

As a possible implementation manner, the entity information includes an entity name, an entity identifier, a domain object and a behavior list, where the domain object is shown in fig. 18, and includes an entity model, an attribute type and an entity unique identifier, the entity model includes an anemia model and a congestion model, the attribute type includes a basic type, an entity and a value object, and the behavior list includes a behavior name and a behavior code, so that the entity name and the entity identifier of any entity input by the user and the entity model, the attribute type and the entity unique identifier of any entity selected by the user and the behavior name and the behavior code of any behavior of any entity input by the user can be obtained in response to the operation of the user on any first aggregated newly added entity.

As another possible implementation manner, the entity information includes an entity name, an entity identifier, an entity number, an entity description, a domain object and a behavior list, where, as shown in fig. 18, the domain object includes an entity model, an attribute type and an entity unique identifier, the entity model includes an anemia model and a congestion model, the attribute type includes a basic type, an entity and a value object, and, as shown in fig. 19, the behavior list includes a behavior name, a behavior code, a behavior input field, a behavior output field and a newly added behavior, so that, in response to a user operation on any first aggregated newly added entity, the entity name, the entity identifier, the entity number and the entity description of any entity input by the user, the entity model, the attribute type and the entity unique identifier of any entity selected by the user, and the behavior name and the behavior code of any behavior input by the user, and the behavior input field and the behavior output field of any behavior input by the user, and in case that the user selects the newly added behavior, the behavior name and the behavior input field and the behavior output field of the newly added behavior selected by the user can be acquired.

Step 310, in response to the user operating on any of the newly added value objects of the second aggregation, obtaining the value object name, the value object identifier, the value object number and the value object description of any of the value objects input by the user, and the value object attribute of any of the value objects selected by the user.

As shown in fig. 20, the user may also create a value object by clicking a new value object button after switching from the entity page to the value object page in any aggregation in the domain modeling design page, so that the target platform may respond to the user operation on the new value object in any second aggregation, provide the window of editing value object information for the user, and obtain the value object information of any value object input by the user.

As a possible implementation manner, as shown in fig. 21, the value object information includes a value object name, a value object identifier, a value object number, a value object description, and a value object attribute, so that the value object name, the value object identifier, the value object number, and the value object description of any value object input by the user and the value object attribute of any value object selected by the user can be obtained in response to the user operating on any newly added value object in the second aggregation.

Step 311, system information and data model information of the target micro service system are acquired.

It should be noted that, in this embodiment, the system information includes technical components and micro-service parameters in addition to the system information mentioned in step 301.

As a possible implementation manner, the technical components and micro service parameters of the target micro service system and the data model information may be obtained in real time when the user designs the technical components and micro service parameters of the target micro service system and the data model information, or the technical components and micro service parameters of the target micro service system and the data model information may be obtained from other devices storing the technical components and micro service parameters of the target micro service system and the data model information, or the technical components and micro service parameters of the target micro service system and the data model information may be obtained in other public, legal and compliance manners, which is not limited in this embodiment.

Step 312, according to the interface information of the target micro-service system, generating an interface packet of the target engineering scaffold corresponding to the target micro-service system.

And step 313, generating an application package of the target engineering scaffold according to the application service information of the target micro service system.

And step 314, generating a domain package of the target engineering scaffold according to the domain service information and the domain model information of the target micro service system.

And step 315, generating a logic implementation package of the target engineering scaffold according to the interface package, the application package and the domain package.

And step 316, generating an infrastructure package of the target engineering scaffold according to the system information and the data model information of the target engineering scaffold.

It should be noted that the execution of steps 312-316 can be referred to the execution of steps 202-206 in the above embodiment, and the principle is the same, and will not be described herein.

In summary, system information, interface information, application service information, domain service information, and domain model information input or selected by a user can be obtained through the target platform.

As can be seen from the above analysis, the system information further includes technical components and micro-service parameters, and in order to clearly illustrate how to obtain the technical components and the micro-service parameters and the data model information in the above embodiment, another engineering scaffold generation method based on the domain driving design is provided in this embodiment, and fig. 22 is a flow chart of another engineering scaffold generation method based on the domain driving design provided in the embodiment of the present invention.

Similarly, the engineering scaffold generation method based on the domain-driven design of the embodiment of the invention is applied to a target platform for designing an engineering architecture of a micro-service system.

As shown in fig. 22, the engineering scaffold generation method based on the domain driving design may include the steps of:

step 2201, acquiring system information, interface information, application service information, domain service information and domain model information of a target micro-service system.

It should be noted that, the system information in this step may include a system name, a system code, a system port, a groupId prefix, an artifactId prefix, and a packet path of the target micro service system, and a service framework of the target micro service system selected by the user, and may further include a system description and whether to set a data source, where correspondingly, in the case where the user selects to set the data source, the system information further includes a reference source.

It should be noted that, the executing process of the system information, the interface information, the application service information, the domain service information and the domain model information of the target micro service system obtained in this step may refer to the executing process of steps 301 to 310 in the previous embodiment, and the principle is the same, which is not described herein again.

At step 2202, table fields selected by a user based on a domain model of a target micro-service system are obtained in response to a user data modeling operation of the target micro-service system.

In this embodiment, the target platform provides the data modeling function of the micro service system, alternatively, the user may perform data modeling by clicking a data modeling button in an overview page of any micro service system on the target platform (as shown in fig. 6, the data modeling button of the micro service system, such as the commodity service, is in the upper right corner), so that the target platform may provide the user with a domain model derivation page as shown in fig. 23 in response to the user performing the data modeling operation on the target micro service system, and obtain the table field selected by the user based on the domain model of the target micro service system.

Step 2203, in response to the new deduction operation of the table field by the user, obtains the first field information of the table field, the table name and the table description input by the user.

Alternatively, as shown in fig. 23, the user may perform data modeling by clicking a new deducing button after selecting a table field from the left domain model on the domain model deducing page, so that the target platform may provide the user with the field design page shown in fig. 24 in response to the new deducing operation of the table field by the user, and acquire the first field information of the table field, the table name and the table description input by the user. Wherein the first field information includes a field source, a field name, a field type, a field length, and a field decimal point location. The first field information is non-editable by the user.

Step 2204, in response to the user editing operation on the table field, obtains the second field information of the table field edited by the user.

In this embodiment, the user may edit the second field information of the table field on the target platform, so that the target platform may obtain the second field information of the table field edited by the user in response to the user's editing operation on the table field, where the second field information includes whether the field is null, whether the field is a primary key, and a field comment.

In step 2205, in response to the user's index adding operation, the index method and the table index edited by the user are obtained.

As shown in fig. 25, the user may further add a table index to the index design page, so that the target platform may obtain an indexing method and a table index edited by the user in response to the user's index adding operation. Wherein the table index includes an index name, an index field, an index type, and an index annotation. The indexing method is preset and not editable by the user.

Step 2206 obtains a DDL statement generated based on the table name, the table field, and the table index.

In this embodiment, the target platform may generate a corresponding DDL (Data Definition Language, database schema definition language) statement based on the table name, table field, and table index. For example, for the table names, table fields, and table indexes shown in fig. 24 and 25, the target platform may generate DDL statements as shown in fig. 26.

Step 2207, in response to the user downloading the engineering scaffold of the target micro service system, obtains the database driver, the log component, the interface implementation start check mark, the service log level and the architecture log level of the target micro service system selected by the user, and the transaction success response code, the transaction success response information and the log generation path of the target micro service system input by the user.

In this embodiment, the target platform provides the function of downloading the engineering scaffold of the micro service system, alternatively, the user may perform the downloading of the engineering scaffold by clicking an engineering scaffold download button in an overview page of any micro service system on the target platform (as shown in fig. 6, the engineering scaffold download button of the micro service system, which is commodity service, is in the upper right corner), so that the target platform may provide the plug-in selection page shown in fig. 27, the parameter configuration item page shown in fig. 28, and the initializing system page shown in fig. 29 to the user in response to the downloading operation of the engineering scaffold of the target micro service system by the user, and acquire the database driver, the log component, the interface implementation start check mark, the service log level, the architecture log level of the target micro service system, and the transaction success response code, the transaction success response information, and the log generation path of the target micro service system input by the user.

Optionally, as shown in fig. 29, the user may also select whether to use an existing data source or a newly created data source at the initialization system page. For example, as shown in fig. 29, the target platform may acquire a path of selecting an existing data source inputted by the user in case the user clicks the select existing data source button to acquire the existing data source selected by the user based on the path.

Step 2208, generating an interface packet of the target engineering scaffold corresponding to the target micro-service system according to the interface information of the target micro-service system.

Step 2209, generating an application package of the target engineering scaffold according to the application service information of the target micro service system.

Step 2210, generating a domain package of the target engineering scaffold according to the domain service information and the domain model information of the target micro service system.

Step 2211, generating a logic implementation package of the target engineering scaffold according to the interface package, the application package and the domain package.

Step 2212, generating an infrastructure package of the target engineering scaffold according to the system information and the data model information of the target engineering scaffold.

It should be noted that, the execution of steps 2208-2212 can be referred to the execution of steps 202-206 in the above embodiment, and the principle is the same, which is not repeated here.

In summary, the acquisition of technical components and microservice parameters, as well as data model information, entered or selected by a user through a target platform may be implemented.

In order to clearly illustrate the engineering scaffold produced in the present invention, an example will now be described.

Fig. 30 is a schematic diagram of a framework of an engineering scaffold according to an embodiment of the present invention.

As shown in fig. 30, the created engineering scaffold is a depositserviceengineering scaffold, that is, the target micro service system is the deposit product micro service named deposit product micro service shown in fig. 5, and the system is encoded as the depositservicedeposit product micro service. And, the depositService engineering scaffold includes an interface package (depositService-api), an application package (depositService-application), a domain package (depositService-domain), a logic implementation package (depositService-implementation), and a basic implementation package (depositService-infrastructure). The logic implementation package (DepositService-implementation) includes an interface package (DepositService-api), an application package (DepositService-application), and a domain package (DepositService-domain). Thus, relevant definitions are provided in an interface package (DepositService-api), an application package (DepositService-application) and a domain package (DepositService-domain) in the DepositService engineering scaffold, and business logic is implemented in a logic implementation package (DepositService-implementation) in the DepositService engineering scaffold, so that the business logic is separated from the system design, and codes can be smoothly migrated between different versions of engineering scaffolds.

Specifically, business logic is implemented within an interface package (DepositService-api), an application package (DepositService-application), and a domain package (DepositService-domain) in a logic implementation package (DepositService-implementation).

Alternatively, the infrastructure of the created engineering scaffold may be as shown in fig. 31. It should be noted that this infrastructure can be customized as appropriate based on the actual situation of the different projects.

Alternatively, in the generated engineering scaffold, the naming rule of the generated code class may be as shown in the following table:

TABLE 1 code class naming convention

Code class	Naming the name
		API interface class	***FacadeService
Application service interface class	***ApplicationService
		DomainService interface class	***DomainService
Method for entering ginseng	***InputDTO
		Method for producing ginseng	***OutputDTO
Persistent layer data model class	***PO
		ORM class	***Mapper
Error code enumeration class	ErrorCodeEnum

It should be noted that, the system hierarchy structure of the DDD mode in the present invention is different from the system hierarchy structure of the DDD mode in the related art, and as shown in fig. 32, the system hierarchy structure of the DDD mode in the present invention has one more implementation layer than the system hierarchy structure of the DDD mode in the related art. The content of the implementation layer is specific logic implementation aiming at the interface layer, the application layer and the domain layer.

In order to achieve the above embodiment, the invention further provides an engineering scaffold generation device based on the field driving design.

Fig. 33 is a schematic structural diagram of an engineering scaffold generating device based on field driving design according to an embodiment of the present invention.

As shown in fig. 33, the engineering scaffold generation device based on the domain driving design includes: an acquisition module 3301, a first generation module 3302, a second generation module 3303, a third generation module 3304, a fourth generation module 3305, and a fifth generation module 3306.

An acquisition module 3301, configured to acquire system information, interface information, application service information, domain model information, and data model information of a target micro-service system;

the first generating module 3302 is configured to generate an interface packet of a target engineering scaffold corresponding to the target micro-service system according to interface information of the target micro-service system; the interface package is used for providing interface definition of the target micro-service system;

the second generating module 3303 is configured to generate an application packet of the target engineering scaffold according to the application service information of the target micro service system; the application package is used for providing application service definition of the target micro-service system;

The third generating module 3304 is configured to generate a domain packet of the target engineering scaffold according to the domain service information and the domain model information of the target micro service system; the domain package is used for providing domain service definition and domain model definition of the target micro-service system;

a fourth generating module 3305, configured to generate a logic implementation package of the target engineering scaffold according to the interface package, the application package and the domain package; the logic implementation package is used for implementing service logic in an interface package, an application package and a domain package which are included in the logic implementation package;

a fifth generating module 3306, configured to generate an infrastructure package of the target engineering scaffold according to the system information and the data model information of the target engineering scaffold; wherein the infrastructure package is used to provide system definition, data model definition, and implementation business logic for the target microservice system.

Further, in one possible implementation of an embodiment of the present invention, the system information includes a system name, a system code, a system port, a service frame, a groupId prefix, an artifactId prefix, and a packet path;

an acquisition module 3301 for:

and responding to the operation of the newly added micro service system of the user, acquiring the system name, the system port, the groupId prefix, the artifactId prefix and the packet path of the target micro service system input by the user, the service framework of the target micro service system selected by the user, and the system code generated based on the system name of the target micro service system input by the user.

Further, in a possible implementation manner of the embodiment of the present invention, the system information further includes a system description and whether to set the data source, and correspondingly, in the case that the user selects to set the data source, the system information further includes a reference source;

an acquisition module 3301 for:

and responding to the operation of the newly added micro service system of the user, acquiring the system description of the target micro service system input by the user, and acquiring the reference source of the target micro service system input by the user under the condition that the user selects the set data source.

Further, in one possible implementation manner of the embodiment of the present invention, the system information further includes a technical component and a micro-service parameter, the technical component includes a database driver and a log component, and the micro-service parameter includes an interface implementation start check flag, a transaction success response code, transaction success response information, a service log level, an architecture log level, and a log generation path;

an acquisition module 3301 for:

and responding to the engineering scaffold downloading operation of the user on the target micro-service system, acquiring a database driver, a log component and an interface realization start check mark, a service log level and a framework log level of the target micro-service system selected by the user, and inputting a transaction success response code, transaction success response information and a log generation path of the target micro-service system by the user.

Further, in a possible implementation manner of the embodiment of the present invention, the interface information includes interface class information and interface class method information, the interface class information includes an interface class name and an interface class identifier, and the interface class method information includes an interface class method name and an interface class method identifier;

an acquisition module 3301 for:

responding to the operation of creating the interface class of the user, and acquiring the interface class name and the interface class identification of any interface class input by the user;

and responding to the operation of the interface class creating method of the user aiming at any target interface class, and acquiring the interface class method name and the interface class method identification of any interface class method input by the user.

Further, in a possible implementation manner of the embodiment of the present invention, the interface class information further includes an interface class description; the interface class method information also comprises error codes, interface class method descriptions, interface class method input parameter names, interface class method output parameter names, interface class method input fields and interface class method output fields;

an acquisition module 3301 for:

responding to the operation of creating the interface class of the user, and acquiring the interface class name, the interface class identifier and the interface class description of any interface class input by the user;

Responding to the operation of the interface class creating method of any target interface class by a user, acquiring the interface class method name, the interface class method identifier, the error code, the interface class method description, the interface class method input parameter name and the interface class method output parameter name of any interface class method input by the user, and the interface class method input field and the interface class method output field of any interface class method selected by the user.

Further, in a possible implementation manner of the embodiment of the present invention, the application service information includes application service class information and application service class method information, the application service class information includes an application service class name and an application service class identifier, and the application service class method information includes an application service class method name and an application service class method identifier;

an acquisition module 3301 for:

responding to the operation of creating the application service class of the user, and acquiring the application service class name and the application service class identification of any application service class input by the user;

and responding to the operation of the user for creating the application service class method aiming at any target application service class, and acquiring the application service class method name and the application service class method identification of any application service class method input by the user.

Further, in a possible implementation manner of the embodiment of the present invention, the application service class information further includes an application service class description; the application service class method information also comprises whether to record stream, application service class method description, whether to use interface class method input and output, application service class method input field and application service class method output field;

an acquisition module 3301 for:

responding to the operation of creating the application service class of the user, and acquiring the application service class name, the application service class identification and the application service class description of any application service class input by the user;

responding to the operation of creating the application service class method of any target application service class by a user, acquiring the application service class method name, the application service class method identification and the application service class method description of any application service class method input by the user, and whether the user selects any application service class method to record the running water, whether the user uses the interface class method to input and output, and acquiring the application service class method input field and the application service class method output field of any application service class method selected by the user under the condition that the user selects to input and output without using the interface class method.

Further, in a possible implementation manner of the embodiment of the present invention, the domain service information includes domain service class information and domain service class method information, the domain service class information includes a domain service class name and a domain service class identifier, and the domain service class method information includes a domain service class method name and a domain service class method identifier;

an acquisition module 3301 for:

responding to the operation of creating the domain service class of the user, and acquiring the domain service class name and the domain service class identification of any domain service class input by the user;

and responding to the operation of the user for creating the domain service class method aiming at any target domain service class, and acquiring the domain service class method name and the domain service class method identification of any domain service class method input by the user.

Further, in a possible implementation manner of the embodiment of the present invention, the domain service class information further includes a domain service class description, and the domain service class method information further includes a domain service class method description, a domain service class method entry parameter name, a domain service class method exit parameter name, a domain service class method input field, and a domain service class method output field;

An acquisition module 3301 for:

responding to the operation of creating the domain service class of the user, and acquiring the domain service class name, the domain service class identifier and the domain service class description of any domain service class input by the user;

responding to the operation of a user for creating a domain service class method of any target domain service class, acquiring a domain service class method name, a domain service class method identifier, a domain service class method description, a domain service class method entry parameter name and a domain service class method exit parameter name of any domain service class method input by the user, and a domain service class method input field and a domain service class method output field of any domain service class method selected by the user.

Further, in one possible implementation manner of the embodiment of the present invention, the domain model information includes aggregate information, entity information and value object information, the aggregate information includes an aggregate name and an aggregate identifier, the entity information includes an entity name, an entity identifier, a domain object and a behavior list, the domain object includes an entity model, an attribute type and an entity unique identifier, the entity model includes an anemia model and a congestion model, the attribute type includes a basic type, an entity and a value object, the behavior list includes a behavior name and a behavior code, and the value object information includes a value object name, a value object identifier, a value object number, a value object description and a value object attribute;

An acquisition module 3301 for:

responding to a new aggregation operation of a user, and acquiring an aggregation name and an aggregation identifier of any aggregation input by the user;

responding to the operation of the user on any first aggregated newly added entity, acquiring the entity name and entity identifier of any entity input by the user, the entity model, attribute type and entity unique identifier of any entity selected by the user, and the behavior name and behavior code of any behavior of any entity input by the user;

and responding to the operation of the user on any newly added value object of the second aggregation, and acquiring the value object name, the value object identification, the value object number and the value object description of any value object input by the user and the value object attribute of any value object selected by the user.

Further, in one possible implementation manner of the embodiment of the present invention, the aggregate information further includes an aggregate description, the entity information further includes an entity number and an entity description, and the behavior list further includes a behavior input field, a behavior output field, and whether to add a behavior newly;

an acquisition module 3301 for:

responding to a new aggregation operation of a user, and acquiring an aggregation name, an aggregation identifier and an aggregation description of any aggregation input by the user;

Responding to the operation of the user on any first aggregated newly added entity, acquiring the entity name, entity identification, entity number and entity description of any entity input by the user, the entity model, attribute type and entity unique identification of any entity selected by the user, the behavior name and behavior code of any behavior of any entity input by the user, the behavior input field and behavior output field of any behavior input by the user, and acquiring the behavior name and behavior code of the newly added behavior input by the user and the behavior input field and behavior output field of the newly added behavior selected by the user under the condition that the user selects the newly added behavior.

Further, in one possible implementation of an embodiment of the present invention, the data model information includes a table name, a table field, a table index, and a database schema definition language DDL statement;

an acquisition module 3301 for:

responding to data modeling operation of a user on a target micro-service system, and acquiring a table field selected by the user based on a field model of the target micro-service system;

responding to a new adding deduction operation of a user on a table field, and acquiring first field information of the table field, a table name and a table description input by the user; wherein the first field information includes a field source, a field name, a field type, a field length, and a field decimal point location;

Responding to the editing operation of the user on the table field, and acquiring second field information of the table field edited by the user; the second field information comprises whether a field is empty, whether the field is a primary key and a field annotation;

responding to the index adding operation of a user, and acquiring an index method and a table index edited by the user; wherein the table index includes an index name, an index field, an index type, and an index annotation;

DDL statements generated based on a table name, a table field, and a table index are obtained.

It should be noted that the foregoing explanation of the embodiment of the engineering scaffold generation method based on the domain driving design is also applicable to the engineering scaffold generation device based on the domain driving design of the embodiment, and will not be repeated here.

In order to achieve the above embodiment, the present invention further proposes an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; the storage stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute the engineering scaffold generating method based on the domain driving design according to any one of the above embodiments of the present invention.

In order to implement the above embodiments, the present invention also proposes a computer-readable storage medium storing computer instructions for causing a computer to execute the engineering scaffold generation method based on the domain drive design proposed in any one of the above embodiments of the present invention.

In order to implement the above embodiments, the present invention also proposes a computer program product comprising a computer program which, when executed by a processor, implements the field driven design based engineering scaffold generation method according to any of the above embodiments of the present invention.

It should be noted that the electronic device shown in fig. 34 is only an example, and should not impose any limitation on the functions and application scope of the embodiments of the present invention.

As shown in fig. 34, the electronic device includes:

memory 3401, processor 3402, and computer programs stored on memory 3401 and executable on processor 3402.

The processor 3402, when executing the program, implements the engineering scaffold generation method based on the domain-driven design provided in any of the above embodiments.

Further, the electronic device further includes:

A communication interface 3403 for communication between the memory 3401 and the processor 3402.

A memory 3401 for storing a computer program executable on the processor 3402.

Memory 3401 may comprise high-speed RAM memory or may also comprise non-volatile memory (non-volatile memory), such as at least one disk memory.

And a processor 3402, configured to implement the engineering scaffold generation method based on the domain driving design according to any of the above embodiments when executing the program.

If the memory 3401, the processor 3402 and the communication interface 3403 are implemented independently, the communication interface 3403, the memory 3401 and the processor 3402 may be connected to each other through a bus and accomplish communication with each other. The bus may be an industry standard architecture (Industry Standard Architecture, abbreviated ISA) bus, an external device interconnect (Peripheral Component, abbreviated PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated EISA) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 34, but not only one bus or one type of bus.

Alternatively, in a specific implementation, if the memory 3401, the processor 3402 and the communication interface 3403 are implemented integrally on a chip, the memory 3401, the processor 3402 and the communication interface 3403 may complete communication with each other through internal interfaces.

The processor 3402 may be a central processing unit (Central Processing Unit, abbreviated as CPU) or an application specific integrated circuit (Application Specific Integrated Circuit, abbreviated as ASIC) or one or more integrated circuits configured to implement embodiments of the present invention.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present invention, the meaning of "plurality" means at least two, for example, two, three, etc., unless specifically defined otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and additional implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order from that shown or discussed, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present invention.

Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

It is to be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. As with the other embodiments, if implemented in hardware, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.

Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.

In addition, each functional unit in the embodiments of the present invention may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like. While embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the invention, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the invention.

Claims

1. The engineering scaffold generation method based on the field driving design is characterized by being applied to a target platform, wherein the target platform is used for designing an engineering framework of a micro-service system;

the method comprises the following steps:

2. The method of claim 1, wherein the system information includes a system name, a system code, a system port, a service framework, a groupId prefix, an artifactId prefix, and a packet path;

the obtaining the system information of the target micro service system includes:

3. The method according to claim 2, wherein the system information further comprises a system description and whether a data source is set, and correspondingly, in case the user selects to set a data source, the system information further comprises a reference source;

the acquiring the system information of the target micro service system further includes:

and responding to the operation of the newly added micro service system of the user, acquiring the system description of the target micro service system input by the user, and acquiring the reference source of the target micro service system input by the user under the condition that the user selects a set data source.

4. The method of claim 3, wherein the system information further comprises a technical component comprising a database driver and a logging component and a micro-service parameter comprising an interface implementation initiation check flag, a transaction success response code, transaction success response information, a traffic log level, an architecture log level, and a log generation path;

and responding to the engineering scaffold downloading operation of the target micro-service system by a user, acquiring a database driver, a log component and an interface realization start check mark, a service log level and an architecture log level of the target micro-service system selected by the user, and inputting a transaction success response code, transaction success response information and a log generation path of the target micro-service system by the user.

5. The method of claim 1, wherein the interface information comprises interface class information and interface class method information, the interface class information comprising an interface class name and an interface class identification, the interface class method information comprising an interface class method name and an interface class method identification;

the obtaining the interface information of the target micro-service system includes:

and responding to the operation of the user for creating the interface class method of any target interface class, and acquiring the interface class method name and the interface class method identification of any interface class method input by the user.

6. The method of claim 5, wherein the interface class information further comprises an interface class description; the interface method information also comprises error codes, interface method description, interface method input parameter names, interface method output parameter names, interface method input fields and interface method output fields;

Responding to the operation of the user for creating the interface class method of any target interface class, acquiring the interface class method name, the interface class method identifier, the error code and the interface class method description of any interface class method input by the user, inputting the parameter name of the interface class method and outputting the parameter name of the interface class method, and inputting the field and outputting the field of the interface class method of any interface class method selected by the user.

7. The method of claim 1, wherein the application service information comprises application service class information and application service class method information, the application service class information comprises an application service class name and an application service class identification, and the application service class method information comprises an application service class method name and an application service class method identification;

the obtaining the application service information of the target micro service system includes:

and responding to the operation of the user for creating the application service class method of any target application service class, and acquiring the application service class method name and the application service class method identification of any application service class method input by the user.

8. The method of claim 7, wherein the application service class information further comprises an application service class description; the application service class method information also comprises whether to record stream, application service class method description, whether to use interface class method input and output, application service class method input field and application service class method output field;

responding to the operation of creating the application service class of the user, and acquiring the application service class name, the application service class identifier and the application service class description of any application service class input by the user;

responding to the operation of the user for creating the application service class method of any target application service class, acquiring the application service class method name, the application service class method identification and the application service class method description of any application service class method input by the user, and whether the user selects whether the application service class method is recorded in a running way or not, whether the user selects to use the interface class method input and output, and acquiring the application service class method input field and the application service class method output field of any application service class method selected by the user under the condition that the user selects not to use the interface class method input and output.

9. The method of claim 1, wherein the domain service information comprises domain service class information and domain service class method information, the domain service class information comprises a domain service class name and a domain service class identifier, and the domain service class method information comprises a domain service class method name and a domain service class method identifier;

the obtaining the domain service information of the target micro service system includes:

and responding to the operation of the user for creating the domain service class method of any target domain service class, and acquiring the domain service class method name and the domain service class method identification of any domain service class method input by the user.

10. The method of claim 9, wherein the domain service class information further comprises a domain service class description, and wherein the domain service class method information further comprises a domain service class method description, a domain service class method entry name, a domain service class method exit name, a domain service class method input field, and a domain service class method output field;

responding to the operation of the user for creating the domain service class method of any target domain service class, acquiring the domain service class method name, the domain service class method identification, the domain service class method description, the domain service class method entry parameter name and the domain service class method exit parameter name of any domain service class method input by the user, and the domain service class method input field and the domain service class method output field of any domain service class method selected by the user.

11. The method of claim 1, wherein the domain model information comprises aggregate information, entity information and value object information, the aggregate information comprises an aggregate name and an aggregate identifier, the entity information comprises an entity name, an entity identifier, a domain object and a behavior list, the domain object comprises an entity model, an attribute type and an entity unique identifier, the entity model comprises an anemia model and a congestion model, the attribute type comprises a base type, an entity and a value object, the behavior list comprises a behavior name and a behavior code, and the value object information comprises a value object name, a value object identifier, a value object number, a value object description and a value object attribute;

The obtaining the domain model information of the target micro-service system comprises the following steps:

12. The method of claim 11, wherein the aggregate information further comprises an aggregate description, the entity information further comprises an entity number and an entity description, and the behavior list further comprises a behavior input field, a behavior output field, and whether behavior is newly added;

Responding to the newly built aggregation operation of the user, and acquiring an aggregation name, an aggregation identifier and an aggregation description of any aggregation input by the user;

responding to the operation of the user on any first aggregated newly added entity, acquiring the entity name, entity identification, entity number and entity description of any entity input by the user, the entity model, attribute type and entity unique identification of any entity selected by the user, the action name and action code of any action of any entity input by the user, the action input field and action output field of any action input by the user, and acquiring the action name and action code of the newly added action input by the user and the action input field and action output field of the newly added action selected by the user under the condition that the user selects the newly added action.

13. The method of claim 1, wherein the data model information includes table names, table fields, table indexes, and database schema definition language DDL statements;

the obtaining the data model information of the target micro-service system comprises the following steps:

Responding to data modeling operation of a user on the target micro-service system, and acquiring a table field selected by the user based on a field model of the target micro-service system;

responding to the new deduction operation of the user on the table field, and acquiring first field information of the table field, the table name and the table description input by the user; wherein the first field information includes a field source, a field name, a field type, a field length, and a field decimal point location;

responding to the editing operation of the user on the table fields, and acquiring second field information of the table fields edited by the user; wherein the second field information comprises whether a field is empty, whether the field is a primary key and a field annotation;

responding to the index adding operation of the user, and acquiring an index method and a table index edited by the user; wherein the table index includes an index name, an index field, an index type, and an index annotation;

and acquiring DDL sentences generated based on the table names, the table fields and the table indexes.

14. An engineering scaffold generation device based on field driven design, characterized in that the device comprises:

15. An electronic device, comprising:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-13.

16. A computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-13.

17. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1-13.