A method and system for efficient extension of business object attributes of a multi-format middle platform

Abstract

The application discloses a kind of multi-industry mode middle station's business object attribute efficient extension method and system, the method includes the following steps: constructing flat multi-module middle station field object design;Based on dependency relationship scanning and collecting business object definition;Read the object expansion relationship file set, and carry out expansion relationship screening;Split out the business object set with expansion relationship and the business object set without expansion relationship, merge and remove attribute definition to the former, then output business object complete definition, do not handle the latter.This application combines the modularization of business object attribute disintegration, componentization reorganization thinking and flat expansion design method, so that the middle station system can easily cope with the multiple needs of new business attribute addition, adjustment and even elimination, so as to quickly respond to market changes, effectively support and empower diversified business scenarios.

Description

Technical Field

[0001] This invention relates to the field of business middleware, and in particular to a method and system for efficiently extending the attributes of business objects in a multi-business middleware. Background Technology

[0002] In a rapidly changing business environment, the business middle platform acts as the central nervous system of an enterprise, deeply extracting the common needs of various business lines and steadily accumulating core business capabilities through shared services. Faced with rapidly changing business demands and the challenges of emerging business scenarios, the middle platform needs an efficient and agile response mechanism to freely add or reconstruct the attributes of business objects without undermining the rock-solid stability and superior performance of existing systems.

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

[0004] To address the above issues, the common solutions for extending business attributes are as follows:

[0005] 1. Metadata-driven design:

[0006] By leveraging a metadata-driven design pattern, business attributes are stored in the form of metadata. Additional attributes for each business entity can be dynamically defined and managed through metadata. This way, when adding new business attributes, there is no need to modify the core code; only the relevant metadata needs to be updated.

[0007] The advantages of this solution are: high flexibility, easy dynamic management of business attributes, no need for frequent modification of core code, and conducive to agile iteration.

[0008] The drawbacks of this approach are that improper metadata management and updates may lead to data consistency issues, and excessive reliance on metadata may result in decreased query performance.

[0009] 2. Attribute plug-in design:

[0010] The design includes an attribute plugin module that provides independent attribute packages for different business formats or scenarios. When a new business format is added or an existing business format needs to expand its attributes, the corresponding attribute plugin can be developed and loaded, thereby enabling hot-swapping and dynamic expansion of business attributes.

[0011] The following is a detailed design scheme for extending business object attributes based on Java's attribute plug-in design:

[0012] Define the base interface and abstract class: Create an AttributePlugin interface or abstract class, which specifies the methods that all attribute plugins need to implement, such as getValue() to get the attribute value, setValue() to set the attribute value, etc.

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

[0014] Business object extension design: Business objects (such as Order) should contain a plugin container to store all the property plugins loaded by it. Methods for adding, removing, and retrieving plugins by name should also be provided.

[0015] Example of use: Dynamically add new attribute plugins to order objects at runtime based on requirements.

[0016] The advantages of this solution are: modularity and strong scalability. New functions or attributes can be implemented by loading plugins without affecting the operation of the original system.

[0017] The drawbacks of this solution are: plugin management and maintenance is a challenge, requiring the guarantee of compatibility and stability between plugins, and placing high demands on the overall monitoring and operation and maintenance of the system.

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

[0019] In database design, the use of EAV (Entity-Attribute-Value) model or semi-structured JSON fields allows for flexible storage of non-predefined attributes, ensuring that changes in business attributes do not lead to frequent changes in the database table structure.

[0020] 3.1 The EAV model allows entities to have a dynamic, unspecified number of attributes, each with a corresponding value. In traditional database design, each entity type typically corresponds to a fixed table, where columns represent predefined attributes. In the EAV model, entity attributes and their corresponding values ​​are stored in separate tables. For example, for a user object, basic information can be stored in an order table, while dynamic or unspecified attributes are stored in two other tables: `entity_attributes` (storing attribute names) and `attribute_values` (storing attribute values ​​associated with entity IDs). Thus, when a new attribute needs to be added, simply insert the new attribute record into the `entity_attributes` table and add the corresponding attribute value to each entity in the `attribute_values` table.

[0021] 3.2 JSON Fields: Use JSON type fields supported by relational databases (such as the JSON type in MySQL, the jsonb type in PostgreSQL, etc.) to store all additional, non-fixed attributes as JSON objects in a single field. This way, when attributes need to be expanded, there's no need to modify the table structure; simply add key-value pairs directly within the JSON object.

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

[0023] The advantages of this solution are: it is highly adaptable to data storage with non-fixed structures, and it is easy to add and change new attributes.

[0024] The drawback of this approach is that it sacrifices database consistency and query efficiency, especially when using the EAV schema extensively or handling complex queries, where performance may be inferior to traditional relational databases. Summary of the Invention

[0025] The purpose of this invention is to overcome the shortcomings and deficiencies of the prior art and provide a method for efficiently extending the attributes of business objects in a multi-business platform, aiming to achieve flexible extension and intelligent optimization of business object attributes.

[0026] Another objective of this invention is to provide a system for efficiently expanding the attributes of business objects in a multi-business middleware platform.

[0027] The objective of this invention is achieved through the following technical solution:

[0028] A method for efficiently extending the attributes of business objects in a multi-business middleware platform includes the following steps:

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

[0030] S2. Scan and collect business object definitions based on dependency relationships;

[0031] S3. Perform business object definition extension relationship filtering: Read the set of description object extension relationship files and perform extension relationship filtering; split into a set of business objects with extension relationships and a set of business objects without extension relationships;

[0032] S4. For a collection of business objects with no extended relationship, no processing is performed; for a collection of business objects with extended relationship, merge and deduplicate attribute definitions, then proceed to step S5.

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

[0034] Step S1 specifically involves: abstracting and designing a business base module and a business extension module within the same middleware domain, and extending all business extension modules based on the business base module within the same middleware domain, thereby ensuring the independence of the business extension modules and enabling flexible assembly to quickly respond to changing business demands; at the same time, multiple business extension modules are designed and developed in parallel and independently, improving the timeliness of business design.

[0035] Furthermore, business objects within the same middleware domain are abstracted into basic business objects and extended business objects. All extended business objects directly inherit from the basic business objects of the basic business modules. As a result, the attributes extended by the business objects between all extended business modules are allowed to be redundantly defined, ensuring that the flexible assembly process of multiple extended business modules can guarantee that the attributes contained in the business objects can meet business requirements.

[0036] This led to the development of a flat, multi-module middleware domain object design.

[0037] Step S2 specifically involves: scanning the business module package of the flattened multi-module middle platform domain object design that the current application depends on, where the business module package includes basic business modules and business extension modules; and scanning the set of business objects of the flattened multi-module middle platform domain object design one by one according to the business module dependency relationship, where the set of business objects includes basic business objects and business extension objects.

[0038] Based on the naming rules of business objects and the inheritance relationship of business object class definitions, the extension relationship between basic business objects and extended business objects is parsed out. Then, using the name of the basic business object class as the key of the MAP set, and combining its corresponding extended business object classes into a linked list to form the MAP value, this in-memory MAP structure is output to describe the object extension relationship MAP set.

[0039] In step S4, the merging and deduplication attribute definition specifically involves: parsing the code of the set of business objects with extended relationships to extract all business attributes of each business object; resolving type conflicts of business attributes with the same name according to their maximum type compatibility, and then deduplicating them according to the same-name attributes; after all the sets of business objects with extended relationships are sorted out, a new ordered linked list set of business objects is output.

[0040] Step S5 specifically involves: for the new ordered linked list of business objects, outputting the complete definition file of the business object that conforms to the syntax that the current computer language can recognize to the specified compilation path; removing the extended definition of the business object from the compiler context to ensure that only one complete business object definition file exists for each business object to participate in compilation and execution.

[0041] Another objective of this invention is achieved through the following technical solution:

[0042] A system for efficiently extending the attributes of business objects in a multi-business middleware 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 filter business object definition extension relationships; it separates the business object sets with extension relationships into sets of business objects without extension relationships.

[0044] The business object integration module, for a set of business objects with extended relationships, follows preset rules and logic to structure, organize, optimize, and reorganize the collected business attributes.

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

[0046] Meanwhile, this invention provides:

[0047] A server includes a processor and a memory, the memory storing at least one program, which is loaded and executed by the processor to achieve the method for efficiently expanding the business object attributes of the aforementioned multi-business platform.

[0048] A computer-readable storage medium storing at least one program, which is loaded and executed by a processor to achieve a method for efficiently expanding the business object attributes of the aforementioned multi-business platform.

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

[0050] 1. Constructing a Modular Business Attribute Model: Given the profound needs of diverse and complex business scenarios, this invention meticulously designs and implements a scalable business object attribute model based on microservice architecture principles. This model, like a precise clockwork component, meticulously encapsulates each business attribute as an independent service entity, accompanied by a dedicated data storage mechanism and standardized service interfaces. In this way, when expanding new business attributes, it ensures the seamless operation of existing business processes while maintaining clear data separation and highly flexible service calls.

[0051] 2. Innovative Flexible Assembly and Construction Technology: This invention cleverly utilizes the art of flexible assembly and construction, making business object attribute modules like plug-and-play Lego bricks. They can be added, removed, or updated as needed during compilation, enabling on-demand expansion and adjustment of business attributes. When faced with the need to add, modify, or remove business attributes, only the dependent modules of the current startup project need to be adjusted to smoothly complete the deployment and update operations of the corresponding modules. This undoubtedly greatly improves the efficiency of business changes and the system's ultra-high availability.

[0052] 3. Intelligent Build System: This invention meticulously crafts a complete and intelligent build ecosystem, which mainly includes a business object extraction module, a business object integration module, and a business object generation module. The business object extraction module, like a bee collecting nectar, automatically identifies and extracts the set of business objects that urgently need expansion from each business module; the business object integration module follows preset rules and logic to structure, organize, and optimize the collected business attributes; and the business object generation module is responsible for generating target code that adapts to new business requirements, without directly touching the original codebase and without incurring any performance loss during actual operation.

[0053] 4. Flattened Expansion Strategy: This invention further adopts a flattened business attribute expansion design concept, which allows newly added business attributes to be integrated into the system hierarchy with extremely low coupling, just like ripples on water. This effectively reduces the difficulty and potential risks of expansion, and greatly enhances the overall business platform's responsiveness and expansion efficiency.

[0054] 5. Dual Considerations for Consistency and Performance Optimization: While pursuing efficient expansion of business attributes, this invention also emphasizes system data consistency and performance optimization. The target runtime package uses the compilation process to automatically merge and remove business objects, ensuring that all business objects do not sacrifice system performance, the intuitiveness of data input and output, or database consistency during runtime. Attached Figure Description

[0055] Figure 1 This is a flowchart illustrating a method for efficiently extending the attributes of business objects in a multi-business middleware platform.

[0056] Figure 2 A schematic diagram of a flat, multi-module design for the middleware platform.

[0057] Figure 3 A schematic diagram of a flattened, multi-module business object design for the middle platform domain.

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

[0059] Figure 5 This is a schematic diagram illustrating the design of a flat, multi-module middleware platform, taking 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 transaction 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 + points transaction + B2C transaction combination, taking the transaction center as an example.

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

[0064] Figure 10 A schematic diagram of the internal structure of a multi-business middle platform for efficiently expanding the attributes of business objects and intelligently constructing the system. Detailed Implementation

[0065] The present invention will be further described in detail below with reference to the embodiments and accompanying drawings, but the embodiments of the present invention are not limited thereto.

[0066] I. Efficient methods for extending business objects in a multi-business middle platform (e.g.) Figure 1 The method includes:

[0067] 1.1 Design of business objects in a flat, multi-module middle platform.

[0068] 1.1.1 Business foundation modules and business extension modules are abstracted and designed within the same middleware domain. All business extension modules are based on the same middleware domain's business foundation modules, ensuring their independence and enabling flexible assembly for rapid response to changing business demands. Simultaneously, multiple business extension modules can be designed and developed in parallel and independently, improving the timeliness of business design.

[0069] 1.1.2 Furthermore, business objects within the same middleware domain can also be abstracted into basic business objects and extended business objects. All extended business objects directly inherit from the basic business objects of the basic business modules. As a result, the attributes extended by the business objects between all extended business modules are allowed to be redundantly defined, ensuring that the flexible assembly process of multiple extended business modules can guarantee that the attributes contained in the business objects can meet the business requirements.

[0070] 1.2 Scan and collect business object definitions.

[0071] 1.2.1 Scan the business module packages designed in 1.1.1 that the current application depends on, and scan the set of business objects designed in 1.1.2 one by one according to the business module dependency relationship. This set includes basic business objects and extended business objects.

[0072] 1.2.2 Based on the naming rules of business objects and the inheritance relationship of business object class definitions, the extension relationship between basic business objects and extended business objects is parsed out. The MAP set describing the extension relationship is output as a memory MAP structure, which uses the name of the basic business object class as the key and the corresponding extended business object classes as linked lists to form the MAP value.

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

[0074] 1.3.1 Read the MAP set of extended relationships of the output description object in 1.2.2 and filter the extended relationships.

[0075] 1.3.2. Separate the business objects with extended relationships and the business objects without extended relationships into MAP sets.

[0076] 1.4. Definition of merging and deduplication attributes.

[0077] 1.4.1 Based on 1.3.2, further code analysis is performed on the MAP collection of business objects with extended relationships. Taking the business attributes of the basic business objects as the basis and adding the extended attributes of other business extension modules, all business attributes of each business object are extracted.

[0078] 1.4.2 Based on all business attributes extracted from each business object in 1.4.1, first resolve type conflicts by maximizing type compatibility for attributes with the same name, and then deduplicate attributes with the same name.

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

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

[0081] 1.5.1. According to 1.4.3, output a new ordered linked list of business objects and output the complete definition file of the business objects that conforms to the syntax that the current computer language can recognize to a specific compilation path.

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

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

[0084] II. The specific design of the flattened multi-module middle platform domain object is shown below.

[0085] 1.1 Within the same middleware platform domain, basic business modules and extended business modules are abstractly designed, such as... Figure 2 As shown, all business extension modules are based on the same middleware business foundation module, thus ensuring the independence of the business extension modules and enabling flexible assembly 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, business objects within the same middleware domain can also be abstracted into basic business objects and extended business objects, such as... Figure 3 As shown, all business extension objects directly inherit from the business base object of the business base module. Therefore, the extended attributes of the business objects between all business extension modules can be redundantly defined, which ensures that the attributes contained in the business objects can meet the business requirements during the flexible assembly process of multiple business extension modules.

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

[0088] 1.4 To further illustrate the practical application of flat, multi-module design in business scenarios, this case study uses the order object design of a transaction center as an example. First, the attributes that a common basic transaction object should contain are abstracted. Then, based on business expansion relationships and different business needs, extension modules such as points transactions, B2C transactions, and automotive industry transactions are extracted. This design allows for the flexible assembly and construction of different transaction centers, much like building blocks, according to different business requirements. Figures 5 to 9Of course, the construction of a middle platform is not limited to such a simple example. For example, B2B transactions, group buying transactions, periodic purchase transactions, inventory transactions, pre-sale transactions, etc., all have different requirements for extending order information attributes. However, no matter how complex the business requirements are, they can be extended and combined by adding corresponding extension modules, such as B2B transaction modules, group buying transaction modules, periodic purchase transaction modules, inventory transaction modules, and pre-sale transaction modules, to meet the business requirements.

[0089] 2. The system for efficiently expanding the attributes of business objects in a multi-business 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 system outputs business object definitions that meet the current business requirements, thus easily handling the diverse needs such as adding, adjusting, and even removing new business attributes. This enables the system to quickly respond to market changes, effectively support and empower diverse business scenarios, and demonstrate a dynamic, balanced, and vibrant operating trend.

[0090] 2.1 Business Object Extraction Module: This module has two responsibilities: scanning and collecting object definitions and filtering business object definition extension relationships. Like a bee collecting nectar, it first filters the scanning scope based on the associated modules and dependencies declared in the business center's startup project. Then, based on the scanning scope and extension relationships, it extracts all business objects scattered across various business modules. Next, according to the naming rules and extension relationships of basic business objects and extended business objects, it automatically identifies and extracts the sets of business objects that do not need expansion and the sets of business objects that urgently need expansion from each business module. Each business object in the set of objects urgently needing expansion is based on the attribute set of the basic business object, with the attributes of the extended business object added and its source identified. The specific implementation steps are as follows:

[0091] 2.1.1 Definition of scanning and collecting objects.

[0092] 2.1.1.1 Scan the business module packages designed in 1.1.1 that the current application depends on, and scan the set of business objects designed in 1.1.2 one by one according to the business module dependency relationship. This set includes basic business objects and extended business objects.

[0093] 2.1.1.2. Based on the naming rules of business objects and the inheritance relationship of business object class definitions, the extension relationship between basic business objects and extended business objects is parsed out. The MAP set describing the extension relationship is output as a memory MAP structure, which uses the name of the basic business object class as the key and the corresponding extended business object classes as linked lists to form the MAP value.

[0094] 2.1.2 Filter the set of business objects that do not need to be extended and the set of business objects that urgently need to be extended by defining and extending the business object definition relationship.

[0095] 2.1.2.1 Read the MAP set of extended relationships of the output description object in 2.1.1.2 and filter the extended relationships.

[0096] 2.1.2.2 Separate the set of business objects that do not need to be expanded and the set of business objects that urgently need to be expanded, MAP set.

[0097] 2.2 The business object integration module, based on the business extraction module in 2.1, extracts the set of objects that urgently need expansion. Following preset rules and logic, it structurally organizes and optimizes the collected business attributes to generate business objects with all the necessary business attributes to meet business requirements, such as... Figure 4 This module's integration capabilities allow for the rapid resolution of business object attribute expansion, overturning the time-consuming and technically risky challenges of relying on deep customization and large-scale refactoring. It easily handles the diverse needs arising from the addition, adjustment, and even removal of new business attributes. The specific implementation steps are as follows:

[0098] 2.2.1. Based on 2.1.2.2, further code analysis is performed on the MAP collection of business objects with extension relationships. Taking the business attributes of the basic business object as the basis and adding the extension attributes of other business extension modules, all business attributes of each business object are extracted.

[0099] 2.2.2 Based on the business attributes extracted from each business object in 2.2.1, firstly, resolve type conflicts by maximizing type compatibility for attributes with the same name, and then deduplicate attributes with the same name.

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

[0101] 2.3 The business object generation module, based on the integration structure in rule 2.2, is responsible for generating target code that adapts to new business requirements. This process requires no direct modification to the original codebase and incurs no performance penalty during actual operation. To avoid interference from intermediate objects and unnecessary object definition loading, this module automatically removes intermediate business objects such as... Figure 2 The system shows XX business extension objects A (XxAExt), XX business extension object B (XxBExt), XX business extension object C (XxBExt), etc. Ultimately, only the XX business object with the same name as the basic business object is retained in the system. Figure 4 As shown. The specific implementation steps are as follows:

[0102] 2.3.1. Based on 2.2.3, output a new ordered linked list of business objects and output the complete definition file of the business objects that conforms to the syntax that the current computer language can recognize to a specific compilation path.

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

[0104] Meanwhile, this invention provides:

[0105] A server includes a processor and a memory, the memory storing at least one program, which is loaded and executed by the processor to achieve the method for efficiently expanding the business object attributes of the aforementioned multi-business platform.

[0106] A computer-readable storage medium storing at least one program, which is loaded and executed by a processor to achieve a method for efficiently expanding the business object attributes of the aforementioned multi-business platform.

[0107] This solution overturns the time consumption and technical risks inherent in previous models that relied on deep customization and large-scale reconstruction. It cleverly utilizes modular decomposition and component-based reorganization of business object attributes, supplemented by a flattened extension design method, and integrates a smart kernel with a flexible loading and building mechanism. This enables the middle platform system to maintain the stable operation of existing businesses while easily handling the diverse needs of adding, adjusting, and even removing new business attributes. As a result, it can quickly respond to market changes, effectively support and empower diverse business scenarios, and demonstrate a dynamic, balanced, and vibrant operating state.

[0108] Compared to metadata-driven design, this invention adopts a flat development design and flexible assembly construction mode. The business object attribute extension is completed during the static compilation process, thereby outputting the business object class definition with all the business attributes required by the current business. The business object at runtime can directly use it for data storage and output display without relying on metadata to perform secondary transformation on its description. Metadata management and updates will not cause data consistency problems or query performance degradation that may be caused by relying on metadata, thus solving the problems of data consistency and query performance degradation.

[0109] Compared to attribute-based plug-in design, this invention adopts a flat development design and a flexible assembly and construction model. Business object attribute extension is completed during the static compilation process. The output business object class definition only contains business attributes and methods for manipulating those attributes. Furthermore, all business attributes can be directly manipulated at runtime without requiring additional plug-ins for conversion processing. Therefore, there are no plug-in management and maintenance issues at runtime. Attribute extension not only does not increase the overall system monitoring and maintenance costs, but it is also intuitive and controllable for both developers and operations personnel.

[0110] Compared to flexible data table structure designs (EAV or JSON fields), this invention adopts a flat development design and flexible assembly construction mode. The business object attribute extension is completed during the static compilation process. At runtime, all attributes of the business object can be directly mapped to the relational database without relying on a special database storage structure. The read and write logic fully complies with the relational database storage and query methods, thus avoiding database consistency and query efficiency degradation issues.

[0111] The above embodiments are preferred embodiments of the present invention, but the embodiments of the present invention are not limited to the above embodiments. Any changes, modifications, substitutions, combinations, or simplifications made without departing from the spirit and principle of the present invention shall be considered equivalent substitutions and shall be included within the protection scope of the present invention.

Claims

1. A method for efficient extension of business object attributes of a multi-format middle platform, characterized in that, Comprise the following steps: S1, construct the flat multi-module middle platform field object design; Specifically: the same middle platform field abstractly designs business basic modules and business extension modules, and all business extension modules are extended based on the same middle platform field business basic module, thereby guaranteeing the independence of the business extension module, flexible assembly and rapid response to changing business demands; At the same time, multiple business extension modules are designed and developed in parallel and independently, improving the timeliness of business design; Further, the business objects of the same middle platform field are abstracted into business basic objects and business extension objects, and all business extension objects directly inherit the business basic objects of the business basic module, so that 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 guarantee that the attributes contained in the business objects can meet the business requirements; Thus, a flat multi-module middle platform field object design is constructed; S2, scan and collect business object definitions based on dependency relationships; S3, perform business object definition extension relationship screening: read the description object extension relationship file set, and perform extension relationship screening; Split the business object set with extension relationship and the business object set without extension relationship; S4, for the business object set without extension relationship, do not do any processing; for the business object set with extension relationship, merge and remove attribute definitions, and then go to step S5; The merging and removing attribute definitions are specifically: code analysis is performed on the business object set with extension relationship, and all business attributes of each business object are extracted; the same named business attributes are solved according to their type maximum compatibility to solve type conflict, and then the same named attributes are removed; after the business object set with extension relationship is completely sorted, a new business object ordered linked list set is outputted; S5, output the complete definition of the business object.

2. The method of claim 1, wherein the business object attribute is efficiently extended in the multi-format middle platform. The step S2 is specifically: scanning the business module package of the flat multi-module middle platform field object design depended by the current application, the business module package including business basic modules and business extension modules; scanning the business object set of the flat multi-module middle platform field object design according to the business module dependency relationship, the business object set including business basic objects and business extension objects; According to the naming rules of the business object and the inheritance relationship declared by the business object class definition, the extension relationship of the business basic object and the business extension object is parsed, and the business basic object class name is taken as the KEY of the MAP set, and the corresponding business extension object class is taken as the VALUE of the MAP set. This memory MAP structure is outputted to describe the object extension relationship MAP set.

3. The method of claim 1, wherein the method further comprises: The step S5 is specifically: for the new business object ordered linked list set, output the complete definition file of the business object conforming to the syntax recognizable by the current computer language to the specified compilation path; remove the extension definition of the business object from the compiler context, so that only one complete business object definition file exists for the final business object to participate in compilation and running.

4. A system for efficient extension of business object attributes of a multi-format middle platform, characterized in that, The method for realizing the efficient expansion of the business object attribute of the multi-format middle platform according to any one of claims 1 to 3 comprises a business object extraction module, a business object integration module and a business object generation module, wherein The business object extraction module is used for scanning and collecting business object definitions, and performing business object definition expansion relationship screening; and splitting out a business object set with expansion relationships and a business object set without expansion relationships; The business object integration module performs structural analysis and optimized recombination on the collected business attributes according to a preset rule logic for the business object set with expansion relationships; The business object generation module is used for generating target codes suitable for new business demands.

5. A server comprising a processor and a memory, wherein the server is configured to: The memory stores at least one program, which is loaded and executed by the processor to realize the efficient expansion of the business object attribute of the multi-format middle platform according to any one of claims 1 to 3.

6. A computer-readable storage medium having stored therein at least one segment of a program, characterized by The program is loaded and executed by the processor to realize the efficient expansion of the business object attribute of the multi-format middle platform according to any one of claims 1 to 3.

Images