CN117271641A - Data processing method, device and storage medium - Google Patents
Data processing method, device and storage medium Download PDFInfo
- Publication number
- CN117271641A CN117271641A CN202311281529.0A CN202311281529A CN117271641A CN 117271641 A CN117271641 A CN 117271641A CN 202311281529 A CN202311281529 A CN 202311281529A CN 117271641 A CN117271641 A CN 117271641A
- Authority
- CN
- China
- Prior art keywords
- data
- target
- object data
- domain
- models
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 13
- 238000000034 method Methods 0.000 claims abstract description 25
- 238000012545 processing Methods 0.000 claims abstract description 25
- 230000015654 memory Effects 0.000 claims description 17
- 230000002085 persistent effect Effects 0.000 claims description 3
- 230000006403 short-term memory Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 6
- 238000013499 data model Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000007405 data analysis Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/254—Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24564—Applying rules; Deductive queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a data processing method, a data processing device and a storage medium, which are used in the field of data processing. The method comprises the following steps: establishing a plurality of field models outside the data system; in a target field model corresponding to a target data system, determining the association relation between object data and other field models; and determining a configuration rule of the object data in the target domain model based on the association relation, and assigning entity metadata of different data systems to the object data of the target domain model based on the configuration rule. Entity metadata of different data systems can be uniformly converted into object data of a target field model through configuration rules, data sharing among different data systems can be achieved through the target field model without collecting a large amount of data of each data system, and cost of data sharing is effectively saved.
Description
Technical Field
The embodiment of the application relates to the technical field of data processing, in particular to a data processing method, a data processing device and a storage medium.
Background
In today's enterprises, more than one service, different services are provided with data by different data systems, different service data is typically stored in the respective data systems, and the service data of these data systems often have different data structures and formats. Entity metadata in a data system is often only used for the construction of the data system itself, is not universal with the outside of the data system, and cannot be used. Data between data systems becomes inconsistent, is difficult to coordinate and integrate, and may cause problems such as repeated data storage, data island and the like.
In order to realize data sharing among different data systems, the data of the data systems are collected into a data warehouse in a data integration mode, then are subjected to data analysis processing, and finally the general rule among the data of each data system is obtained, and the general rule is used for data sharing. However, to increase the accuracy of the generic rules, a large amount of data for each data system needs to be collected, greatly increasing the cost of data sharing.
Disclosure of Invention
The embodiment of the application provides a data processing method, a data processing device and a storage medium, which can effectively save the cost of data sharing.
The embodiment of the application provides a data processing method, which comprises the following steps:
establishing a plurality of field models outside the data system, wherein the field models are used for describing entities in the data system and object data corresponding to the entities;
in a target domain model corresponding to a target data system, determining the association relation between object data and other domain models, wherein the other domain models are domain models corresponding to other data systems outside the target data system;
and determining a configuration rule of the object data in the target domain model based on the association relation, and assigning entity metadata of different data systems to the object data of the target domain model based on the configuration rule.
Further, the building a plurality of domain models outside the data system includes:
determining whether an entity of the preset data system is associated with an entity of the other data system;
if yes, taking the entities of other data systems as object data corresponding to the entities of the preset data system, and building a domain model corresponding to the entities of the preset data system outside the data system.
Further, in the target domain model corresponding to the target data system, determining the association relationship between the object data and other domain models includes:
in a target domain model corresponding to the target data system, determining whether the object data is matched with the entities of other domain models;
if yes, determining that the object data references other field models, and taking the reference relationship as the association relationship.
Further, the determining the configuration rule of the object data in the target domain model based on the association relation includes:
if the object data in the target field model has an association relationship, setting a configuration rule of the object data as other field models associated with the calling object data;
and if the object data in the target domain model does not have the association relationship, setting a configuration rule of the object data based on entity metadata in a data system corresponding to the domain model.
Further, the assigning entity metadata of different data systems to the object data of the target domain model based on the configuration rule includes:
determining entity metadata associated with entities of the target domain model in different data systems;
determining target entity metadata which accords with a preset matching rule in the target field model in the associated entity metadata;
and assigning the target entity metadata to the object data of the target domain model based on the configuration rule.
Further, the method comprises the steps of:
acquiring a query request for querying object data corresponding to a target entity, and determining a preset domain model corresponding to the target entity and other domain models associated with the object data corresponding to the target entity;
inquiring data in a data system corresponding to the preset field model based on the inquiring condition of the inquiring request to obtain first data;
in the other related domain models, inquiring data in a data system corresponding to the other domain models based on the matching rule to obtain second data;
and assigning the first data and the second data to the object data of the preset domain model based on the configuration rule of the object data of the preset domain model, and returning the assigned object data.
Further, the method further comprises:
acquiring an update request of target object data corresponding to an update entity, and determining a preset domain model corresponding to the entity;
determining other field models associated with the target object data based on configuration rules corresponding to the target object data;
determining target entity metadata in a data system corresponding to other field models based on the matching rules of the preset field model and the matching rules of other field models;
and updating the object data corresponding to the target object data in the target entity metadata based on the update request.
The embodiment of the application also provides a data processing device, which comprises:
the system comprises a building unit, a data system and a storage unit, wherein the building unit is used for building a plurality of field models outside the data system, and the field models are used for describing entities in the data system and object data corresponding to the entities;
the determining unit is used for determining the association relation between the object data and other domain models in the target domain model corresponding to the target data system, wherein the other domain models are domain models corresponding to other data systems outside the target data system;
and the execution unit is used for determining a configuration rule of the object data in the target domain model based on the association relation and assigning data in different data systems to the object data of the target domain model based on the configuration rule.
The embodiment of the application also provides electronic equipment, which comprises:
a central processing unit, a memory and an input/output interface;
the memory is a short-term memory or a persistent memory;
the central processor is configured to communicate with the memory and to execute the instruction operations in the memory to perform the methods described above.
Embodiments also provide a computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform a method as described above.
From the above technical solutions, the embodiments of the present application have the following advantages:
in the embodiment of the application, a plurality of field models are built outside a data system; in a target field model corresponding to a target data system, determining the association relation between object data and other field models; and determining a configuration rule of the object data in the target domain model based on the association relation, and assigning entity metadata of different data systems to the object data of the target domain model based on the configuration rule. Entity metadata of different data systems can be uniformly converted into object data of a target field model through configuration rules, data sharing among different data systems can be achieved through the target field model without collecting a large amount of data of each data system, and cost of data sharing is effectively saved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to these drawings for a person having ordinary skill in the art.
FIG. 1 is a diagram of a communication network architecture of a data system disclosed in an embodiment of the present application;
FIG. 2 is a flow chart of a data process disclosed in an embodiment of the present application;
FIG. 3 is a flow chart of another data processing disclosed in an embodiment of the present application;
FIG. 4 is a schematic diagram of a domain model disclosed in an embodiment of the present application;
FIG. 5 is a schematic diagram illustrating assignment of a user domain model according to an embodiment of the present application;
FIG. 6 is a schematic diagram illustrating assignment of an order field model disclosed in an embodiment of the present application;
FIG. 7 is a schematic diagram of assignment of a product domain model according to an embodiment of the present application;
FIG. 8 is a schematic diagram illustrating assignment of a payment information domain model according to an embodiment of the present application;
FIG. 9 is a diagram of a data processing apparatus according to an embodiment of the present application;
fig. 10 is a schematic diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail with reference to the accompanying drawings, and the described embodiments should not be construed as limiting the present application, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In the following description, reference is made to "one embodiment" or "one specific example" and the like, which describe a subset of all possible embodiments, but it is to be understood that "one embodiment" or "one specific example" may be the same subset or a different subset of all possible embodiments and may be combined with each other without conflict. In the following description, the term plurality refers to at least two. Some value as referred to herein reaches a threshold value (if any), and in some specific examples may include the former being greater than the latter.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the present application.
For ease of understanding and description, application scenarios of the present application will be briefly described before further detailed description of embodiments of the present application.
As shown in fig. 1, the data processing apparatus 101 may acquire data from a plurality of data systems 102, collect the data of the data systems into a data warehouse, and then perform data analysis processing to obtain a general rule between the data of each data system, and use the general rule to perform data sharing. However, to increase the accuracy of the generic rules, a large amount of data for each data system needs to be collected, greatly increasing the cost of data sharing. Therefore, the embodiment of the application provides a data processing method, which can effectively save the cost of data sharing, as shown in fig. 2, specifically includes the following steps:
201. a plurality of domain models are built outside the data system.
The data processing apparatus may build a plurality of domain models outside the data system, the domain models describing entities in the data system and object data corresponding to the entities. The object data may be understood as an attribute corresponding to the target entity, that is, other entities forming the target entity, such as an entity included in the system a, are orders, where the orders are composed of payment information, user, product information, and the like, that is, the object data corresponding to the orders are payment information, user, product information, and the like. Corresponding domain models can be built outside a plurality of different data systems, which can be understood as heterogeneous systems, i.e. data in the data systems are not generic.
It will be appreciated that there are a plurality of entities in each data system, and that in general, each entity in the data system builds a corresponding domain model outside the data system. And the entity in the data system has corresponding entity metadata, the entity metadata can be understood to be a data model corresponding to the service data in the data system, and the entity metadata comprises the entity in the data system and the corresponding object data in the data system. It will be appreciated that the domain model corresponding to the entity is different from the entity metadata corresponding to the entity in the data system, and is used for description only and not for redevelopment of the data system. Entity metadata (data model) within the system is described outside of the data system by a domain model, without modification to the data system.
202. And determining the association relation between the object data and other field models in the target field model corresponding to the target data system.
After the domain model is built outside the data system, the association relation between the object data and other domain models can be determined in the target domain model corresponding to the target data system. The other domain models are domain models corresponding to other data systems except the target data system. That is, whether the object data in the target domain model corresponding to the target data system has an association relationship with other domain models is determined, and the association relationship may refer to other domain models or be converted from other domain models, which is not limited herein. If the domain model corresponding to the order in the system a contains the object data such as payment information, user information, product information, etc., and the user information is mainly located in the user of the system B, it can be determined that the domain model corresponding to the order is in the domain model corresponding to the order, and the user object data references the domain model corresponding to the user in the system B. And determining the association relation between the domain models corresponding to different data systems. It can be understood that the domain models can be used as nodes, and the association relations among the domain models can be used as edge relations, so that a topological relation diagram of the domain models can be formed.
It can be appreciated that the domain model and the association relationship can be optimized, for example, the repeated domain model can be removed or the unnecessary association relationship can be removed; if the domain model corresponding to the order in the system a contains the user, and the domain model corresponding to the user in the system a exists, but the main provider of the user information is the system B, only the domain model corresponding to the user in the system B can be reserved at this time, and the domain model corresponding to the user in the system a is removed.
203. And determining the configuration rule of the object data in the target field model based on the association relation.
After the association relation between the object data and other domain models is determined, the configuration rule of the object data in the target domain model can be determined based on the association relation. The configuration rule represents an assignment mode of the object data, and can determine that the configuration rule of the object data in the target field model is as follows: and referring to other domain models, or assigning corresponding object data in entity metadata corresponding to the domain models, where the entity metadata is entity metadata associated with entities of the domain models, and the entity metadata is not limited herein. And determining a domain model with an edge relation with the target domain model from the topological relation diagram corresponding to the domain model, and obtaining the configuration rule of the object data in the target domain model.
The configuration rules may be direct assignment, or through function assignment, or enumeration mapping assignment, and are not limited in this regard. The function formula comprises a function name, parameters and a return value, and when the object data in the target domain model is associated with the multiple domain model, the configuration rule of the object data can be set as a plurality of calling functions, and the plurality of calling functions are executed in sequence.
It will be appreciated that the object data contained in a domain model may be configured from one entity metadata of a data system; or the object data contained in a domain model needs to be configured from the entity metadata of different data systems, and the object data in the domain model can also be configured from the entity metadata of different data systems.
204. And assigning entity metadata of different data systems to the object data of the target domain model based on the configuration rules.
After the configuration rule of the object data in the domain model is determined, the entity metadata of different data systems can be assigned to the object data of the target domain model based on the configuration rule, namely, the entity metadata of different data systems are unified into the target domain model. The object data of the target domain model can be determined to be associated with other domain models, entity metadata of other data systems are assigned to the other domain models, and then the entity metadata of the other data systems are returned to the corresponding object data through logic processing such as data conversion and merging through the other domain models, so that the object data of the target domain model contains data of the other data systems. Entity metadata with the same business semantics in each data system is uniformly described through the target field model, and the relationship of the entity metadata of each data system is converted into an entity and a relationship under one field model, so that the entity and the relationship are easier to know; according to the target field model, the required data can be returned once without determining the data system in which the data is located.
In the embodiment of the application, a plurality of field models are established outside the data system; in a target field model corresponding to a target data system, determining the association relation between object data and other field models; and determining a configuration rule of the object data in the target domain model based on the association relation, and assigning entity metadata of different data systems to the object data of the target domain model based on the configuration rule. Entity metadata of different data systems can be uniformly converted into object data of a target field model through configuration rules, data sharing among different data systems can be achieved through the target field model without collecting a large amount of data of each data system, and cost of data sharing is effectively saved.
Further, the flow of data processing will be described in detail below, as shown in fig. 3, and specifically includes the following steps:
301. based on the associated entity, a domain model corresponding to the entity is established outside the data system.
In the embodiment of the application, when the domain model is built outside the data system, the domain model corresponding to the entity can be built outside the data system based on the associated entity. Specifically, whether the entity of the preset data system is associated with the entity of the other data system or not can be determined, if so, the entity of the other data system is used as object data corresponding to the entity of the preset data system, and a domain model corresponding to the entity of the preset data system is built outside the data system.
The entity of the preset data system is associated with the entity of the other data system, which can be understood that the object data corresponding to the entity of the preset data system is mainly provided by the other data system; if the user information corresponding to the order in the system a is mainly provided by the system B, it can be determined that the order of the system a is associated with the user information of the system B, and when the domain model corresponding to the order in the system a is built outside the system a, the user information can be used as object data in the domain model.
302. And determining the reference relation between the object data and other field models in the target field model corresponding to the target data system.
After the domain model is established, the reference relation between the object data and other domain models can be determined in the target domain model corresponding to the target data system. Specifically, whether the object data is matched with the entity of other domain models can be determined in the target domain model corresponding to the target data system; if yes, determining that the object data references other field models, and taking the reference relationship as an association relationship; i.e. determining other domain models referenced by the object data in the target domain model, i.e. the object data is mainly obtained by the other domain models.
As shown in fig. 4, the order orderball in the data system mainly comprises a User, commodity orderball product, payment information PayInfo and the like, and the corresponding specific data are provided by different data systems. The method can establish a field model corresponding to order OrderBill, a field model corresponding to User, a field model corresponding to commodity OrderProduct and a field model corresponding to payment information PayInfo outside the data system, wherein each field model corresponds to an entity in different data systems. At this time, the object data in the domain model corresponding to the order OrderBill may be determined: creator refers to the domain model corresponding to the User, and the object data: product products refers to a field model corresponding to commodity OrderProduct, and object data: the payment information payInfo refers to a domain model to which the payment information payInfo corresponds.
Other object data related to the order, such as order number billno and creation time createTime, are also included in the domain model corresponding to the order OrderBill, which is not limited herein. And the domain model corresponding to the User comprises object data related to the User, such as name, phone and the like; the field model corresponding to the commodity OrderProduct comprises object data related to the commodity, such as quantitative quality, unit price and the like; the domain model corresponding to the payment information PayInfo includes object data related to payment, such as a payment status payStatus, a payment time payTime, and the like.
303. And determining the configuration rule of the object data in the target field model based on the reference relation.
In the embodiment of the application, the configuration rule of the object data in the target field model is determined based on the reference relation, namely, the assignment rule of the object data in the target field model is determined. Specifically, if the object data in the target domain model has an association relationship (reference relationship), setting a configuration rule of the object data as other domain models associated with the call object data; i.e. the object data is assigned to the data returned by the other domain model to which the object data is associated. If the object data in the target field model does not have the association relationship, setting a configuration rule of the object data based on entity metadata in a data system corresponding to the target field model.
The configuration rule of the object data may be direct assignment, as shown in fig. 5, and the domain model corresponding to the User sets a data object assigned as the "src" original system in the field configuration, that is, directly assigns entity metadata to the corresponding object data. When the object data refers to other domain models, the configuration rule of the object data is a function for calling other neighborhood models, as shown in fig. 6, the domain model corresponding to the order OrderBill is set to be assigned as "find match (User, src. Create)" in the field configuration, that is, searching is performed according to the matching rule of the domain model corresponding to the User; setting a value as 'findMulti (OrderProduct)' in field configuration, namely searching a matched object in a field model corresponding to the OrderProduct according to the billno, and returning a plurality of objects; setting a value of 'findOne (Paylnfo,' paySerialNo ', src.paySerialNo)', searching a matched object in a field model corresponding to payment information Paylnfo according to paySerialNo, and returning to the first item. As in fig. 7: the domain model corresponding to OrderProduct, FIG. 8: the configuration rule of the object data may also be a calculation expression, or other assignment function, as shown in the field model corresponding to paynfo. Where "toUTC" represents the time of conversion to UTC format and "findMappingData" represents lookup mapping data.
304. And determining target entity metadata based on the entity association and the matching rule, and assigning the target entity metadata to the object data of the target domain model through the configuration rule.
After determining the configuration rule of the object data in the target domain model, the target entity metadata can be determined based on the entity association and the matching rule, and the target entity metadata is assigned to the object data of the target domain model through the configuration rule. In particular, entity metadata associated with entities of the target domain model may be determined in different data systems; i.e. the associated entity metadata is found by the entity association first. For example, the field model corresponding to the order is associated entity metadata corresponding to the order, and the entity metadata corresponding to the order is located in the data system for providing the order data.
It will be appreciated that the same entity in a data system may contain a plurality of entity metadata, each entity metadata containing object data with a certain distinction; the entity metadata corresponding to the order may be entity metadata of the order a, entity metadata of the order B or entity metadata of the order C, and the object data in the entity metadata of each order: there is a certain distinction between payment information, user, product information, etc. Therefore, it is necessary to determine target entity metadata conforming to a preset matching rule in the domain model from among the associated entity metadata. It may be understood that in each domain model, a corresponding matching rule may be set according to an entity corresponding to the domain model, for example, in the domain model corresponding to the order, the matching rule may be set to have the same order number, that is, "billno= src.billno", that is, when the order number in the associated entity metadata is the same as the order number of the domain model, the matching rule is preset in the domain model, and the matching rule is set to be the target entity metadata. It can be appreciated that one or more matching rules can be set for each domain model, and corresponding matching priorities can also be set when a plurality of matching rules are set.
After determining the target entity metadata conforming to the preset matching rule in the target domain model, the target entity metadata can be assigned to the object data of the target domain model based on the configuration rule. It may be understood that the object data of the target domain model may refer to other domain models, and the object data assigned by the other domain models may be obtained by calling a function and returned to the object data of the domain model. As shown in fig. 6, if the domain model corresponding to the User is referenced by the target data (target object field) creator in the domain model corresponding to the order bill, the data may be assigned to the target data corresponding to the domain model from the entity metadata b_user of the system B based on the matching rule in the domain model corresponding to the User, and then the value of the assigned target data is returned to the target data creator; correspondingly, the object data products can obtain entity metadata C_products in the system C; the object data payinfo can obtain entity metadata T_PayDetail in the system A; at this time, the domain model corresponding to the order OrderBill can unify entity metadata of a plurality of data systems.
305. Object data in a data system is processed based on a domain model.
After assigning values to the object data in the domain model, the object data in the data system may be processed based on the domain model. The access information of each different data system can be configured first, namely, the connection mode and the connection address of the source system are set. And accessing the data in different data systems through the access information, and processing the data.
In one implementation, the data may be queried according to a domain model, and the object data corresponding to the entity may be queried, for example, based on a query statement: findOne (domain model name, object data, matching value), which is the entity corresponding to the domain model. The object data can be searched based on the query statement, and the returned data format is the format of the domain model, so that the position of the source system, the access mode of the source system and the format of entity metadata in the source system are not required to be known.
Specifically, a query request for querying object data corresponding to a target entity can be obtained, and a preset domain model corresponding to the target entity and other domain models associated with the object data corresponding to the target entity are determined; inquiring data in a data system corresponding to a preset field model based on an inquiry condition of an inquiry request to obtain first data; in the other related domain models, inquiring data in a data system corresponding to the other domain models based on the matching rule to obtain second data; and assigning the first data and the second data to the object data of the preset domain model based on the configuration rule of the object data of the preset domain model, and returning the assigned object data.
If the order object data with the order number billno x is queried, the field model corresponding to the order can be queried according to the order number billno, and the order object data is associated with the field model corresponding to the user, the field model corresponding to the commodity and the field model corresponding to the payment information; at this time, the data of the data system corresponding to the domain model can be queried based on the condition order number billno as x and the matching rule in each domain model, and the data is returned to the order object data to obtain the query result.
In one embodiment, the data may also be updated as a domain model, and the object data in the data system may be modified. Specifically, an update request for updating target object data corresponding to an entity can be obtained, and a preset domain model corresponding to the entity is determined; determining other field models associated with the target object data based on configuration rules corresponding to the target object data; determining target entity metadata in a data system corresponding to other field models based on a matching rule of a preset field model and matching rules of other field models; and updating the object data corresponding to the target object data in the target entity metadata based on the update request.
If the number of the commodities in the updated order object data is n, the commodity field model associated with the commodities in the order field model can be determined, and based on the matching rule of the order field model and the matching rule of the commodity field model, if the query condition is that the order number billno is equal to the order number billno of the object data in the OrderBill order field model, and the number in the entity metadata corresponding to the commodities is equal to the number of the commodities, the corresponding entity metadata is found, and then the number of the commodities in the entity metadata is n.
Therefore, in the embodiment of the application, the data models of all the data systems from the domain model and the relation among the data models are facilitated by building the domain model outside the data systems, so that the service semantics are unified; the data island is eliminated, and data exchange, sharing and butt joint are implemented among the data systems.
The embodiment of the application also provides a data processing device, as shown in fig. 9, including:
the building unit 901 is configured to build a plurality of domain models outside the data system, where the domain models are used to describe entities in the data system and object data corresponding to the entities;
a determining unit 902, configured to determine, in a target domain model corresponding to a target data system, an association relationship between object data and other domain models, where the other domain models are domain models corresponding to other data systems outside the target data system;
the execution unit 903 is configured to determine a configuration rule of the object data in the target domain model based on the association relationship, and assign data in different data systems to the object data of the target domain model based on the configuration rule.
Further, the establishing unit 901 is specifically configured to determine whether an entity of the preset data system is associated with an entity of another data system;
if yes, taking the entities of other data systems as object data corresponding to the entities of the preset data system, and building a domain model corresponding to the entities of the preset data system outside the data system.
Further, the determining unit 902 is specifically configured to determine, in a target domain model corresponding to the target data system, whether the object data matches with an entity of another domain model;
if yes, determining that the object data references other field models, and taking the reference relationship as the association relationship.
Further, the execution unit 903 is specifically configured to set a configuration rule of the object data to invoke other domain models associated with the object data if the object data in the target domain model has an association relationship;
and if the object data in the target domain model does not have the association relationship, setting a configuration rule of the object data based on entity metadata in a data system corresponding to the domain model.
Further, the execution unit 903 is specifically configured to determine entity metadata associated with an entity of the target domain model in different data systems;
determining target entity metadata which accords with a preset matching rule in the target field model in the associated entity metadata;
and assigning the target entity metadata to the object data of the target domain model based on the configuration rule.
Further, the data processing apparatus further includes: the query unit is used for acquiring a query request for querying object data corresponding to a target entity, and determining a preset field model corresponding to the target entity and other field models associated with the object data corresponding to the target entity;
inquiring data in a data system corresponding to the preset field model based on the inquiring condition of the inquiring request to obtain first data;
in the other related domain models, inquiring data in a data system corresponding to the other domain models based on the matching rule to obtain second data;
and assigning the first data and the second data to the object data of the preset domain model based on the configuration rule of the object data of the preset domain model.
Further, the data processing apparatus further includes: the updating unit is used for acquiring an updating request of target object data corresponding to an updating entity and determining a preset field model corresponding to the entity;
determining other field models associated with the target object data based on configuration rules corresponding to the target object data;
determining target entity metadata in a data system corresponding to other field models based on the matching rules of the preset field model and the matching rules of other field models;
and updating the object data corresponding to the target object data in the target entity metadata based on the update request.
Referring to fig. 10, an electronic device 1000 of an embodiment of the present application may include one or more central processing units (CPUs, central processing units) 1001 and a memory 1005, where the memory 1005 stores one or more application programs or data.
Wherein the memory 1005 may be volatile storage or persistent storage. The program stored in the memory 1005 may include one or more modules, each of which may include a series of instruction operations in the electronic device. Still further, the central processor 1001 may be configured to communicate with the memory 1005, and execute a series of instruction operations in the memory 1005 on the electronic device 1000.
The electronic device 1000 can also include one or more power supplies 1002, one or more wired or wireless network interfaces 1003, one or more input/output interfaces 1004, and/or one or more operating systems, such as Windows ServerTM, mac OS XTM, unixTM, linuxTM, freeBSDTM, etc.
The cpu 1001 may perform the operations performed by the foregoing first aspect or any specific method embodiment of the first aspect, which are not described herein.
A computer readable storage medium is provided comprising instructions which, when run on a computer, cause the computer to perform a method as described in the first aspect or any specific implementation of the first aspect.
A computer program product comprising instructions or a computer program is provided which, when run on a computer, causes the computer to perform the method as described above in the first aspect or any one of the specific implementations of the first aspect.
It should be understood that, in various embodiments of the present application, the sequence number of each step does not mean that the execution sequence of each step should be determined by the function and the internal logic, and should not limit the implementation process of the embodiments of the present application.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the system and apparatus described above may refer to the corresponding process in the foregoing method embodiment, which is not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the elements is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system or apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all or part of the technical solution contributing to the prior art, or in the form of a software product, which is stored in a storage medium (computer program product) and includes several instructions for causing a computer device (which may be a personal computer, a service server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Claims (10)
1. A method of data processing, comprising:
establishing a plurality of field models outside the data system, wherein the field models are used for describing entities in the data system and object data corresponding to the entities;
in a target domain model corresponding to a target data system, determining the association relation between object data and other domain models, wherein the other domain models are domain models corresponding to other data systems outside the target data system;
and determining a configuration rule of the object data in the target domain model based on the association relation, and assigning entity metadata of different data systems to the object data of the target domain model based on the configuration rule.
2. The data processing method of claim 1, wherein the building a plurality of domain models outside the data system comprises:
determining whether an entity of the preset data system is associated with an entity of the other data system;
if yes, taking the entities of other data systems as object data corresponding to the entities of the preset data system, and building a domain model corresponding to the entities of the preset data system outside the data system.
3. The data processing method according to claim 1, wherein determining, in the target domain model corresponding to the target data system, an association relationship between the object data and other domain models includes:
in a target domain model corresponding to the target data system, determining whether the object data is matched with the entities of other domain models;
if yes, determining that the object data references other field models, and taking the reference relationship as the association relationship.
4. The data processing method according to claim 1, wherein the determining the configuration rule of the object data in the target domain model based on the association relation includes:
if the object data in the target field model has an association relationship, setting a configuration rule of the object data as other field models associated with the calling object data;
and if the object data in the target field model does not have the association relation, setting a configuration rule of the object data based on entity metadata in a data system corresponding to the target field model.
5. The data processing method according to claim 1, wherein assigning entity metadata of different data systems to object data of the target domain model based on the configuration rule includes:
determining entity metadata associated with entities of the target domain model in different data systems;
determining target entity metadata which accords with a preset matching rule in the target field model in the associated entity metadata;
and assigning the target entity metadata to the object data of the target domain model based on the configuration rule.
6. A data processing method according to claim 1, characterized in that the method comprises:
acquiring a query request for querying object data corresponding to a target entity, and determining a preset domain model corresponding to the target entity and other domain models associated with the object data corresponding to the target entity;
inquiring data in a data system corresponding to the preset field model based on the inquiring condition of the inquiring request to obtain first data;
in the other related domain models, inquiring data in a data system corresponding to the other domain models based on the matching rule to obtain second data;
and assigning the first data and the second data to the object data of the preset domain model based on the configuration rule of the object data of the preset domain model, and returning the assigned object data.
7. The data processing method of claim 1, wherein the method further comprises:
acquiring an update request of target object data corresponding to an update entity, and determining a preset domain model corresponding to the entity;
determining other field models associated with the target object data based on configuration rules corresponding to the target object data;
determining target entity metadata in a data system corresponding to other field models based on the matching rules of the preset field model and the matching rules of other field models;
and updating the object data corresponding to the target object data in the target entity metadata based on the update request.
8. A data processing apparatus, comprising:
the system comprises a building unit, a data system and a storage unit, wherein the building unit is used for building a plurality of field models outside the data system, and the field models are used for describing entities in the data system and object data corresponding to the entities;
the determining unit is used for determining the association relation between the object data and other domain models in the target domain model corresponding to the target data system, wherein the other domain models are domain models corresponding to other data systems outside the target data system;
and the execution unit is used for determining a configuration rule of the object data in the target domain model based on the association relation and assigning data in different data systems to the object data of the target domain model based on the configuration rule.
9. An electronic device, comprising:
a central processing unit, a memory and an input/output interface;
the memory is a short-term memory or a persistent memory;
the central processor is configured to communicate with the memory and to execute instruction operations in the memory to perform the method of any of claims 1 to 7.
10. A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311281529.0A CN117271641A (en) | 2023-09-27 | 2023-09-27 | Data processing method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311281529.0A CN117271641A (en) | 2023-09-27 | 2023-09-27 | Data processing method, device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117271641A true CN117271641A (en) | 2023-12-22 |
Family
ID=89214091
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311281529.0A Pending CN117271641A (en) | 2023-09-27 | 2023-09-27 | Data processing method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117271641A (en) |
-
2023
- 2023-09-27 CN CN202311281529.0A patent/CN117271641A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111506559B (en) | Data storage method, device, electronic equipment and storage medium | |
| CN111339171B (en) | Data query method, device and equipment | |
| CN113360519B (en) | Data processing method, device, equipment and storage medium | |
| CN111026775A (en) | Method and device for determining correlation index, server and storage medium | |
| CN111737564A (en) | Information query method, device, equipment and medium | |
| CN113407623A (en) | Data processing method and device and server | |
| CN110727857A (en) | Method and device for identifying key features of potential users aiming at business objects | |
| CN112416425A (en) | APP construction method and device, computer equipment and storage medium | |
| CN112883125A (en) | Entity data processing method, device, equipment and storage medium | |
| CN113568924A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111047434B (en) | Operation record generation method and device, computer equipment and storage medium | |
| CN114116065A (en) | Method and device for acquiring topological graph data object and electronic equipment | |
| CN112860953A (en) | Data importing method, device, equipment and storage medium of graph database | |
| CN114722036A (en) | Data processing method and device, electronic equipment and readable storage medium | |
| US11531706B2 (en) | Graph search using index vertices | |
| CN110515979B (en) | Data query method, device, equipment and storage medium | |
| CN114995877B (en) | Variable configuration method and device | |
| EP2294793A1 (en) | User interfaces for service object located in a distributed system | |
| CN117271641A (en) | Data processing method, device and storage medium | |
| CN110333883B (en) | Method and device for updating persistent data | |
| CN116028696A (en) | Resource information acquisition method and device, electronic equipment and storage medium | |
| CN113918728A (en) | Industrial Internet post-service knowledge map analysis platform | |
| CN113901046A (en) | Virtual dimension table construction method and device | |
| CN114020813A (en) | Data comparison method, device and equipment based on Hash algorithm and storage medium | |
| CN113779362A (en) | Data searching method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |