CN107291869B - Distributed service system and data query method thereof - Google Patents

Distributed service system and data query method thereof Download PDF

Info

Publication number
CN107291869B
CN107291869B CN201710451567.4A CN201710451567A CN107291869B CN 107291869 B CN107291869 B CN 107291869B CN 201710451567 A CN201710451567 A CN 201710451567A CN 107291869 B CN107291869 B CN 107291869B
Authority
CN
China
Prior art keywords
data
cache
database
flag
mark
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
Application number
CN201710451567.4A
Other languages
Chinese (zh)
Other versions
CN107291869A (en
Inventor
李晓鹏
宋宇鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing 58 Information Technology Co Ltd
Original Assignee
Beijing 58 Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing 58 Information Technology Co Ltd filed Critical Beijing 58 Information Technology Co Ltd
Priority to CN201710451567.4A priority Critical patent/CN107291869B/en
Publication of CN107291869A publication Critical patent/CN107291869A/en
Application granted granted Critical
Publication of CN107291869B publication Critical patent/CN107291869B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/23—Updating
    • G06F16/2365—Ensuring data consistency and integrity
    • 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/23—Updating
    • 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/24552—Database cache management
    • 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/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
    • G06F16/2471—Distributed queries

Abstract

The invention provides a method for querying data of a distributed service system, which comprises a master database, a slave database, a cache and a marking unit, wherein when the data of the master database is updated, a mark is stored in the marking unit, and the mark is deleted after the data of the master database is synchronized to the slave database, the method comprises the following steps: a) judging whether data exist in the cache or not, if so, entering a step f; otherwise, entering the step b; b) judging whether the mark exists in the mark unit, if so, entering the step c; otherwise, entering the step d; c) querying data in the master database, and then entering step e; d) querying the slave database for data; e) writing the inquired data into the cache; f) and returning the data in the cache as a query result. The invention ensures that the data in the cache is consistent with the data of the database, and eliminates the risk of data inconsistency caused by high concurrency and master-slave synchronization delay.

Description

Distributed service system and data query method thereof
The application is filed on 14 th 04/2014 in application, the application number is CN201410148256.7, and the invention is named as a distributed service system and a divisional application of a data updating and data inquiring method thereof.
Technical Field
The invention relates to the technical field of computer network data updating, in particular to a distributed service system and a data query method thereof.
Background
In large distributed web services, as the user population continues to increase, access to information systems is increasing. In each inquiry request of the user, the information system carries out corresponding operations such as searching, data calculation and the like in the database, and then returns the result. The query volume increases, and the data processing volume of the information system also linearly increases. In order to relieve the access pressure of the database server, a database server data caching technology is developed. The caching technology has the function of temporarily storing data frequently accessed by a user, the data in the cache is a copy of the data in the data storage source, and the data can be directly returned when the user accesses the temporarily stored data again without acquiring the data from the database server, so that the burden of the database server is reduced.
The master-slave synchronization mode is a common solution, that is, two databases with completely consistent storage contents are provided, wherein one database is a master database and the other database is a slave database. All writing and updating operations are performed on the master database, all query operations are performed on the slave database, and the contents of the master database which are written or changed after updating are updated to the slave database within a certain time.
Currently, in the data updating method in the master-slave synchronization mode, when data is updated, the cache is first deleted, and then the master database of the database is updated. At this time, when data query operation is performed, firstly, the cache is queried, if the cache has a value, the cache is directly returned, if the cache has no value, the slave database of the database is queried, and the queried value is placed in the cache.
However, in such a solution, a situation may result in which the data in the cache is inconsistent with the data stored by the database, i.e., the data in the cache is old data before being updated. For example, in preparation for an update operation, the data in the cache is first deleted and then the master database is updated. If a query operation occurs before the update of the master database is completed, at this time, according to the flow of the query operation, the query operation is firstly performed in the cache, but since the data in the cache is already deleted, the query operation is performed in the slave database. Assuming that the data searched from the database is a (original data), after the search is finished, the data will be written into the cache, i.e. the cache is written into a. And the update operation updates the database to B (new data) at this time. It will happen that data (B) in the database is not consistent with data (a) in the cache, i.e. the cache holds erroneous data. If no more update occurs, the data in the cache cannot be updated to B, and the data obtained by the subsequent query operation is the error data A in the cache.
For another example, after the master database completes the update operation, for example, when data a is updated to B, a query request occurs, and the cache is queried first, and at this time, the slave database is queried because the data in the cache is deleted in preparation for the update operation and no data exists in the cache. Since there is a delay in synchronizing new data B from the master database to the slave database, when B has not yet been updated to the slave database, the data in the slave database is still a, so the queried data will be a, and then a will be written into the cache. Thus, even if the data in the database is synchronized to B later, the data queried later will be the data A queried from the cache, resulting in error.
Therefore, a new distributed service system and a new method for updating and querying data are needed to effectively avoid the old data before updating in the cache after the database is updated.
Disclosure of Invention
The invention aims to provide a method for querying data of a distributed service system, wherein the system comprises a master database, a slave database, a cache and a marking unit, a mark is stored in the marking unit when the data of the master database is updated, and the mark is deleted after the data of the master database is synchronized to the slave database, and the method comprises the following steps:
a) judging whether data exist in the cache or not, if so, entering a step f; otherwise, entering the step b;
b) judging whether the mark exists in the mark unit, if so, entering the step c; otherwise, entering the step d;
c) querying data in the master database, and then entering step e;
d) querying the slave database for data;
e) writing the inquired data into the cache;
f) and returning the data in the cache as a query result.
Preferably, the mark is a specific value given to a certain data bit of the mark unit, or data stored in the mark unit, or a created file.
Preferably, the tag unit is located in the cache.
Preferably, the system comprises:
the main database is used for storing data and supporting query operation on the data;
a slave database for storing data and updating the data stored by the master database according to the data of the master database, wherein the slave database supports query operation;
the cache is used for storing data and supporting query operation and write operation on the data, wherein when the data of the main database is updated, the data in the cache is deleted for the first time, and after the data of the main database is updated, the data in the cache is deleted again; and
the marking unit is used for storing the mark after the data in the cache is deleted for the first time, and deleting the mark after the data in the master database is synchronized to the slave database;
when data in the distributed service system is queried, firstly querying the cache, and if the data exists in the cache, returning the data in the cache as a query result; if the cache does not store data, judging whether the mark exists in the mark unit, if so, performing data query on the master database, otherwise, performing data query on the slave database, and writing the result of the query on the master database or the slave database into the cache.
Preferably, the flag in the flag cell is a specific value assigned to a certain data bit in the flag cell, and the flag is deleted to reset the data bit.
Preferably, the mark in the marking unit is the data stored in the marking unit, and the mark is the data deleted in the marking unit.
Preferably, the flag in the flag unit is one file created, and the flag is deleted as the file created.
Preferably, the tag unit is located in the cache.
The method for querying the data of the distributed service system can effectively avoid the condition that the cache still stores old data before updating after the database is updated. The data updating and data query method is particularly suitable for ensuring that the data in the cache is consistent with the data of the database under the environment of high-concurrency distributed service and master-slave databases, and eliminating the risk of data inconsistency caused by high-concurrency and master-slave synchronization delay.
Drawings
Further objects, features and advantages of the present invention will become apparent from the following description of embodiments of the invention, with reference to the accompanying drawings, in which:
fig. 1a schematically shows a block diagram of a distributed service system according to an embodiment of the invention.
Fig. 1b schematically shows a block diagram of a distributed service system according to another embodiment of the invention.
Fig. 2 schematically shows a flow chart of a distributed service system data updating method according to an embodiment of the present invention.
Fig. 3 schematically shows a flow chart of a distributed service system data query method according to an embodiment of the invention.
Detailed Description
The objects and functions of the present invention and methods for accomplishing the same will be apparent by reference to the exemplary embodiments. However, the present invention is not limited to the exemplary embodiments disclosed below; it can be implemented in different forms. The nature of the description is merely to assist those skilled in the relevant art in a comprehensive understanding of the specific details of the invention.
Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the drawings, the same reference numerals denote the same or similar parts, or the same or similar steps.
Fig. 1a schematically shows a block diagram of a distributed service system according to an embodiment of the invention. As shown in fig. 1a, a distributed service system to which an embodiment of the present invention is applied includes: master database 110, slave database 120, cache 130, and tagging unit 131. Fig. 1b schematically shows a block diagram of a distributed service system according to another embodiment of the invention. Where the tag unit 131 is located within the cache 130.
When the system updates data, the data in the master database 110 is updated first, and the slave database 120 is updated and synchronized according to the updated data in the master database 110. In particular, query operations to the master database 110 are supported, for example, in the presence of tags in the cache 130. The marks will be described later.
The slave database 120 is configured to receive the synchronous update data from the master database 1105, support query of the slave database 120 (for example, when the data to be queried is not found in the cache 130), and write the query result into the cache 130 after query.
A cache 130 supporting query operations and write operations thereto. The data in the cache 130 is deleted for the first time when the database of the master database 110 is updated, and is deleted again after the data of the master database is updated.
The marking unit 131 is used for marking that the system is in a data updating state. When the system performs data update, after the data in the cache 130 is deleted for the first time, a tag is put in the tag unit 131, and after the data in the master database is synchronized to the slave database, the tag is deleted. As shown in fig. 1a and fig. 1b, respectively, the marking unit 131 may be disposed outside the cache 130 or within the cache 130.
Preferably, a flag is put in the flag cell 131 to give a specific value to a certain data bit in the flag cell 131, and the flag is deleted to reset the data bit.
Preferably, a mark is put in the marking unit 131 to store data in the marking unit 131, such as but not limited to storing data capable of functioning as a mark, and the mark is deleted to delete the stored data.
Preferably, a mark is put in the marking unit 131 to create a file in the marking unit 131, and the file created by the mark is deleted.
When the cache 130 is queried, if the cache 130 has a query result, the query result is directly returned; if no query result exists, whether a mark exists in the mark unit 131 of the cache 130 is judged, if yes, data query is performed on the master database 110, otherwise, data query is performed on the slave database 120, after the query is completed, the query result from the master database 110 or the slave database 120 is written into the cache 130, and the query result is returned.
Fig. 2 schematically shows a flow chart of a method for data update of a distributed service system according to an embodiment of the invention. As shown in fig. 2: in step 210, when the distributed service system performs data update, the data in the cache 130 is deleted first. In the master-slave database architecture of the distributed service according to the present invention, when the database needs to be updated, the data in the master database 110 is directly updated.
In step 220, a marker is placed in the marking unit 131. The flag is placed in the flag cell, for example, a specific value is assigned to a certain data bit in the flag cell 131, for example, a value of 1 is assigned to a certain data bit in the flag cell 131. The placing of the mark in the marking unit 131 is, for example, storing data in the marking unit 131, preferably data capable of performing a marking function, for example, storing a long and complex value capable of performing an identification feature. The put mark is also for example the creation of a file.
At step 230, the data in the master database 110 is updated.
At step 240, the data in the master database 110 is synchronized to the slave database 120. According to the present invention, a synchronization operation is performed whenever there is an update operation in the master database 110 and the updated transaction request has been submitted.
At step 250, the data in the cache 130 is deleted. Specifically, the mark in the mark unit 131 is not deleted here. The purpose of deleting data in the cache 130 is to delete old data stored in the cache 130 from after step 210 to before this step. The old data specifically includes: old data written to the cache 130 from the database 120 follows step 210 and precedes step 220.
In the present embodiment, step 240 is performed first, and then step 250 is performed, but the order of the steps is not limited thereto. For example, step 250 may be performed first and then step 240 may be performed. That is, the steps 240 and 250 are only required to be after the step 230 and before the step 260. In step 260, the flag set in the flag cell 131 in step 220 is deleted. In particular, the deletion of the flag is performed after the synchronization operation of the master database 110 to the slave database 120 is completed. Here, the flag is deleted by, for example, resetting the data bit of the flag cell 131 assigned with the specific value in step 220, for example, resetting the data bit of the flag cell 131 assigned with 1 in step 220. The delete marker is, for example, the data stored in step 220 in the delete marker unit 131, preferably data capable of functioning as a marker, such as deleting the long and complex value capable of functioning as an identification feature. Also for example, the file created in step 220 is deleted.
Fig. 3 schematically shows a flow chart of a method of performing a database query after an update of a master-slave database, for example as shown in fig. 2.
As shown in fig. 3: step 310, when the database needs to be queried, firstly, querying the cache 130, judging whether the cache 130 has data to be queried, if so, entering step 360 to directly return a query result; otherwise, go to step 320.
Step 320, judging whether a mark exists in the marking unit 131, if so, entering step 330; otherwise, go to step 340. The tag is the above-mentioned tag put in the tagging unit 131 when data update is performed on the master database 110.
Step 330, query the master database 110 for data, and then proceed to step 350. When the flag is determined to exist in the flag unit 131, it indicates that the system is in the process of performing the data update operation on the master database 110, and then the master database 110 being updated needs to be directly queried to obtain the latest and correct data result.
At step 340, the data is queried from the database 120. When it is determined that the flag does not exist in the flag cell 131, it indicates that the system is not performing the data update operation on the master database 110. Since the updated data 10 of the master database 110 is synchronized to the slave database 120 after each database update operation, when no mark exists in the marking unit 131, it indicates that the master database 110 and the slave database 120 are synchronized, and only the slave database 120 needs to be queried to obtain the latest and correct data result.
Step 350, writing the queried data into the cache 130. The write operation can ensure that the data in the cache is consistent with the data in the master database and the slave database, thereby ensuring that only the cache is required to be queried to obtain a correct and latest data result in the subsequent 15-database query when the data exists in the cache.
And step 360, returning the data in the cache as a query result.
According to the method and the system for updating the database of the master database and the slave database in the distributed service, the possibility that old data before updating still exists in the cache after the updating of the database is finished can be effectively avoided. The database updating and inquiring method is particularly suitable for the environment of high-concurrency distributed service and master-slave databases, ensures that the data in the cache is consistent with the data of the databases, and eliminates the risk of data inconsistency caused by high-concurrency and master-slave synchronization delay.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

Claims (8)

1. A method for querying data in a distributed service system, the system comprising a master database, a slave database, a cache and a tag unit, wherein when data in the master database is updated, a tag is stored in the tag unit, and after the data in the master database is synchronized with the slave database, the tag is deleted, the method comprising the following steps:
a) judging whether data exist in the cache or not, if so, entering a step f); otherwise, entering the step b);
b) judging whether the mark exists in the mark unit, if so, entering the step c); otherwise, entering step d);
c) querying the master database for data, and then proceeding to step e);
d) querying the slave database for data;
e) writing the inquired data into the cache;
f) and returning the data in the cache as a query result.
2. The method of claim 1, wherein the flag is a specific value assigned to a certain data bit of the flag cell, or data stored in the flag cell, or a created file.
3. The method of claim 1, wherein the tag unit is located in the cache.
4. A distributed service system for use in the method of any one of claims 1 to 3, the system comprising:
the main database is used for storing data and supporting query operation on the data;
a slave database for storing data and updating the data stored by the master database according to the data of the master database, wherein the slave database supports query operation;
the cache is used for storing data and supporting query operation and write operation on the data, wherein when the data of the main database is updated, the data in the cache is deleted for the first time, and after the data of the main database is updated, the data in the cache is deleted again; and
the marking unit is used for storing the mark after the data in the cache is deleted for the first time, and deleting the mark after the data in the master database is synchronized to the slave database;
when data in the distributed service system is queried, firstly querying the cache, and if the data exists in the cache, returning the data in the cache as a query result; if the cache does not store data, judging whether the mark exists in the mark unit, if so, performing data query on the master database, otherwise, performing data query on the slave database, and writing the result of the query on the master database or the slave database into the cache.
5. The system of claim 4, wherein the flag in the flag cell is a specific value assigned to a data bit in the flag cell, and wherein the flag is deleted and the data bit is reset.
6. The system of claim 4, wherein the flag in the flag cell is to store data in the flag cell, and wherein the flag is to delete the data stored in the flag cell.
7. The system of claim 4, wherein the flag in the flag cell is one file created and wherein the flag is deleted to delete the created file.
8. The system of claim 4, wherein the tag unit is located in the cache.
CN201710451567.4A 2014-04-14 2014-04-14 Distributed service system and data query method thereof Active CN107291869B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710451567.4A CN107291869B (en) 2014-04-14 2014-04-14 Distributed service system and data query method thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710451567.4A CN107291869B (en) 2014-04-14 2014-04-14 Distributed service system and data query method thereof
CN201410148256.7A CN103955486B (en) 2014-04-14 2014-04-14 Distribution service and its data update, the method for data query

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN201410148256.7A Division CN103955486B (en) 2014-04-14 2014-04-14 Distribution service and its data update, the method for data query

Publications (2)

Publication Number Publication Date
CN107291869A CN107291869A (en) 2017-10-24
CN107291869B true CN107291869B (en) 2020-04-24

Family

ID=51332761

Family Applications (2)

Application Number Title Priority Date Filing Date
CN201410148256.7A Active CN103955486B (en) 2014-04-14 2014-04-14 Distribution service and its data update, the method for data query
CN201710451567.4A Active CN107291869B (en) 2014-04-14 2014-04-14 Distributed service system and data query method thereof

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN201410148256.7A Active CN103955486B (en) 2014-04-14 2014-04-14 Distribution service and its data update, the method for data query

Country Status (1)

Country Link
CN (2) CN103955486B (en)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104346468A (en) * 2014-11-14 2015-02-11 浪潮(北京)电子信息产业有限公司 Method and device for realizing concurrent I/O (Input/Output) in database system
CN104881444B (en) * 2015-05-14 2018-08-14 微梦创科网络科技（中国）有限公司 The method and system of cache server are updated in website
CN105260475B (en) * 2015-10-30 2019-08-16 努比亚技术有限公司 A kind of data search method, date storage method and related device
CN106897303B (en) * 2015-12-18 2020-09-15 北京国双科技有限公司 Data query method and device
CN105608229A (en) * 2016-01-29 2016-05-25 锐达互动科技股份有限公司 System and method for synchronizing master-slave databases
CN107566434B (en) * 2016-07-01 2022-01-07 北京京东尚科信息技术有限公司 Cache data reading and writing method and system, electronic equipment and computer readable medium
CN106202387B (en) * 2016-07-08 2019-05-21 苏州超块链信息科技有限公司 A kind of data consistency concurrent maintenance method
CN106407351A (en) * 2016-09-05 2017-02-15 乐视控股（北京）有限公司 Data processing method and device applied to database
CN108509450B (en) * 2017-02-27 2022-04-12 北京京东尚科信息技术有限公司 Method and device for processing high-concurrency update of database
CN107832401B (en) * 2017-11-01 2021-07-16 郑州云海信息技术有限公司 Database data access method, system, device and computer readable storage medium
CN110019340A (en) * 2017-12-08 2019-07-16 北京新媒传信科技有限公司 Data storage/read method, apparatus and system
CN108897495B (en) * 2018-06-28 2023-10-03 北京五八信息技术有限公司 Cache updating method, device, cache equipment and storage medium
CN109358805B (en) * 2018-09-03 2021-11-30 中新网络信息安全股份有限公司 Data caching method
CN109710688B (en) * 2018-11-26 2021-10-08 福建天泉教育科技有限公司 Data real-time comparison and verification method and message middleware
CN109828980A (en) * 2019-02-19 2019-05-31 北京字节跳动网络技术有限公司 Data cache method, device, terminal and storage medium
CN109871388A (en) * 2019-02-19 2019-06-11 北京字节跳动网络技术有限公司 Data cache method, device, whole electronic equipment and storage medium
CN109992695B (en) * 2019-04-10 2021-08-27 北京奇艺世纪科技有限公司 Video information query method and device
CN110427386B (en) * 2019-08-05 2023-09-19 广州方硅信息技术有限公司 Data processing method, device and computer storage medium
CN111177197B (en) * 2019-12-26 2023-03-14 北京仁科互动网络技术有限公司 Cache processing method and system
CN113760860B (en) * 2020-11-12 2023-09-22 北京京东振世信息技术有限公司 Data reading method and device
CN112364061A (en) * 2020-11-18 2021-02-12 浪潮云信息技术股份公司 Mysql-based high-concurrency database access method
CN113094430B (en) * 2021-03-25 2023-10-03 北京达佳互联信息技术有限公司 Data processing method, device, equipment and storage medium
CN113360571A (en) * 2021-06-03 2021-09-07 广东电网有限责任公司 Characteristic mark-based power grid monitoring system memory database relation database synchronization method
CN113704267A (en) * 2021-08-31 2021-11-26 平安普惠企业管理有限公司 Data query method, system, equipment and storage medium based on elastic search

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5737536A (en) * 1993-02-19 1998-04-07 Borland International, Inc. System and methods for optimized access in a multi-user environment
CN101576921A (en) * 2009-06-15 2009-11-11 用友软件股份有限公司 Data query system and data query engine device
CN102081625A (en) * 2009-11-30 2011-06-01 中国移动通信集团北京有限公司 Data query method and query server
CN102508854A (en) * 2011-09-29 2012-06-20 畅捷通信息技术股份有限公司 Data access device and method
CN102521406A (en) * 2011-12-26 2012-06-27 中国科学院计算技术研究所 Distributed query method and system for complex task of querying massive structured data
CN102521405A (en) * 2011-12-26 2012-06-27 中国科学院计算技术研究所 Massive structured data storage and query methods and systems supporting high-speed loading
CN103345502A (en) * 2013-07-01 2013-10-09 曙光信息产业(北京)有限公司 Transaction processing method and system of distributed type database

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100454311C (en) * 2006-12-25 2009-01-21 华为技术有限公司 Data synchronous method and device based on SQL

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5737536A (en) * 1993-02-19 1998-04-07 Borland International, Inc. System and methods for optimized access in a multi-user environment
CN101576921A (en) * 2009-06-15 2009-11-11 用友软件股份有限公司 Data query system and data query engine device
CN102081625A (en) * 2009-11-30 2011-06-01 中国移动通信集团北京有限公司 Data query method and query server
CN102508854A (en) * 2011-09-29 2012-06-20 畅捷通信息技术股份有限公司 Data access device and method
CN102521406A (en) * 2011-12-26 2012-06-27 中国科学院计算技术研究所 Distributed query method and system for complex task of querying massive structured data
CN102521405A (en) * 2011-12-26 2012-06-27 中国科学院计算技术研究所 Massive structured data storage and query methods and systems supporting high-speed loading
CN103345502A (en) * 2013-07-01 2013-10-09 曙光信息产业(北京)有限公司 Transaction processing method and system of distributed type database

Also Published As

Publication number Publication date
CN103955486B (en) 2017-08-01
CN103955486A (en) 2014-07-30
CN107291869A (en) 2017-10-24

Similar Documents

Publication Publication Date Title
CN107291869B (en) Distributed service system and data query method thereof
US9251163B2 (en) File sharing system and file sharing method
US8924365B2 (en) System and method for range search over distributive storage systems
CN112363979B (en) Distributed index method and system based on graph database
CN109189852B (en) Data synchronization method and device for data synchronization
US20140297592A1 (en) Computer-readable medium storing program and version control method
WO2015154694A1 (en) System and method for massively parallel processing database
WO2015081780A1 (en) Columnar database processing method and processing device
US9384202B1 (en) Gateway module to access different types of databases
CN106255962B (en) System and method for improved data structure storage
US8600962B2 (en) Transaction processing device, transaction processing method, and transaction processing program
CN109815240A (en) For managing method, apparatus, equipment and the storage medium of index
CN114048269B (en) Method and device for synchronously updating metadata in distributed database
CN114185991A (en) Method and related device for realizing data synchronization based on distributed database
KR101424568B1 (en) Client and database server for resumable transaction and method thereof
CN112699187A (en) Associated data processing method, device, equipment, medium and product
CN111797119A (en) Caching device, caching system and caching method
CN109491988B (en) Data real-time association method supporting full-scale updating
CN111949725A (en) Data query method and device, electronic equipment and computer readable storage medium
CN108959548B (en) Service request processing method and device
WO2016101528A1 (en) Method and device for processing data in memory database
CN113626449A (en) Data storage method, data query method and related equipment
CN113849574A (en) Data processing method, front end and computer readable storage medium
JP2016194826A (en) Database processing control method, processing control program and database server
CN113407209B (en) Configuration data updating 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
CP02 Change in the address of a patent holder

Address after: Room 210-02, 2nd Floor, Block C, Office Building, Comprehensive Service Zone, Nangang Industrial Zone, Economic and Technological Development Zone, Binhai New Area, Tianjin 300450

Patentee after: 58Tongcheng Information Technology Co.,Ltd.

Address before: Building 105, Yard 10, Jiuxianqiao North Road, Jiangtai, Chaoyang District, Beijing 100015

Patentee before: 58Tongcheng Information Technology Co.,Ltd.

CP02 Change in the address of a patent holder