Method and system for efficiently expanding business object attributes of multi-business-state platform

Abstract

The invention discloses a method and a system for efficiently expanding business object attributes of a multi-business platform. The method comprises the following steps of: constructing a flattened multi-module platform domain object design; scanning and collecting business object definitions based on the dependency relationship; reading a description object extension relation file set, and performing extension relation screening; a business object set with an expansion relation and a business object set without an expansion relation are split, the business object set with the expansion relation and the business object set without the expansion relation are combined and subjected to duplicate removal attribute definition, then a business object complete definition is output, and the business object complete definition is not processed. According to the method, modularized disassembly and modularized recombination thinking of business object attributes are combined with a flattened extension design method, so that the middle platform system can easily meet the multiple requirements of adding, adjusting and even eliminating new business attributes, market changes can be quickly responded, and diversified business scenes can be powerfully supported and endowed.

Description

Technical Field

[0001] The present invention relates to the field of business middle platforms, and in particular to a method and system for efficiently expanding the attributes of business objects in a multi-format middle platform. Background Art

[0002] In an ever-changing business environment, the business middle platform is like the central nervous system of an enterprise, deeply extracting the common demands of each business line and steadily accumulating core business capabilities in the form of shared services. Faced with ever-changing business needs and emerging business scenario challenges, the middle platform needs an efficient and agile response mechanism to freely add or reconstruct business object attributes without shaking the rock-solid stability and excellent performance of the existing system.

[0003] In the current landscape of multiple business formats and complex business logic, the technical bottlenecks encountered by the current business middle-office architecture in dealing with complex adaptability and expansion of business object attributes are becoming increasingly prominent.

[0004] To solve the above problems, the current common solutions for business attribute extension are:

[0005] 1. Metadata-driven design:

[0006] Using the metadata-driven design pattern, business attributes are stored in the form of metadata. Additional attributes of each business entity can be dynamically defined and managed through metadata, so that when adding new business attributes, there is no need to modify the core code, only update the relevant metadata.

[0007] Advantages of this solution: high flexibility, easy and dynamic management of business attributes, no need to frequently modify core code, and conducive to agile iteration.

[0008] Disadvantages of this solution: Improper metadata management and updating may cause data consistency issues, and excessive reliance on metadata may lead to degraded query performance.

[0009] 2. Attribute plug-in design:

[0010] Design attribute plug-in modules to provide independent attribute packages for different business formats or business scenarios. When new business formats are added or existing business formats need to extend attributes, you only need to develop and load the corresponding attribute plug-in, thereby realizing hot-swap and dynamic expansion of business attributes.

[0011] The following is a detailed design scheme for implementing business object attribute extension based on Java attribute plug-in design:

[0012] Define basic interfaces and abstract classes: Create an AttributePlugin interface or abstract class to specify the methods that all attribute plug-ins need to implement, such as getValue() to obtain attribute values ​​and setValue() to set attribute values.

[0013] Create specific attribute plugins: For each additional business object attribute, create a new plugin that implements the above interface. For example, if you want to add an address attribute to the user object, you can create an AddressPlugin.

[0014] Business object extension design: Business objects (such as Order) need to contain a plug-in container to store all attribute plug-ins loaded by it. It also provides methods for adding and removing plug-ins and obtaining plug-ins by plug-in name.

[0015] Example: Dynamically add new attribute plugins to the order object based on demand at runtime.

[0016] Advantages of this solution: modularity and strong scalability. New functions or properties can be implemented by loading plug-ins without affecting the operation of the original system.

[0017] Disadvantages of this solution: Plug-in management and maintenance is a challenge, and the compatibility and stability between plug-ins need to be ensured, and the overall monitoring and operation and maintenance of the system are required to be high.

[0018] 3. Flexible data table structure design (EAV or JSON fields):

[0019] In database design, the EAV (Entity-Attribute-Value) model or semi-structured JSON fields are used to allow flexible storage of non-predefined attributes, so that changes in business attributes will not lead to frequent changes in the database table structure.

[0020] 3.1. The EAV model allows an entity to have a dynamic, unknown number of attributes, each of which has a corresponding value. In traditional database design, each entity type usually corresponds to a fixed table, in which the columns represent predefined attributes; in the EAV model, the attributes of the entity and their corresponding values ​​are stored in different tables. For example, for a user object, the basic information can be placed in an order table, while the dynamic or indefinite number of attributes are stored in two other tables: entity_attributes (storing attribute names) and attribute_values ​​(storing attribute values ​​associated with entity IDs). In this way, when you need to add new attributes, you only need to insert new attribute records into the entity_attributes table and add corresponding attribute values ​​for each entity in the attribute_values ​​table.

[0021] 3.2. JSON field: Use JSON type fields supported by relational databases (such as JSON type in MySQL, jsonb type in PostgreSQL, etc.) to store all additional, non-fixed attributes in a field in the form of JSON objects. In this way, when you need to extend the attributes, you don't need to modify the table structure, you can directly add key-value pairs inside the JSON object.

[0022] 3.3. Key-value pair table: Another approach is to create a separate key-value pair table to store all extensible attributes of any entity. This table usually contains the entity ID, attribute name, and attribute value.

[0023] Advantages of this solution: It has good adaptability to data storage with non-fixed structure and is convenient for adding and changing new attributes.

[0024] Disadvantages of this solution: It sacrifices database consistency and query efficiency. Especially when EAV mode is used extensively or complex queries are processed, the performance may not be as good as traditional relational databases. Summary of the invention

[0025] The purpose of the present invention is to overcome the shortcomings and deficiencies of the prior art and to provide a method for efficiently expanding the business object attributes of a multi-format middle platform, aiming to achieve flexible expansion and intelligent optimization of business object attributes.

[0026] Another object of the present invention is to provide a system for efficiently expanding the business object attributes of a multi-format middle platform.

[0027] The purpose of the present invention is achieved through the following technical solutions:

[0028] A method for efficiently extending the business object attributes of a multi-format middle platform includes the following steps:

[0029] S1. Build a flat multi-module middle platform domain object design;

[0030] S2, scanning and collecting business object definitions based on dependencies;

[0031] S3, screening the extended relationship of business object definition: reading the set of files describing the extended relationship of the object, screening the extended relationship; splitting the set of business objects with extended relationship and the set of business objects without extended relationship;

[0032] S4, do not do any processing on the set of business objects without extended relationship; merge and remove duplicate attribute definitions on the set of business objects with extended relationship, and then go to step S5;

[0033] S5. Output the complete definition of the business object.

[0034] The step S1 is specifically as follows: the business basic module and the business extension module are abstractly designed in the same middle platform field, and all business extension modules are extended based on the business basic module in the same middle platform field, so as to ensure the independence of the business extension module and flexibly assemble and quickly respond to changing business demands; at the same time, multiple business extension modules are designed and developed in parallel and independently to improve the timeliness of business design;

[0035] Furthermore, the business objects in the same middle platform domain are abstracted into business basic objects and business extension objects. All business extension objects directly inherit the business basic objects of the business basic module. Therefore, the attributes extended by the business objects between all business extension modules are allowed to be redundantly defined, so that the flexible assembly process of multiple business extension modules can ensure that the attributes contained in the business objects can meet the business requirements.

[0036] In this way, a flat multi-module middle-end domain object design is constructed.

[0037] The step S2 is specifically as follows: scanning the business module package of the flattened multi-module middle platform domain object design that the current application relies on, the business module package including the business basic module and the business extension module; scanning the business object set of the flattened multi-module middle platform domain object design one by one according to the business module dependency relationship, the business object set including the business basic object and the business extension object;

[0038] According to the naming rules of business objects and the inheritance relationship declared in the business object class definition, the extension relationship between the business basic object and the business extension object is parsed, and the business basic object class name is used as the KEY of the MAP set. The corresponding business extension object class is combined in a linked list as the VALUE of the MAP. This memory MAP structure output describes the object extension relationship MAP set.

[0039] In step S4, the merging and deduplication of attributes are specifically defined as follows: code parsing is performed on a set of business objects with extended relationships to extract all business attributes of each business object; type conflicts of business attributes with the same name are resolved according to their maximum compatibility, and then deduplication is performed based on the attributes with the same name; after all sets of business objects with extended relationships are sorted out, a new set of ordered linked lists of business objects is output.

[0040] The step S5 is specifically as follows: for the new ordered linked list set of business objects, output the complete definition file of the business object that conforms to the syntax recognizable by the current computer language to the specified compilation path; remove the extended definition of the business object from the compiler context to ensure that there is only one complete business object definition file for compilation and operation for a business object.

[0041] Another object of the present invention is achieved by the following technical solutions:

[0042] A system for efficiently expanding the attributes of business objects in a multi-format middle platform includes a business object extraction module, a business object integration module, and a business object generation module; wherein,

[0043] The business object extraction module is used to scan and collect business object definitions, and to screen the extended relationships of business object definitions; to split the business object set with extended relationships and the business object set without extended relationships;

[0044] The business object integration module structures and optimizes the business attributes collected from a set of business objects with extended relationships according to the preset rule logic.

[0045] The business object generation module is used to generate target code that adapts to new business demands.

[0046] At the same time, the present invention provides:

[0047] A server comprises a processor and a memory, wherein the memory stores at least one program, and the program is loaded and executed by the processor to implement the method for efficiently expanding the business object attributes of the multi-format middle platform.

[0048] A computer-readable storage medium stores at least one program, which is loaded and executed by a processor to implement the method for efficiently expanding the business object attributes of the multi-format middle platform mentioned above.

[0049] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0050] 1. Construct a modular business attribute model: In the context of the profound needs of multi-format and complex business scenarios, the present invention carefully designs and implements a scalable business object attribute model based on the concept of microservice architecture. This model is like a precise clock component. Each business attribute is finely encapsulated as an independent service entity, and is accompanied by a dedicated data storage mechanism and a standardized service interface. In this way, when expanding new business attributes, it can not only ensure the smooth operation of existing business processes, but also ensure clear barriers between data and high flexibility of service calls.

[0051] 2. Flexible assembly and construction technology innovation: The present invention cleverly uses the art of flexible assembly and construction, making the business object attribute module like a plug-and-play Lego building block, which can be added, removed or updated as needed during compilation, to achieve on-demand business attribute expansion and adjustment. In the face of the need to add, modify or remove business attributes, you only need to adjust the current startup project dependency module to easily complete the deployment and update operations of the corresponding module, which undoubtedly greatly improves the efficiency of business changes and the ultra-high availability of the system.

[0052] 3. Intelligent construction system: The present invention has ingeniously created a complete and intelligent construction ecosystem, which mainly includes a business object extraction module, a business object integration module and a business object generation module. The business class extraction module is like a bee collecting honey, automatically identifying and extracting a set of business objects that need to be expanded in each business module; the business class integration module follows the preset rule logic to structure and optimize the collected business attributes; and the business object generation module is responsible for breeding target codes that adapt to new business demands, without directly touching the original code base, and without any performance loss in actual operation.

[0053] 4. Flat expansion strategy planning: The present invention further adopts a flat business attribute expansion design concept, so that the newly added business attributes can be integrated into the system level with extremely low coupling like water waves throwing stones, thereby effectively reducing the difficulty and potential risks of expansion, and greatly improving the resilience and expansion efficiency of the overall business middle platform.

[0054] 5. Dual considerations of consistency and performance optimization: While pursuing efficient expansion of business attributes, the present invention also attaches importance to data consistency and performance optimization of the system. The target operation package uses the compilation process to automatically merge and eliminate business objects, so that all business objects are running without sacrificing system performance, intuitiveness of data input and output, and consistency of the database. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 The present invention is a flowchart of a method for efficiently extending the attributes of business objects in a multi-format middle platform.

[0056] Figure 2 Schematic diagram of the flat multi-module design in the middle office field.

[0057] Figure 3 Schematic diagram of the design of flat multi-module business objects in the middle office field.

[0058] Figure 4 This is the rendering of the business objects after the flattened multi-module assembly and integration in the middle office field.

[0059] Figure 5 This is a schematic diagram of the design of a flat multi-module middle platform using a trading center as an example.

[0060] Figure 6 This is a schematic diagram of module combination example 1 - basic transaction + points transaction combination taking the trading center as an example.

[0061] Figure 7 This is a schematic diagram of module combination example 2 - basic transaction + B2C transaction combination taking the transaction center as an example.

[0062] Figure 8 This is a schematic diagram of module combination example 3 - basic transaction + point transaction + B2C transaction combination, taking the transaction center as an example.

[0063] Fig. 9 This is a schematic diagram of module combination example 4 - basic transaction + point transaction + B2C transaction + automobile industry characteristic transaction, taking the transaction center as an example.

[0064] Fig.10 A schematic diagram of the internal structure of the system for efficient expansion of business object attributes in the multi-format middle platform - intelligent construction. DETAILED DESCRIPTION

[0065] The present invention is further described in detail below in conjunction with embodiments and drawings, but the embodiments of the present invention are not limited thereto.

[0066] 1. Efficient expansion method of business objects in multiple business platforms (such as Figure 1 )The method comprises:

[0067] 1.1. Flat multi-module middle-end domain business object design.

[0068] 1.1.1. The same middle platform domain abstractly designs business basic modules and business extension modules, and all business extension modules are extended based on the same middle platform domain business basic modules, so as to ensure the independence of business extension modules and flexibly assemble them to quickly respond to changing business demands. At the same time, multiple business extension modules can be designed and developed in parallel and independently to improve the timeliness of business design.

[0069] 1.1.2. Furthermore, business objects in the same middle platform domain can also be abstracted into business basic objects and business extension objects. All business extension objects directly inherit the business basic objects of the business basic module. Therefore, the attributes extended by the business objects between all business extension modules are allowed to be defined redundantly, so that the flexible assembly process of multiple business extension modules can ensure that the attributes contained in the business objects can meet business needs.

[0070] 1.2. Scan and collect business object definitions.

[0071] 1.2.1. Scan the business module package designed in 1.1.1 that the current application depends on, and scan the business object set designed in 1.1.2 one by one according to the business module dependency relationship. The set includes business basic objects and business extension objects.

[0072] 1.2.2. According to the naming rules of business objects and the inheritance relationship declared in the business object class definition, the extension relationship between the business basic object and the business extension object is parsed, and the name of the business basic object class is used as the KEY of the MAP set. The corresponding business extension object class is combined in a linked list as the VALUE of the MAP. This memory MAP structure outputs the description of the object extension relationship MAP set.

[0073] 1.3. Perform business object definition extension relationship screening.

[0074] 1.3.1. Read the extended relationship MAP set of the description object output in 1.2.2 to perform extended relationship screening.

[0075] 1.3.2. Split out the MAP sets of business objects with extension relationship and business objects without extension relationship.

[0076] 1.4. Merge and remove duplicate attribute definitions.

[0077] 1.4.1. Split out the MAP set of business objects with extended relationships according to 1.3.2 for further code analysis. Based on the business attributes of the business basic objects and adding the extended attributes of other business extension modules, all the business attributes of each business object are extracted.

[0078] 1.4.2. Based on all the business attributes of each business object extracted in 1.4.1, first resolve type conflicts according to the attribute names and the maximum compatibility of the attributes with the same name, and then remove duplicates according to the attributes with the same name.

[0079] 1.4.3. Repeat 1.4.1 and 1.4.2 until all extended relationship business object sets are sorted out, and output a new business object ordered linked list set.

[0080] 1.5. Output the complete definition of the business object.

[0081] 1.5.1. Output a new ordered linked list of business objects according to 1.4.3 and output a complete definition file of the business object that conforms to the syntax that can be recognized by the current computer language to a specific compilation path.

[0082] 1.5.2. Remove the object's extended definition file from the compiler context to ensure that only one complete business object definition file exists for compilation and operation, thereby ensuring the accuracy of business input and output during operation.

[0083] 2. Intelligent construction system, which includes business object extraction module, business object integration module and business object generation module (such as Fig.10 ).

[0084] 2. The flat multi-module middle platform domain object design is as follows.

[0085] 1.1. In the same platform field, business basic modules and business extension modules are abstractly designed. Figure 2 As shown, all business extension modules are extended based on the same business basic module in the middle platform, so as to ensure the independence of business extension modules and flexibly assemble them to quickly respond to changing business demands. At the same time, multiple business extension modules can be designed and developed in parallel and independently, improving the timeliness of business design.

[0086] 1.2. Furthermore, the business objects in the same middle platform domain can also be abstracted into business basic objects and business extension objects, such as Figure 3 As shown, all business extension objects directly inherit the business basic object of the business basic module, so that the extended attributes of the business objects between all business extension modules are allowed to be redundantly defined, so that the flexible assembly process of multiple business extension modules can ensure that the attributes contained in the business objects can meet business needs.

[0087] 1.3. In the subsequent process of freely assembling business modules like building blocks according to different business requirements, the business object integration module of the business object efficient expansion system of the multi-business middle platform in this case integrates and processes the business objects with all business attributes required to meet the business requirements, such as Figure 4 shown.

[0088] 1.4. In order to deepen the understanding of the flat multi-module design that fits the actual business design and use, this case uses the order object design of the transaction center as an example to further illustrate. First, the attributes that the general basic transaction object should contain are abstracted. Secondly, according to the business expansion relationship and different business demands, the points transaction extension module, B2C transaction module, automobile industry transaction module, etc. are extracted. In this way, the design can be freely assembled like building blocks to build different transaction centers according to different business demands. Figures 5 to 9Of course, the construction of the middle platform is not as simple as this example. For example, 2B transactions, group purchase transactions, periodic purchase transactions, one-time transactions, pre-sale transactions, etc., all have different attribute extension demands for order information. However, no matter how complex the business demands are, they can be expanded and combined to meet the business demands by adding corresponding extension modules, such as 2B transaction module, group purchase transaction module, periodic purchase transaction module, one-time transaction module, and pre-sale transaction module.

[0089] 2. The system for efficiently expanding the business object attributes of the multi-format middle platform includes a business object extraction module, a business object integration module, and a business object generation module. After processing by these modules, the output is a business object definition that meets the current business demands, so as to easily cope with the diverse demands of adding, adjusting, and even removing new business attributes. It can quickly respond to market changes, strongly support and enable diversified business scenarios, and show a dynamically balanced and vibrant operating situation.

[0090] 2.1. Business object extraction module. This module has two responsibilities: scanning and collecting object definitions and screening business object definition extension relationships. It is like a bee collecting honey. First, it screens out the scope that needs to be scanned based on the associated modules and module dependencies declared in the business center startup project. Secondly, all business objects scattered in each business module are extracted one by one according to the scanning scope and extension relationship. Then, according to the name definition rules and extension relationships of the business basic objects and business extension objects, the business object sets that do not need to be expanded and the business object sets that need to be expanded in each business module are automatically identified and extracted. Each business object in the business object set that needs to be expanded is based on the attribute set of the business basic object, and the attributes of the business extension object are added to it, and its source is identified. The specific implementation steps are as follows:

[0091] 2.1.1. Scan and collect object definitions.

[0092] 2.1.1.1. Scan the business module package designed in 1.1.1 that the current application depends on, and scan the business object set designed in 1.1.2 one by one according to the business module dependency relationship. The set includes business basic objects and business extension objects.

[0093] 2.1.1.2. According to the naming rules of business objects and the inheritance relationship declared in the business object class definition, the extension relationship between the business basic object and the business extension object is parsed, and the name of the business basic object class is used as the KEY of the MAP set. The corresponding business extension object class is combined in a linked list as the VALUE of the MAP. This memory MAP structure outputs the description of the object extension relationship MAP set.

[0094] 2.1.2. Define the extended relationship of business objects to screen the business object sets that do not need to be extended and the business object sets that need to be extended urgently.

[0095] 2.1.2.1. Read the extended relationship MAP set of the description object output in 2.1.1.2 to perform extended relationship screening.

[0096] 2.1.2.2. Split out the business object set that does not need to be expanded and the business object set that urgently needs to be expanded into a MAP set.

[0097] 2.2. The business object integration module extracts the object set to be expanded based on the business extraction module in 2.1, follows the preset rule logic, and performs structured sorting and optimization on the collected business attributes to reorganize the business objects with all the business attributes required to meet the business requirements, such as Figure 4 Through the integration capabilities of this module, the expansion of business object attributes can be quickly solved, which subverts the time-consuming and technical risk dilemma of relying on deep customization and large-scale reconstruction models in the past, and easily copes with the diverse needs of adding, adjusting and even removing new business attributes. The specific implementation steps are as follows:

[0098] 2.2.1. According to 2.1.2.2, the MAP set of business objects with extended relationships is split out for further code analysis. Based on the business attributes of the business basic objects and the extended attributes of other business extension modules, all business attributes of each business object are extracted.

[0099] 2.2.2. According to all the business attributes of each business object extracted in 2.2.1, first resolve type conflicts according to the attribute names and the maximum compatibility of the attributes with the same name, and then remove duplicates according to the attributes with the same name.

[0100] 2.2.3. Repeat 2.2.1 and 2.2.2 until all extended relationship business object sets are sorted out, and output a new business object ordered linked list set.

[0101] 2.3. The business object generation module is responsible for generating target code that adapts to new business demands according to the integration structure in 2.2, without directly touching the original code base, and without any performance loss in actual operation. In order to avoid interference from intermediate objects and unnecessary object definition loading, this module will automatically remove intermediate business objects such as Figure 2 As shown in the figure, XX business extension object A (XxAExt), XX business extension object B (XxBExt), XX business extension object C (XxBExt), etc., only the XX business object with the same name as the business basic object is retained in the final system. Figure 4 The specific implementation steps are as follows:

[0102] 2.3.1. Output a new ordered linked list of business objects according to 2.2.3 and output a complete definition file of the business object that conforms to the syntax that can be recognized by the current computer language to a specific compilation path.

[0103] 2.3.2. Remove the object's extended definition file from the compiler context to ensure that only one complete business object definition file exists for compilation and operation, thereby ensuring the accuracy of business input and output during operation.

[0104] At the same time, the present invention provides:

[0105] A server comprises a processor and a memory, wherein the memory stores at least one program, and the program is loaded and executed by the processor to implement the method for efficiently expanding the business object attributes of the multi-format middle platform.

[0106] A computer-readable storage medium stores at least one program, which is loaded and executed by a processor to implement the method for efficiently expanding the business object attributes of the multi-format middle platform mentioned above.

[0107] This solution overturns the time-consuming and technical risk dilemmas of relying on deep customization and large-scale reconstruction models in the past. It cleverly uses the modular disassembly and component-based reorganization thinking of business object attributes, supplemented by a flat expansion design method, and integrates the intelligent core of flexible loading and construction mechanisms. The middle-office system can maintain the stable operation of existing businesses while easily responding to the diverse needs of adding, adjusting and even eliminating new business attributes. It can quickly respond to market changes, strongly support and enable diversified business scenarios, and show a dynamically balanced and vibrant operating situation.

[0108] Compared with metadata-driven design, the present invention adopts flat development design and flexible assembly construction mode. The business object attribute expansion has been completed in the static compilation process, so as to completely output the business object class definition of all business attributes required by the current business. The business objects at runtime can directly use it for data storage and output display, without relying on metadata for secondary conversion of its description. Metadata management and update will not cause data consistency problems and dependence on metadata may cause query performance degradation, thereby solving the problems of data consistency and query performance degradation.

[0109] Compared with the attribute plug-in design, the present invention adopts flat development design and flexible assembly construction mode, and has completed the business object attribute extension in the static compilation process. The class definition of the output business object only has business attributes and methods for operating business attributes, and all business attributes can be directly operated at runtime, without the need for additional plug-ins for conversion processing, so there is no plug-in management and maintenance problem at runtime. Attribute extension will not only not increase the additional cost of overall system monitoring and operation and maintenance, but also is intuitive and controllable for development and operation and maintenance personnel.

[0110] Compared with the flexible data table structure design (EAV or JSON field), the present invention adopts flat development design and flexible assembly construction mode. The business object attribute expansion has been completed in the static compilation process. All attributes of the business object can be directly mapped to the relational database at runtime. There is no need to rely on database storage with a special structure. The read and write logic fully complies with the relational database storage and query method, which will not cause problems such as database consistency and decreased query efficiency.

[0111] The above embodiments are preferred implementation modes of the present invention, but the implementation modes of the present invention are not limited to the above embodiments. Any other changes, modifications, substitutions, combinations, and simplifications that do not deviate from the spirit and principles of the present invention should be equivalent replacement methods and are included in the protection scope of the present invention.

Claims

1. A method for efficiently extending the business object attributes of a multi-format middle platform, characterized in that: The following steps are involved: S1. Build a flat multi-module middle platform domain object design; S2, scanning and collecting business object definitions based on dependencies; S3, screening the extended relationship of business object definition: reading the set of files describing the extended relationship of the object, and screening the extended relationship; Split into a set of business objects with extension relationship and a set of business objects without extension relationship; S4, do not do any processing on the set of business objects without extended relationship; merge and remove duplicate attribute definitions on the set of business objects with extended relationship, and then go to step S5; S5. Output the complete definition of the business object.

2. The method for efficiently expanding the business object attributes of the multi-format middle platform according to claim 1 is characterized in that: The step S1 is specifically as follows: the business basic module and the business extension module are abstractly designed in the same middle platform field, and all business extension modules are extended based on the business basic module in the same middle platform field, so as to ensure the independence of the business extension module and flexibly assemble and quickly respond to changing business demands; at the same time, multiple business extension modules are designed and developed in parallel and independently to improve the timeliness of business design; Furthermore, the business objects in the same middle platform domain are abstracted into business basic objects and business extension objects. All business extension objects directly inherit the business basic objects of the business basic module. Therefore, the attributes extended by the business objects between all business extension modules are allowed to be redundantly defined, so that the flexible assembly process of multiple business extension modules can ensure that the attributes contained in the business objects can meet the business requirements. In this way, a flat multi-module middle-end domain object design is constructed.

3. The method for efficiently expanding the business object attributes of the multi-format middle platform according to claim 1 is characterized in that: The step S2 is specifically as follows: scanning the business module package of the flattened multi-module middle platform domain object design that the current application relies on, the business module package including the business basic module and the business extension module; scanning the business object set of the flattened multi-module middle platform domain object design one by one according to the business module dependency relationship, the business object set including the business basic object and the business extension object; According to the naming rules of business objects and the inheritance relationship declared in the business object class definition, the extension relationship between the business basic object and the business extension object is parsed, and the business basic object class name is used as the KEY of the MAP set. The corresponding business extension object class is combined in a linked list as the VALUE of the MAP. This memory MAP structure output describes the object extension relationship MAP set.

4. The method for efficiently expanding the business object attributes of the multi-format middle platform according to claim 1 is characterized in that: In step S4, the merging and deduplication of attributes are specifically defined as follows: code parsing is performed on a set of business objects with extended relationships to extract all business attributes of each business object; type conflicts of business attributes with the same name are resolved according to their maximum compatibility, and then deduplication is performed based on the attributes with the same name; after all sets of business objects with extended relationships are sorted out, a new set of ordered linked lists of business objects is output.

5. According to claim 1, the method for efficiently expanding the business object attributes of the multi-format middle platform is characterized in that: The step S5 is specifically as follows: for the new ordered linked list set of business objects, output the complete definition file of the business object that conforms to the syntax recognizable by the current computer language to the specified compilation path; remove the extended definition of the business object from the compiler context to ensure that there is only one complete business object definition file for compilation and operation for a business object.

6. A system for efficiently expanding the business object attributes of a multi-format middle platform, characterized in that: It includes a business object extraction module, a business object integration module and a business object generation module; wherein, The business object extraction module is used to scan and collect business object definitions, and to screen the extended relationships of business object definitions; to split the business object set with extended relationships and the business object set without extended relationships; The business object integration module structures and optimizes the business attributes collected from a set of business objects with extended relationships according to the preset rule logic. The business object generation module is used to generate target code that adapts to new business demands.

7. A server, comprising a processor and a memory, characterized in that: At least one program is stored in the memory, and the program is loaded and executed by the processor to implement the method for efficiently expanding the business object attributes of the multi-format middle platform described in any one of claims 1 to 5.

8. A computer-readable storage medium, wherein at least one program is stored in the storage medium, characterized in that: The program is loaded and executed by the processor to implement the method for efficiently expanding the business object attributes of the multi-format middle platform described in any one of claims 1 to 5.

Images