CN108399175B - Data storage and query method and device - Google Patents
Data storage and query method and device Download PDFInfo
- Publication number
- CN108399175B CN108399175B CN201710067363.0A CN201710067363A CN108399175B CN 108399175 B CN108399175 B CN 108399175B CN 201710067363 A CN201710067363 A CN 201710067363A CN 108399175 B CN108399175 B CN 108399175B
- Authority
- CN
- China
- Prior art keywords
- data
- identifier
- type
- service identifier
- data table
- 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.)
- Active
Links
Images
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/24—Querying
- G06F16/245—Query processing
- G06F16/2453—Query optimisation
Abstract
The application provides a data storage and query method and a device thereof, wherein the storage method comprises the following steps: determining a first service identifier of first class data having an association relation with second class data; acquiring a data table identifier corresponding to the second type of data according to the first service identifier; and storing the second type data into a data table corresponding to the data table identification. Through the technical scheme, in order to inquire the second type data corresponding to the first type data, even if a plurality of databases exist in the service system corresponding to the second type data and each database also has a plurality of data tables, the second type data can be inquired by inquiring one data table of one database, the inquiry process does not need to cross database data tables, the inquiry workload is small, the efficiency is high, the system overhead is low, the resources of the service system are saved, the resource utilization rate is high, the data retrieval is convenient, the convenience for maintaining the databases can be improved, and the expandability is good.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a data storage and query method and apparatus.
Background
Currently, as society develops, a large amount of data in a business system needs to be stored, and a database is a collection for storing data. With the continuous increase of services, when the data volume required to be stored reaches a certain degree, the data storage management is performed by using a single database, which causes problems of capacity bottleneck, performance bottleneck and the like, and affects the processing capacity of a service system, thereby affecting the more rapid development of the services; meanwhile, a single database is also a single point of the service system, and once a fault occurs, the availability of the service is directly influenced.
In order to solve the problem of a single database, a database-dividing and table-dividing technology can be adopted, wherein the database-dividing and table-dividing technology is a method for storing and managing mass data by a database, the database-dividing is to divide mass data into a plurality of database storage management by one database storage management, and the table-dividing is to divide mass data into a plurality of data table storage management by one data table storage management. By the database and table dividing technology, the capacity of the database is improved, the overall stability of a service system can be improved, and the influence of single database exception on services is reduced.
When there are multiple business systems, there may be an association between data of different business systems, for example, data 1 of business system a has an association with data 2 of business system B. When only one database and one data table exist in the service system B, the data 2 associated with the data 1 can be directly queried from the data table of the database. However, after the database-based and table-based technology is adopted, if the service system B has a plurality of databases, and each database has a plurality of data tables, in order to query the data 2 associated with the data 1, it is necessary to sequentially query whether each data table of each database has the data 2. The query process needs a cross-database data table, so that the query workload is large, the efficiency is poor, the system overhead is high, and the resources of a service system are wasted.
Disclosure of Invention
The application provides a data storage method, which comprises the following steps:
determining a first service identifier of first class data having an association relation with second class data;
acquiring a data table identifier corresponding to the second type of data according to the first service identifier;
and storing the second type data into a data table corresponding to the data table identification.
The application provides a data query method, which comprises the following steps:
when a data query request carrying a first service identifier is received, querying a mapping relation through the first service identifier to obtain a second service identifier corresponding to the first service identifier;
determining a data table identifier corresponding to the second type of data according to the second service identifier;
and querying the second type data from the data table corresponding to the data table identification.
The present application provides a data storage device, the device comprising: the determining module is used for determining a first service identifier of the first class of data which has an incidence relation with the second class of data;
the acquisition module is used for acquiring a data table identifier corresponding to the second type of data according to the first service identifier;
and the storage module is used for storing the second type of data into the data table corresponding to the data table identification.
The application provides a data inquiry device, the device includes:
the system comprises an acquisition module, a mapping module and a data processing module, wherein the acquisition module is used for acquiring a second service identifier corresponding to a first service identifier through a first service identifier query mapping relation when receiving a data query request carrying the first service identifier;
the determining module is used for determining a data table identifier corresponding to the second type of data according to the second service identifier;
and the query module is used for querying the second class data from the data table corresponding to the data table identification.
Based on the above technical solution, in the embodiment of the present application, when storing the second type of data, the first service identifier of the first type of data having an association relationship with the second type of data may be determined, the data table identifier corresponding to the second type of data is obtained according to the first service identifier, and the second type of data is stored in the data table corresponding to the data table identifier. When a data query request carrying a first service identifier is received, a data table identifier corresponding to second-class data can be determined through the first service identifier, and the second-class data is queried from a data table corresponding to the data table identifier. Based on this, when there are multiple service systems and there is relevance between data of different service systems, in order to query the second type of data corresponding to the first type of data, even if there are multiple databases in the service system corresponding to the second type of data and there are multiple data tables in each database, the second type of data can be queried by querying one data table in one database.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments of the present application or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained by those skilled in the art according to the drawings of the embodiments of the present application.
FIG. 1 is a schematic diagram of an application scenario in an embodiment of the present application;
FIG. 2 is a flow chart of a data storage method in one embodiment of the present application;
FIG. 3 is a flow diagram of a data query method in one embodiment of the present application;
FIG. 4 is a diagram of a hardware configuration of a server in one embodiment of the present application;
FIG. 5 is a block diagram of a data storage device in one embodiment of the present application;
FIG. 6 is a hardware block diagram of a server in another embodiment of the present application;
fig. 7 is a block diagram of a data query apparatus according to an embodiment of the present application.
Detailed Description
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein is meant to encompass any and all possible combinations of one or more of the associated listed items.
It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. Depending on the context, moreover, the word "if" as used may be interpreted as "at … …" or "when … …" or "in response to a determination".
The embodiment of the present application proposes a data storage method, as shown in fig. 1, the method may be applied to a network including a plurality of business systems (also referred to as application systems), each business system may include a plurality of databases, and each database may include a plurality of data tables. The service systems may be deployed in a distributed manner, that is, the service systems may be deployed in one server or may be deployed in multiple servers.
In order to solve the problem of a single database, a database-dividing and table-dividing technology can be adopted, wherein the database-dividing and table-dividing technology is a method for storing and managing mass data by a database, the database-dividing is to divide mass data into a plurality of database storage management by one database storage management, and the table-dividing is to divide mass data into a plurality of data table storage management by one data table storage management. Based on this, in the embodiment of the present application, each business system may include a plurality of databases, and each database may include a plurality of data tables. Therefore, the capacity of the database is improved, the overall stability of a service system can be improved, and the influence of single database exception on the service is reduced.
Referring to fig. 2, which is a flow chart of the data storage method, the method may include the following steps:
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between the steps may also be changed, and the execution sequence is not limited.
With respect to step 201, in an example, the process for determining the first service identifier of the first type of data having an association relationship with the second type of data may include, but is not limited to: in a first mode, if the upstream data which has an incidence relation with the second type of data has parent data, determining the service identifier of the parent data as a first service identifier of the first type of data; and if the upstream data which has the association relation with the second type of data does not have parent data, determining the service identifier of the upstream data as the first service identifier of the first type of data. Or, in the second mode, whether the upstream data having the association relationship with the second type of data has parent data or not, the service identifier of the upstream data is directly determined as the first service identifier of the first type of data.
As shown in fig. 1, data of the business system a has an association relationship with data of the business system B, data of the business system B has an association relationship with data of the business system C, and data of the business system a has an association relationship with data of the business system C. For example, business system a is a payment system, business system B is a chargeback system, and business system C is a financial system. In this application scenario, it is assumed that data 1, data 2, and data 3 have an association relationship, and it is necessary to store data 1 in the data table of the service system a, data 2 in the data table of the service system B, and data 3 in the data table of the service system C.
For the process of "storing data 1 in the data table of the service system a", since the service system a does not have an upstream system, that is, there is no upstream data associated with data 1, a preset policy may be adopted to select a database and a data table for data 1, and store data 1 in the data table of the database. For example, the user identifier is parsed from data 1, the database identifier is determined based on the second last bit of the user identifier, and the data table identifier is determined based on the last bit of the user identifier. Assuming that D is 3, when the penultimate digit of the user identifier is 0, 1, 2, or 3, the corresponding database identifier is a1, when the penultimate digit of the user identifier is 4, 5, or 6, the corresponding database identifier is a2, and when the penultimate digit of the user identifier is 7, 8, or 9, the corresponding database identifier is A3. For the database a1, assuming that O is 10, when the last bit of the user id is 0, the corresponding data table id is a11, when the last bit of the user id is 1, the corresponding data table id is a12, and so on. The processing for database A2 and database A3 is similar to database A1 and will not be described in detail. The foregoing is only one example of the preset policy, and the preset policy is not limited to this, and all manners capable of selecting the database and the data table for the data 1 are within the protection scope of the embodiment of the present application.
For the process of "storing data 2 in the data table of the service system B", since the service system B has an upstream system (i.e., the service system a), that is, there is upstream data (i.e., data 1) associated with the data 2, the process may be performed by using the technical solution of the embodiment of the present application. In this step, only the contents related to step 201 will be described, and other processes of "storing data 2 in the data table of the service system B" will be described later. For step 201, data 2 that needs to be stored in the service system B may be referred to as second class data, upstream data that has an association relationship with the second class data is data 1, and the upstream data does not have a parent data, so that the service identifier of data 1 is determined as a first service identifier of the first class data.
For the process of "storing data 3 in the data table of the service system C", since the service system C has an upstream system (i.e., the service system B), that is, there is upstream data (i.e., data 2) associated with the data 3, the process may be performed by using the technical solution of the embodiment of the present application. In this step, only the contents related to step 201 will be described, and other processes of "storing data 3 in the data table of the service system C" will be described later. For step 201, data 3 to be stored in the service system C may be referred to as second class data, and upstream data having an association relationship with the second class data is data 2, where the upstream data has parent data (data 1), so that the service identifier of data 1 is determined as a first service identifier of the first class data.
In one example, when there is no more upstream data in the upstream data having an association relationship with the second type of data, it indicates that there is no parent data corresponding to the upstream data. When there is data further upstream in the upstream data having an association relationship with the second type of data, it indicates that there is parent data corresponding to the upstream data, and the parent data refers to data of the first business system (i.e., the business system a where there is no upstream system). For example, if the service system C is also associated with the service system D, when the data 4 required to be stored in the service system D is the second type of data, the upstream data is data 3, and the parent data of the upstream data is data 1, not data 2.
Based on the above manner, for all data (such as data 2, data 3, data 4, and the like) associated with data 1, the first type of data is data 1, so that the data table identifiers corresponding to data 2, data 3, and data 4 can be determined based on the same service identifier, and the following situations do not occur: the data table identification corresponding to the data 2 is determined based on the service identification of the data 1, the data table identification corresponding to the data 3 is determined based on the service identification of the data 2, and the data table identification corresponding to the data 4 is determined based on the service identification of the data 3.
In this way, the following effects can be achieved: assuming that both data 2 and data 3 need to be stored in the service system B, when the data table identifiers corresponding to the data 2 and the data 3 are determined based on the service identifier of the data 1, the data table identifiers corresponding to the data 2 and the data 3 are the same, so that the data 2 and the data 3 are stored in the same data table. When the data 2 and the data 3 are inquired, the data 2 and the data 3 can be inquired from the same data table, cross-data table processing is not needed, and the performance is high. If the data table identifier corresponding to the data 2 is determined based on the service identifier of the data 1, and the data table identifier corresponding to the data 3 is determined based on the service identifier of the data 2, the data table identifiers corresponding to the data 2 and the data 3 may be different, so that the data 2 and the data 3 are stored in different data tables, and thus, when the data 2 and the data 3 corresponding to the data 1 are queried, cross-data table processing is required, and the performance is low.
With respect to step 202, in an example, the process of "obtaining the data table identifier corresponding to the second type of data according to the first service identifier" may include, but is not limited to, the following manners: determining the number of data tables of a service system corresponding to the first type of data and the number of data tables of a service system corresponding to the second type of data; if the number of the data tables of the service system corresponding to the first type of data is the same as the number of the data tables of the service system corresponding to the second type of data, the data table identifier corresponding to the first type of data can be determined according to the first service identifier, and the data table identifier corresponding to the second type of data can be obtained according to the data table identifier corresponding to the first type of data. And secondly, determining the number of data tables of the service system corresponding to the second type of data, and obtaining the data table identification corresponding to the second type of data according to the first service identification and the number of the data tables.
Based on the first method, for the process of "storing data 2 in the data table of the service system B", assuming that D is 3 and E is 3, the number of data tables of the service system a corresponding to the first type of data (i.e., data 1) is O + P + Q, and the number of data tables of the service system B corresponding to the second type of data (i.e., data 2) is R + S + T. Further, assuming that the number of the data table identifier and the service identifier is the same, the data table identifier corresponding to the data 1 may be determined according to the service identifier of the data 1, and the data table identifier corresponding to the data 1 is determined as the data table identifier corresponding to the data 2.
For the process of "determining the data table identifier corresponding to the data 1 according to the service identifier of the data 1", when the service identifier of the data 1 is generated, a service identifier including the data table identifier of the data 1 may be generated, and if the data 1 is stored in the data table a16, the service identifier may be xxxxxx 006, where xxxx is any numerical value and may be selected empirically, without limitation, and 006 indicates that the data 1 is stored in the 6 th data table of the service system a, so that it may be determined that the data table identifier corresponding to the data 1 is 6 according to the service identifier xxxx006 of the data 1, and it is determined that the data table identifier corresponding to the data 2 is 6. Of course, the last 3 bits of the service identifier are used as the data table identifier, and in practical applications, other positions of the service identifier may also be used as the data table identifier, such as the previous 3 bits, the 5 th to 7 th bits, and so on, which is not limited herein.
The procedure for "storing data 3 in the data table of the business system C" is similar to the above-described procedure.
For the second way, in an example, the process of "obtaining the data table identifier corresponding to the second type of data according to the first service identifier and the number of the data tables" may include, but is not limited to: performing hash processing on the first service identifier to obtain a first numerical value; the first numerical value is subjected to remainder processing on the number of the data table to obtain a second numerical value; and determining the data table identifier corresponding to the second class of data according to the second numerical value.
Based on the second method, for the process of "storing data 2 in the data table of the service system B", assuming that E is 3, the number of data tables of the service system B corresponding to the second type of data (data 2) is R + S + T. Assuming that the first service identifier is 98745006, a hash process may be performed on "98745006" to obtain a first value, and a specific hash algorithm may be selected according to actual experience, which is not described herein again. And then, carrying out remainder processing on the first numerical value pair (R + S + T) to obtain a second numerical value. Assuming that the second value is 0, the data table identifier corresponding to the data 2 is 1, which represents the 1 st data table of the service system B, assuming that the second value is 1, the data table identifier corresponding to the data 2 is 2, which represents the 2 nd data table of the service system B, and so on.
In one example, assume that the number of sub-pools of service system a is D1(D1 ≧ 1), the number of sub-tables of service system a is T1(T1 ≧ 1), the number of sub-pools of service system B is D2(D2 ≧ 1), the number of sub-tables of service system B is T2(T1 ≧ 2), and the first service identifier is ID 1. Based on this, the hash processing is carried out on the first service identifier to obtain a first numerical value; and, the process of obtaining the second value by performing remainder processing on the number of the data table by using the first value may include, but is not limited to, processing by using the following formula: hash (ID 1)% T2; wherein, the hash () algorithm is a hash algorithm configured in advance according to experience.
The procedure for "storing data 3 in the data table of the business system C" is similar to the above-described procedure.
For step 203, in one example, for the process of "store data 2 in data table of business system B", assuming that the data table is identified as 7, data 2 may be stored in the 7 th data table of business system B. Further, for the process of "storing data 3 in the data table of business system C", assuming that the data table is identified as 9, data 3 may be stored in the 9 th data table of business system C.
In an example, after obtaining the data table identifier corresponding to the second type of data according to the first service identifier (i.e., step 102), the second service identifier of the second type of data may also be determined according to the data table identifier corresponding to the second type of data, and the mapping relationship between the first service identifier and the second service identifier is recorded.
For example, when the service identifier of data 2 is generated, a service identifier including the data table identifier of data 2 may be generated, for example, when the data table identifier of data 2 is 7, the service identifier of data 2 may be yyyy007, which is an arbitrary number and can be selected empirically, without limitation, and 007 indicates that data 2 is stored in the 7 th data table of service system B. Of course, the last 3 bits of the service identifier are used as the data table identifier, and in practical application, when the service identifier of the data 2 is generated, other positions of the service identifier may also be used as the data table identifier, such as the previous 3 bits, the 5 th to the 7 th bits, and so on, which is not limited.
In one example, based on a mapping relationship between a first service identifier and a second service identifier, when a data query request carrying the first service identifier is received, the mapping relationship is queried through the first service identifier, so that a second service identifier corresponding to the first service identifier can be obtained, a data table identifier corresponding to second-class data is determined according to the second service identifier, and the second-class data is queried from a data table corresponding to the data table identifier.
For example, assuming that a mapping relationship of "the first service identifier 98745006 and the second service identifier 34598007" is maintained, based on this, when a data query request carrying 98745006 is received, 34598007 can be obtained by querying 98745006 for the mapping relationship. Moreover, since the last 3 bits of 34598007 are 007, it is determined that the data table is designated as 007, that is, the data table corresponding to the second type of data is designated as 007, and therefore, the 7 th data table of the service system B can be searched for data 2 corresponding to 34598007.
In an example, after the data table identifier corresponding to the second type of data is obtained according to the first service identifier (i.e., step 102), the database identifier corresponding to the second type of data may also be determined according to the data table identifier corresponding to the second type of data, and the second service identifier of the second type of data is determined according to the data table identifier and the database identifier corresponding to the second type of data; wherein the second service identifier includes the data table identifier and the database identifier. And then, recording the mapping relation between the first service identifier and the second service identifier.
In an example, for the process of "determining the database identifier corresponding to the second type of data according to the data table identifier corresponding to the second type of data", it is assumed that the service system B includes 3 databases, the database 1 includes 10 data tables, the database 2 includes 12 data tables, and the database 1 includes 9 data tables, and when the data table identifier is 7 (between 1 and 10), the corresponding database identifier is 1, when the data table identifier is 15 (between 11 and 22), the corresponding database identifier is 2, when the data table identifier is 28 (between 23 and 31), the corresponding database identifier is 3, and so on, and no limitation is made to this.
For example, when the service identifier of the data 2 is generated, a service identifier including a data table identifier and a database identifier of the data 2 may be generated, and if the data table identifier of the data 2 is 7 and the database identifier is 1, the service identifier of the data 2 may be yyyy001007, which is an arbitrary number and may be selected empirically, without limitation, 001 indicates that the data 2 is stored in the 1 st database of the service system B, and 007 indicates that the data 2 is stored in the 7 th database of the service system B. Of course, in this embodiment, the last 3 bits of the service identifier are taken as the data table identifier, and the 4 th to 6 th bits of the service identifier are taken as the database identifier, for example, in practical application, when the service identifier of the data 2 is generated, other positions of the service identifier may also be taken as the data table identifier, and other positions of the service identifier may be taken as the database identifier, which is not limited to this.
In an example, based on a mapping relationship between a first service identifier and a second service identifier, when a data query request carrying the first service identifier is received, the mapping relationship may be queried through the first service identifier to obtain a second service identifier corresponding to the first service identifier, a data table identifier and a database identifier corresponding to second-class data are determined according to the second service identifier, a database corresponding to the database identifier and a data table corresponding to the data table identifier are determined, and the second-class data are queried from the data table of the database.
For example, assuming that a mapping relationship of "the first service identifier 98745006 and the second service identifier 34598001007" is maintained, based on this, when a data query request carrying 98745006 is received, 34598001007 can be obtained by querying 98745006 for the mapping relationship. Since the 4 th to 6 th bits of the reciprocal number 34598001007 are 001, and the last 3 th bit is 007, it is determined that the database id is 001 and the data table id is 007, that is, the database id corresponding to the second type of data is 001 and the data table id is 007, so that the 7 th data table of the 1 st database of the service system B can be queried for data 2 corresponding to 34598001007.
Based on the technical scheme, when a plurality of service systems exist and data of different service systems have relevance, in order to query second type data corresponding to the first type data, even if the service systems corresponding to the second type data have a plurality of databases and each database has a plurality of data tables, the second type data can be queried by querying one data table of one database.
Similar to the data storage method described above, the embodiment of the present application also proposes a data query method, as shown in fig. 1, the method may be applied to a network including a plurality of business systems, each business system may include a plurality of databases, and each database may include a plurality of data tables. The service systems may be deployed in a distributed manner, that is, the service systems may be deployed in one server or may be deployed in multiple servers. Referring to fig. 3, a flow chart of the data query method may include the following steps:
In an example, the execution sequence is only an example given for convenience of description, and in practical applications, the execution sequence between the steps may also be changed, and the execution sequence is not limited.
In an example, before querying the second type data from the data table corresponding to the data table identifier (i.e., step 303), a first service identifier of the first type data having an association relationship with the second type data may also be determined, and the data table identifier corresponding to the second type data is obtained according to the first service identifier. Further, the second type data may be stored in a data table corresponding to the data table identifier.
In one example, the process for determining the first service identifier of the first type of data having an association relationship with the second type of data may include, but is not limited to, the following: in a first mode, if the upstream data which has an incidence relation with the second type of data has parent data, determining the service identifier of the parent data as a first service identifier of the first type of data; and if the upstream data which has the association relation with the second type of data does not have parent data, determining the service identifier of the upstream data as the first service identifier of the first type of data. Or, in the second mode, whether the upstream data having the association relationship with the second type of data has parent data or not, the service identifier of the upstream data is directly determined as the first service identifier of the first type of data.
In an example, the process of "obtaining the data table identifier corresponding to the second type of data according to the first service identifier" may include, but is not limited to, the following ways: determining the number of data tables of a service system corresponding to the first type of data and the number of data tables of a service system corresponding to the second type of data in a first mode; if the number of the data tables of the service system corresponding to the first type of data is the same as the number of the data tables of the service system corresponding to the second type of data, the data table identifier corresponding to the first type of data can be determined according to the first service identifier, and the data table identifier corresponding to the second type of data can be obtained according to the data table identifier corresponding to the first type of data. And secondly, determining the number of data tables of the service system corresponding to the second type of data, and obtaining the data table identification corresponding to the second type of data according to the first service identification and the number of the data tables.
For the second way, in an example, the process of "obtaining the data table identifier corresponding to the second type of data according to the first service identifier and the number of the data tables" may include, but is not limited to: performing hash processing on the first service identifier to obtain a first numerical value; the first numerical value is subjected to remainder processing on the number of the data table to obtain a second numerical value; and determining the data table identifier corresponding to the second class of data according to the second numerical value.
In an example, after the data table identifier corresponding to the second type of data is obtained according to the first service identifier, a second service identifier of the second type of data may also be determined according to the data table identifier corresponding to the second type of data, and a mapping relationship between the first service identifier and the second service identifier is recorded.
Further, based on the mapping relationship between the first service identifier and the second service identifier, when a data query request carrying the first service identifier is received, the mapping relationship is queried through the first service identifier, so that a second service identifier corresponding to the first service identifier can be obtained, a data table identifier corresponding to the second type of data is determined according to the second service identifier, and the second type of data is queried from a data table corresponding to the data table identifier.
In an example, after the data table identifier corresponding to the second type of data is obtained according to the first service identifier, the database identifier corresponding to the second type of data may also be determined according to the data table identifier corresponding to the second type of data, and the second service identifier of the second type of data is determined according to the data table identifier and the database identifier corresponding to the second type of data; wherein the second service identifier may include the data table identifier and the database identifier. And then, recording the mapping relation between the first service identifier and the second service identifier.
Further, based on the mapping relationship between the first service identifier and the second service identifier, when a data query request carrying the first service identifier is received, the mapping relationship can be queried through the first service identifier to obtain a second service identifier corresponding to the first service identifier, a data table identifier and a database identifier corresponding to the second type of data are determined according to the second service identifier, a database corresponding to the database identifier and a data table corresponding to the data table identifier are determined, and the second type of data is queried from the data table of the database.
Based on the technical scheme, when a plurality of service systems exist and data of different service systems have relevance, in order to query second type data corresponding to the first type data, even if the service systems corresponding to the second type data have a plurality of databases and each database has a plurality of data tables, the second type data can be queried by querying one data table of one database.
The data storage and query method is described in detail below with reference to specific application scenarios. In this application scenario, as shown in fig. 1, data of the service system a and data of the service system B have an association relationship, data of the service system B and data of the service system C have an association relationship, and data of the service system a and data of the service system C have an association relationship. For example, business system a is a payment system, business system B is a chargeback system, and business system C is a financial system. In this application scenario, it is assumed that data 1, data 2, and data 3 have an association relationship, and it is necessary to store data 1 in the data table of the service system a, data 2 in the data table of the service system B, and data 3 in the data table of the service system C.
In the application scenario, the data storage and query method may include the following steps:
step 1, selecting a database and a data table for data 1 by adopting a preset strategy, storing the data 1 into the data table of the database, and generating a service identifier of the data 1 according to the database identifier and the data table identifier.
Step 2, since the business system B has an upstream system (business system a), that is, there is upstream data (data 1) associated with the data 2, the data 2 to be stored in the business system B is referred to as second type data, the upstream data having an association relationship with the second type data is data 1, and the upstream data does not have parent data, so that the business identifier of the data 1 is determined as the first business identifier of the first type data.
And 3, determining the number of data tables of the service system B corresponding to the data 2.
And 4, performing hash processing on the service identifier of the data 1 to obtain a first numerical value, and performing remainder processing on the number of the data table of the service system B by using the first numerical value to obtain a second numerical value.
And step 5, determining a data table identifier (such as a data table 7) corresponding to the data 2 according to the second numerical value.
And 6, storing the data 2 into a data table 7 of the service system B corresponding to the data table identification.
And 7, determining the service identifier of the data 2 according to the data table identifier and the database identifier corresponding to the data 2, wherein the service identifier may include the data table identifier and the database identifier corresponding to the data 2.
And 8, recording the mapping relation between the service identifier of the data 1 and the service identifier of the data 2 by the service system B.
Step 9, since the service system C has an upstream system (service system B), that is, there is upstream data (data 2) associated with the data 3, the data 3 to be stored in the service system C is referred to as second type data, the upstream data having an association relationship with the second type data is referred to as data 2, and the upstream data has parent data, so that the service identifier of the parent data (data 1) is determined as the first service identifier of the first type data.
And step 10, determining the data table number of the service system C corresponding to the data 3.
And 11, performing hash processing on the service identifier of the data 1 to obtain a first numerical value, and performing remainder processing on the number of the data table of the service system C by using the first numerical value to obtain a second numerical value.
And step 12, determining a data table identifier (such as the data table 9) corresponding to the data 3 according to the second value.
And step 13, storing the data 3 into the data table 9 of the service system C corresponding to the data table identification.
And step 14, determining the service identifier of the data 3 according to the data table identifier and the database identifier corresponding to the data 3, wherein the service identifier may include the data table identifier and the database identifier corresponding to the data 3.
Step 15, the service system C records the mapping relationship between the service identifier of the data 1 and the service identifier of the data 3, and records the mapping relationship between the service identifier of the data 2 and the service identifier of the data 3.
Step 16, when receiving the data query request carrying the service identifier of the data 1, the service system B queries the mapping relation recorded in the step 8 through the service identifier of the data 1 to obtain the service identifier of the data 2.
Step 17, the service system B determines the database identifier and the data table identifier of the data 2 according to the service identifier of the data 2, determines the database corresponding to the database identifier and the data table corresponding to the data table identifier, and queries the data 2 from the data table of the database, which is not described in detail again.
Step 18, when receiving the data query request carrying the service identifier of data 1/data 2, the service system C queries the mapping relationship recorded in step 15 through the service identifier to obtain the service identifier of data 3.
Step 19, the service system C determines the database identifier and the data table identifier of the data 3 according to the service identifier of the data 3, determines the database corresponding to the database identifier and the data table corresponding to the data table identifier, and queries the data 3 from the data table of the database, which is not described in detail again.
Based on the same application concept as the method, the embodiment of the present application further provides a data storage device 120, and the data storage device 120 is applied on the server 10. The data storage device 120 may be implemented by software, or may be implemented by hardware or a combination of hardware and software. A logical means, implemented in software for example, is formed by the processor 11 of the server 10 reading corresponding computer program instructions in the non-volatile memory 12. From a hardware aspect, as shown in fig. 4, which is a hardware structure diagram of the server 10 where the data storage device 120 is located, in addition to the processor 11 and the nonvolatile memory 12 shown in fig. 4, the server 10 may further include other hardware, such as a forwarding chip, a network interface, and a memory, which are responsible for processing a packet; the server 10 may also be a distributed device in terms of hardware architecture, and may include multiple interface cards to extend message processing at the hardware level.
As shown in fig. 5, a structure diagram of a data storage device proposed in the present application includes: a determining module 1201, configured to determine a first service identifier of a first type of data having an association relationship with a second type of data; an obtaining module 1202, configured to obtain, according to the first service identifier, a data table identifier corresponding to the second type of data; a storage module 1203, configured to store the second type data in a data table corresponding to the data table identifier.
The determining module 1201 is specifically configured to, in a process of determining a first service identifier of first type data having an association relationship with second type data, determine, if parent data exists in upstream data having an association relationship with the second type data, a service identifier of the parent data as the first service identifier of the first type data; or, if the upstream data having the association relationship with the second type of data does not have parent data, determining the service identifier of the upstream data as the first service identifier of the first type of data.
The obtaining module 1202 is specifically configured to, in the process of obtaining the data table identifier corresponding to the second type of data according to the first service identifier, determine the data table identifier corresponding to the first type of data according to the first service identifier if the number of the data tables of the service system corresponding to the first type of data is the same as the number of the data tables of the service system corresponding to the second type of data; obtaining a data table identifier corresponding to the second type of data according to the data table identifier corresponding to the first type of data; or, determining the number of data tables of the service system corresponding to the second type of data; obtaining a data table identifier corresponding to the second type of data according to the first service identifier and the number of the data tables;
the obtaining module 1202 is specifically configured to, in the process of obtaining a data table identifier corresponding to second-class data according to a first service identifier and the number of data tables, perform hash processing on the first service identifier to obtain a first numerical value; the first numerical value is subjected to remainder processing on the number of the data tables to obtain a second numerical value; and determining the data table identifier corresponding to the second type of data according to the second numerical value.
In one example, the data storage device further comprises (not embodied in the figure):
the recording module is used for determining a second service identifier of second type data according to a data table identifier corresponding to the second type data and recording the mapping relation between the first service identifier and the second service identifier;
the query module is used for querying the mapping relation through the first service identifier when receiving a data query request carrying the first service identifier to obtain a second service identifier corresponding to the first service identifier; determining a data table identifier corresponding to the second type of data according to the second service identifier; and querying the second type data from the data table corresponding to the data table identification.
Based on the same application concept as the method, the embodiment of the present application further provides a data query device 220, where the data query device 220 is applied on the server 20. The data query device 220 may be implemented by software, or may be implemented by hardware, or a combination of hardware and software. A logical means, implemented in software for example, is formed by the processor 21 of the server 20 reading corresponding computer program instructions in the non-volatile memory 22. From a hardware aspect, as shown in fig. 6, which is a hardware structure diagram of the server 20 where the data query device 220 is located, in addition to the processor 21 and the nonvolatile memory 22 shown in fig. 6, the server 20 may further include other hardware, such as a forwarding chip, a network interface, and a memory, which are responsible for processing a message; the server 20 may also be a distributed device in terms of hardware architecture, and may include multiple interface cards to facilitate expansion of message processing at the hardware level.
As shown in fig. 7, a structure diagram of a data query apparatus proposed in the present application includes: an obtaining module 2201, configured to, when a data query request carrying a first service identifier is received, query a mapping relationship through the first service identifier to obtain a second service identifier corresponding to the first service identifier; a determining module 2202, configured to determine, according to the second service identifier, a data table identifier corresponding to the second type of data; a query module 2203, configured to query the second type data from the data table identified by the data table identifier.
In one example, the data querying device further comprises (not shown in the figure):
the storage module is used for determining a first service identifier of the first class of data which has an incidence relation with the second class of data; acquiring a data table identifier corresponding to the second type of data according to the first service identifier; and storing the second type data into a data table corresponding to the data table identification.
In one example, the data querying device further comprises (not shown in the figure):
the recording module is used for determining a second service identifier of the second type of data according to a data table identifier corresponding to the second type of data; and recording the mapping relation between the first service identifier and the second service identifier.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Furthermore, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (which may include, but is not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (18)
1. A method of data storage, the method comprising:
determining a first service identifier of first class data having an association relation with second class data; acquiring a data table identifier corresponding to the second type of data according to the first service identifier; determining a database identifier corresponding to the second type of data according to the data table identifier; determining a second service identifier of the second type of data according to the data table identifier and the database identifier; recording the mapping relation between the first service identifier and the second service identifier; storing the second type data into a data table corresponding to the data table identification;
when a data query request carrying the first service identifier is received, querying the mapping relation through the first service identifier to obtain a second service identifier corresponding to the first service identifier; determining a data table identifier and a database identifier corresponding to the second type of data according to the second service identifier; determining a database corresponding to the database identifier and a data table corresponding to the data table identifier; and querying the second type data from the data table of the database.
2. The method according to claim 1, wherein the process of determining the first service identifier of the first type of data having an association relationship with the second type of data specifically includes:
if the upstream data which has the incidence relation with the second type of data has parent data, determining the service identifier of the parent data as a first service identifier of the first type of data; alternatively, the first and second electrodes may be,
and if the upstream data which has the incidence relation with the second type of data does not have parent data, determining the service identifier of the upstream data as the first service identifier of the first type of data.
3. The method according to claim 1, wherein the process of obtaining the data table identifier corresponding to the second type of data according to the first service identifier specifically includes:
if the number of the data tables of the service system corresponding to the first type of data is the same as that of the service system corresponding to the second type of data, determining a data table identifier corresponding to the first type of data according to the first service identifier;
and obtaining the data table identification corresponding to the second type of data according to the data table identification corresponding to the first type of data.
4. The method according to claim 1, wherein the process of obtaining the data table identifier corresponding to the second type of data according to the first service identifier specifically includes:
determining the number of data tables of the service system corresponding to the second type of data;
and obtaining the data table identification corresponding to the second type of data according to the first service identification and the number of the data tables.
5. The method according to claim 4, wherein the process of obtaining the data table identifier corresponding to the second type of data according to the first service identifier and the number of the data tables specifically includes:
performing hash processing on the first service identifier to obtain a first numerical value;
the first numerical value is subjected to remainder processing on the number of the data tables to obtain a second numerical value;
and determining the data table identifier corresponding to the second type of data according to the second numerical value.
6. The method according to claim 1, wherein after obtaining the data table identifier corresponding to the second type of data according to the first service identifier, the method further comprises:
determining a second service identifier of the second type of data according to a data table identifier corresponding to the second type of data;
and recording the mapping relation between the first service identifier and the second service identifier.
7. The method of claim 6, wherein after storing the second type of data in the data table corresponding to the data table identification, the method further comprises:
when a data query request carrying the first service identifier is received, querying the mapping relation through the first service identifier to obtain a second service identifier corresponding to the first service identifier;
determining a data table identifier corresponding to the second type of data according to the second service identifier;
and querying the second type data from the data table corresponding to the data table identification.
8. The method of claim 1,
the second service identifier includes the data table identifier and the database identifier.
9. A method for data query, the method comprising:
when a data query request carrying a first service identifier is received, querying a mapping relation through the first service identifier to obtain a second service identifier corresponding to the first service identifier;
determining a data table identifier and a database identifier corresponding to the second type of data according to the second service identifier;
determining a database corresponding to the database identifier and a data table corresponding to the data table identifier;
and querying the second class data from the data table corresponding to the data table identification of the database.
10. The method of claim 9, wherein before querying the second type of data from the data table corresponding to the data table identification of the database, the method further comprises:
determining a first service identifier of first class data having an association relation with the second class data;
acquiring a data table identifier corresponding to the second type of data according to the first service identifier;
and storing the second type data into a data table corresponding to the data table identification.
11. The method according to claim 10, wherein the process of obtaining the data table identifier corresponding to the second type of data according to the first service identifier specifically includes:
if the number of the data tables of the service system corresponding to the first type of data is the same as that of the service system corresponding to the second type of data, determining a data table identifier corresponding to the first type of data according to the first service identifier;
obtaining a data table identifier corresponding to the second type of data according to the data table identifier corresponding to the first type of data;
or, determining the number of data tables of the service system corresponding to the second type of data;
and obtaining the data table identification corresponding to the second type of data according to the first service identification and the number of the data tables.
12. The method according to claim 10, wherein after obtaining the data table identifier corresponding to the second type of data according to the first service identifier, the method further comprises:
determining a second service identifier of the second type of data according to a data table identifier corresponding to the second type of data;
and recording the mapping relation between the first service identifier and the second service identifier.
13. A data storage device, characterized in that the device comprises:
the determining module is used for determining a first service identifier of the first class of data which has an incidence relation with the second class of data;
the acquisition module is used for acquiring a data table identifier corresponding to the second type of data according to the first service identifier;
the recording module is used for determining a database identifier corresponding to the second type of data according to the data table identifier; determining a second service identifier of the second type of data according to the data table identifier and the database identifier; recording the mapping relation between the first service identifier and the second service identifier;
the storage module is used for storing the second type of data into the data table corresponding to the data table identification;
the query module is used for querying the mapping relation through the first service identifier when receiving a data query request carrying the first service identifier to obtain a second service identifier corresponding to the first service identifier; determining a data table identifier and a database identifier corresponding to the second type of data according to the second service identifier; determining a database corresponding to the database identifier and a data table corresponding to the data table identifier; and querying the second type data from the data table of the database.
14. The apparatus of claim 13,
the determining module is specifically configured to, in a process of determining a first service identifier of first-class data having an association relationship with second-class data, determine, if parent data exists in upstream data having an association relationship with the second-class data, a service identifier of the parent data as the first service identifier of the first-class data; or, if the upstream data having the association relationship with the second type of data does not have parent data, determining the service identifier of the upstream data as the first service identifier of the first type of data.
15. The apparatus of claim 13,
the obtaining module is specifically configured to, in a process of obtaining a data table identifier corresponding to the second type of data according to the first service identifier, determine, according to the first service identifier, a data table identifier corresponding to the first type of data if the number of data tables of a service system corresponding to the first type of data is the same as the number of data tables of a service system corresponding to the second type of data; obtaining a data table identifier corresponding to the second type of data according to the data table identifier corresponding to the first type of data; or, determining the number of data tables of the service system corresponding to the second type of data; obtaining a data table identifier corresponding to the second type of data according to the first service identifier and the number of the data tables;
the obtaining module is specifically configured to, in a process of obtaining a data table identifier corresponding to second-class data according to a first service identifier and the number of data tables, perform hash processing on the first service identifier to obtain a first numerical value; the first numerical value is subjected to remainder processing on the number of the data tables to obtain a second numerical value; and determining the data table identifier corresponding to the second type of data according to the second numerical value.
16. A data query apparatus, characterized in that the apparatus comprises:
the system comprises an acquisition module, a mapping module and a data processing module, wherein the acquisition module is used for acquiring a second service identifier corresponding to a first service identifier through a first service identifier query mapping relation when receiving a data query request carrying the first service identifier;
the determining module is used for determining a data table identifier and a database identifier corresponding to the second type of data according to the second service identifier; determining a database corresponding to the database identifier and a data table corresponding to the data table identifier;
and the query module is used for querying the second class data from the data table corresponding to the data table identification of the database.
17. The apparatus of claim 16, further comprising:
the storage module is used for determining a first service identifier of the first class of data which has an incidence relation with the second class of data; acquiring a data table identifier corresponding to the second type of data according to the first service identifier; and storing the second type data into a data table corresponding to the data table identification.
18. The apparatus of claim 16, further comprising:
the recording module is used for determining a second service identifier of the second type of data according to a data table identifier corresponding to the second type of data; and recording the mapping relation between the first service identifier and the second service identifier.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710067363.0A CN108399175B (en) | 2017-02-07 | 2017-02-07 | Data storage and query method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710067363.0A CN108399175B (en) | 2017-02-07 | 2017-02-07 | Data storage and query method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108399175A CN108399175A (en) | 2018-08-14 |
| CN108399175B true CN108399175B (en) | 2022-04-12 |
Family
ID=63094168
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710067363.0A Active CN108399175B (en) | 2017-02-07 | 2017-02-07 | Data storage and query method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108399175B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110245150B (en) * | 2019-05-30 | 2023-03-17 | 创新先进技术有限公司 | Data processing method, data processing device, data query method, data query device, data processing equipment and data processing system |
| CN110275890B (en) * | 2019-06-27 | 2021-01-15 | 中国石油集团东方地球物理勘探有限责任公司 | Data query method and system |
| CN110704455B (en) * | 2019-10-17 | 2022-08-05 | 昆仑数智科技有限责任公司 | Method, device, terminal and storage medium for generating data asset directory |
| CN113849524B (en) * | 2021-11-30 | 2022-10-18 | 阿里云计算有限公司 | Data processing method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103020193A (en) * | 2012-12-03 | 2013-04-03 | 北京奇虎科技有限公司 | Method and equipment for processing database operation request |
| CN103577440A (en) * | 2012-07-27 | 2014-02-12 | 阿里巴巴集团控股有限公司 | Data processing method and device in non-relational database |
| CN103677649A (en) * | 2012-09-12 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Data access method and device |
| CN105022739A (en) * | 2014-04-21 | 2015-11-04 | 腾讯科技（北京）有限公司 | Data storage method and device |
| CN106168949A (en) * | 2016-05-03 | 2016-11-30 | 泰康保险集团股份有限公司 | The method and device that data base splits |
| CN106202219A (en) * | 2016-06-27 | 2016-12-07 | 安徽科成信息科技有限公司 | A kind of update method of network monitoring daily record |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103593419B (en) * | 2013-10-30 | 2018-03-09 | 华为技术有限公司 | Data query method, apparatus, server and system |
| US9965488B2 (en) * | 2015-06-18 | 2018-05-08 | International Business Machines Corporation | Back referencing of deduplicated data |
| US10067954B2 (en) * | 2015-07-22 | 2018-09-04 | Oracle International Corporation | Use of dynamic dictionary encoding with an associated hash table to support many-to-many joins and aggregations |
-
2017
- 2017-02-07 CN CN201710067363.0A patent/CN108399175B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103577440A (en) * | 2012-07-27 | 2014-02-12 | 阿里巴巴集团控股有限公司 | Data processing method and device in non-relational database |
| CN103677649A (en) * | 2012-09-12 | 2014-03-26 | 腾讯科技（深圳）有限公司 | Data access method and device |
| CN103020193A (en) * | 2012-12-03 | 2013-04-03 | 北京奇虎科技有限公司 | Method and equipment for processing database operation request |
| CN105022739A (en) * | 2014-04-21 | 2015-11-04 | 腾讯科技（北京）有限公司 | Data storage method and device |
| CN106168949A (en) * | 2016-05-03 | 2016-11-30 | 泰康保险集团股份有限公司 | The method and device that data base splits |
| CN106202219A (en) * | 2016-06-27 | 2016-12-07 | 安徽科成信息科技有限公司 | A kind of update method of network monitoring daily record |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108399175A (en) | 2018-08-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6716727B2 (en) | Streaming data distributed processing method and apparatus | |
| CN106874348B (en) | File storage and index method and device and file reading method | |
| CN110162526B (en) | Method, device and equipment for inquiring data records in block chain type account book | |
| CN108399175B (en) | Data storage and query method and device | |
| CN113766035A (en) | Method and device for service acceptance and consensus | |
| CN107911249B (en) | Method, device and equipment for sending command line of network equipment | |
| CN106407207B (en) | Real-time newly-added data updating method and device | |
| CN109032803B (en) | Data processing method and device and client | |
| CN104572727A (en) | Data querying method and device | |
| CN107729135B (en) | Method and device for parallel data processing in sequence | |
| CN108259346B (en) | Equivalent routing table item establishing method and device | |
| CN109033360B (en) | Data query method, device, server and storage medium | |
| CN106878367B (en) | Method and device for realizing asynchronous call of service interface | |
| CN109032533B (en) | Data storage method, device and equipment | |
| CN104298687B (en) | A kind of hash partition management method and device | |
| CN111722918A (en) | Service identification code generation method and device, storage medium and electronic equipment | |
| CN109145053B (en) | Data processing method and device, client and server | |
| CN109271449A (en) | A kind of distributed storage inquiry system file-based and querying method | |
| CN114721594A (en) | Distributed storage method, device, equipment and machine readable storage medium | |
| CN109542612A (en) | A kind of hot spot keyword acquisition methods, device and server | |
| CN111400301A (en) | Data query method, device and equipment | |
| CN108664322A (en) | Data processing method and system | |
| CN107391541A (en) | A kind of real time data merging method and device | |
| CN110555020B (en) | Mapping relation establishing and data querying methods, devices and equipment | |
| CN107547382B (en) | Neighbor relation discovery 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |