CN111309783A - Cochain data reading system - Google Patents
Cochain data reading system Download PDFInfo
- Publication number
- CN111309783A CN111309783A CN202010085410.6A CN202010085410A CN111309783A CN 111309783 A CN111309783 A CN 111309783A CN 202010085410 A CN202010085410 A CN 202010085410A CN 111309783 A CN111309783 A CN 111309783A
- Authority
- CN
- China
- Prior art keywords
- uplink data
- backup server
- block chain
- data
- uplink
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
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/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2471—Distributed queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Fuzzy Systems (AREA)
- Mathematical Physics (AREA)
- Probability & Statistics with Applications (AREA)
- Software Systems (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a cochain data reading system which comprises a backup server and a block chain system, wherein the backup server backs up cochain data to obtain same first cochain data and second cochain data, the first cochain data is sent to the block chain system, the second cochain data is stored in the backup server, whether the second cochain data corresponding to a cochain data reading instruction exists in the backup server or not is judged according to the cochain data reading instruction, the cochain data is obtained from a corresponding position according to a judgment result, and finally the obtained cochain data is returned. Because the uplink data is backed up, even if the uplink data is not recorded by the block chain temporarily, the uplink data can be searched from the backup server, so that the data does not need to be waited for successfully uplink, the time occupied by data reading is reduced, and the reading efficiency is further improved.
Description
Technical Field
The invention relates to a system for reading uplink data.
Background
With the development of internet technology, the blockchain has been widely applied to data storage and interaction due to the advantages of decentralization, openness, security, autonomy, and the like. When using a chain of blocks to store data, the data needs to be stored into the blocks. When a user adopts the existing uplink data reading mode, the uplink data can be read from the block chain only after the uplink data is recorded by the block chain, the data reading time is longer, and the efficiency is lower.
Disclosure of Invention
The invention aims to provide an uplink data reading system, which is used for solving the problems that when a user adopts the existing uplink data reading mode, the uplink data can be read from a block chain only after the uplink data is recorded by the block chain, the data reading time is long, and the efficiency is low.
In order to solve the problems, the invention adopts the following technical scheme:
a cochain data reading system comprises a backup server and a block chain system, wherein the backup server is connected with the block chain system;
the backup server backs up the uplink data to obtain the same first uplink data and second uplink data, and the backup server sends the first uplink data to a block chain system, wherein the block chain system comprises a memory database, and the memory database is used for storing the first uplink data; the backup server stores the second uplink data into the backup server;
when the block chain system receives an uplink data reading instruction, judging whether second uplink data corresponding to the uplink data reading instruction exists in the backup server or not according to the uplink data reading instruction;
if second uplink data corresponding to the uplink data reading instruction exists in the backup server, acquiring the second uplink data from the backup server;
if the backup server does not have second uplink data corresponding to the uplink data reading instruction, acquiring first uplink data corresponding to the uplink data reading instruction from the block chain system;
the block chain system returns the acquired uplink data.
Optionally, the block chain system determines whether the first uplink data is successfully uplink;
and if the first uplink data is successfully uplink, deleting the second uplink data from the backup server.
The invention has the beneficial effects that: the backup server backups the uplink data to obtain two identical uplink data, and the two uplink data are respectively stored in the block chain system and the backup server. When the block chain system receives an uplink data reading instruction, whether second uplink data corresponding to the uplink data reading instruction exists in the backup server or not is judged according to the uplink data reading instruction, and if the second uplink data corresponding to the uplink data reading instruction exists in the backup server, the second uplink data are obtained from the backup server; if not, acquiring first uplink data corresponding to the uplink data reading instruction from the block chain system. Because the uplink data is backed up, even if the uplink data is not recorded by the block chain temporarily, the uplink data can be searched from the backup server, so that the data does not need to be waited for successfully uplink, the time occupied by data reading is reduced, and the reading efficiency is further improved.
Drawings
In order to more clearly illustrate the technical solution of the embodiment of the present invention, the drawings needed to be used in the embodiment will be briefly described as follows:
FIG. 1 is a block diagram of an uplink data reading system.
Detailed Description
As shown in fig. 1, the present embodiment provides an uplink data reading system, which includes a backup server and a blockchain system, wherein the backup server is connected to the blockchain system.
The backup server may be a hardware server device such as: is a single server or a combined server system composed of a plurality of servers; or may be a virtual software device formed of software modules. Similarly, the blockchain system may be a hardware device, such as: is a single server or a combined server system composed of a plurality of servers; or may be a virtual software device formed of software modules. The backup server and the blockchain system can be connected in a wired communication mode or in a wireless communication mode.
The backup server is configured to backup the received uplink data, and in this embodiment, the backup server receives the uplink data through the client. The client can be a mobile phone, a desktop computer, a tablet computer, a notebook computer, and the like. The number of the clients is determined according to the actual application scenario, and may be one client or a plurality of clients.
When the client needs to record some data in the blockchain, the uplink data is output to the backup server. The backup server backs up the received uplink data to obtain the same first uplink data and second uplink data, specifically: and copying the uplink data, wherein the original uplink data is the first uplink data, and the copied data is the second uplink data.
The backup server sends the first uplink data to the blockchain system. The block chain system comprises a memory database, wherein the memory database is used for storing the first uplink data. The writing speed of the memory database is far higher than that of the traditional disk database, and therefore, the uplink data are stored in the memory database, and the storage efficiency can be effectively improved. Moreover, even if uplink data is written into the memory database frequently, the performance of the block chain is not affected.
The backup server stores the second uplink data into the backup server, and the storage manner in the backup server is set according to actual needs, for example, a memory database is also set in the backup server and used for storing the second uplink data. Or, a designated storage area is set in the backup server, and the designated storage area may be set according to actual requirements, may be set as a cache area, or may be set as a persistent storage area.
When the block chain system receives an uplink data read command, for example: when the ue needs to query the uplink data, it can send an uplink data reading command to the blockchain system (then, the ue connects to the backup server and the blockchain system, specifically, two ues can be set, where the first ue connects to the backup server, the second ue connects to the blockchain system, the first ue is used to send the uplink data, and the second ue is used to send the uplink data reading command).
The block chain system judges whether second uplink data corresponding to the uplink data reading instruction exists in the backup server according to the uplink data reading instruction, namely the block chain system judges whether uplink data corresponding to the uplink data reading instruction exists in the backup server according to the uplink data reading instruction: if the backup server has second uplink data corresponding to the uplink data reading instruction, acquiring the second uplink data from the backup server; if the backup server does not have the second uplink data corresponding to the uplink data reading instruction, acquiring the first uplink data corresponding to the uplink data reading instruction from the block chain system.
After the block chain system acquires the uplink data, the block chain system returns the acquired uplink data, and specifically sends the uplink data to a publisher of the uplink data reading instruction, namely, the second client.
Because the uplink data is backed up, even if the uplink data is not recorded by the block chain temporarily, the second uplink data can be searched from the backup server, so that the data uplink does not need to be waited, the time occupied by data reading is reduced, and the reading efficiency is further improved.
Further, the block chain system can also determine whether the first uplink data is successfully uplink, if the first uplink data is successfully uplink, which indicates that the uplink data can be directly acquired from the block chain system, the uplink data does not need to be acquired from the backup server, and at this time, in order to save the storage space of the backup server, the second uplink data is deleted from the backup server.
In addition, if the backup server receives a large amount of uplink data in a short time, the backup server may be blocked and uplink efficiency is affected, therefore, when the backup server receives the uplink data, the backup server can queue up to receive the uplink data in a first-in first-out manner, and then sequentially extract the uplink data from the queue to perform uplink operation, thereby avoiding backup server blocking caused by excessive uplink data and improving uplink efficiency.
The above-mentioned embodiments are merely illustrative of the technical solutions of the present invention in a specific embodiment, and any equivalent substitutions and modifications or partial substitutions of the present invention without departing from the spirit and scope of the present invention should be covered by the claims of the present invention.
Claims (2)
1. An uplink data reading system is characterized by comprising a backup server and a block chain system, wherein the backup server is connected with the block chain system;
the backup server backs up the uplink data to obtain the same first uplink data and second uplink data, and the backup server sends the first uplink data to a block chain system, wherein the block chain system comprises a memory database, and the memory database is used for storing the first uplink data; the backup server stores the second uplink data into the backup server;
when the block chain system receives an uplink data reading instruction, judging whether second uplink data corresponding to the uplink data reading instruction exists in the backup server or not according to the uplink data reading instruction;
if second uplink data corresponding to the uplink data reading instruction exists in the backup server, acquiring the second uplink data from the backup server;
if the backup server does not have second uplink data corresponding to the uplink data reading instruction, acquiring first uplink data corresponding to the uplink data reading instruction from the block chain system;
the block chain system returns the acquired uplink data.
2. The system according to claim 1, wherein said block chain system determines whether said first uplink data is successfully uplink;
and if the first uplink data is successfully uplink, deleting the second uplink data from the backup server.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010085410.6A CN111309783A (en) | 2020-02-10 | 2020-02-10 | Cochain data reading system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010085410.6A CN111309783A (en) | 2020-02-10 | 2020-02-10 | Cochain data reading system |
Publications (1)
Publication Number | Publication Date |
---|---|
CN111309783A true CN111309783A (en) | 2020-06-19 |
Family
ID=71159226
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010085410.6A Pending CN111309783A (en) | 2020-02-10 | 2020-02-10 | Cochain data reading system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111309783A (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180039667A1 (en) * | 2016-08-05 | 2018-02-08 | Chicago Mercantile Exchange Inc. | Systems and methods for blockchain rule synchronization |
CN107704196A (en) * | 2017-03-09 | 2018-02-16 | 上海亿账通区块链科技有限公司 | Block chain data-storage system and method |
CN109739843A (en) * | 2018-12-26 | 2019-05-10 | 篱笆墙网络科技有限公司 | Block chain data read-write method, system, equipment and storage medium |
CN110753084A (en) * | 2019-09-06 | 2020-02-04 | 平安普惠企业管理有限公司 | Uplink data reading method, cache server and computer readable storage medium |
-
2020
- 2020-02-10 CN CN202010085410.6A patent/CN111309783A/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180039667A1 (en) * | 2016-08-05 | 2018-02-08 | Chicago Mercantile Exchange Inc. | Systems and methods for blockchain rule synchronization |
CN107704196A (en) * | 2017-03-09 | 2018-02-16 | 上海亿账通区块链科技有限公司 | Block chain data-storage system and method |
CN109739843A (en) * | 2018-12-26 | 2019-05-10 | 篱笆墙网络科技有限公司 | Block chain data read-write method, system, equipment and storage medium |
CN110753084A (en) * | 2019-09-06 | 2020-02-04 | 平安普惠企业管理有限公司 | Uplink data reading method, cache server and computer readable storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108319654B (en) | Computing system, cold and hot data separation method and device, and computer readable storage medium | |
CN104077380B (en) | A kind of data de-duplication method, apparatus and system | |
CN102609360B (en) | Data processing method, data processing device and data processing system | |
US10824362B2 (en) | File migration to persistent memory | |
CN111400083B (en) | Data storage method and system and storage medium | |
WO2019001521A1 (en) | Data storage method, storage device, client and system | |
CN109710185A (en) | Data processing method and device | |
CN101582076A (en) | Data de-duplication method based on data base | |
CN101551808B (en) | Technology for supporting multi-process embedded tree-based databases | |
CN103516549B (en) | A kind of file system metadata log mechanism based on shared object storage | |
CN112799595B (en) | Data processing method, device and storage medium | |
US8572338B1 (en) | Systems and methods for creating space-saving snapshots | |
KR20180061493A (en) | Recovery technique of data intergrity with non-stop database server redundancy | |
CN103019891A (en) | Method and system for restoring deleted file | |
CN111666046B (en) | Data storage method, device and equipment | |
CN111240879B (en) | SAS card firmware log collection method, system, device and storage medium | |
CN111125002B (en) | Data backup archiving method and system based on distributed storage | |
CN108021562B (en) | Disk storage method and device applied to distributed file system and distributed file system | |
US20230142948A1 (en) | Techniques for managing context information for a storage device | |
CN111309783A (en) | Cochain data reading system | |
WO2023070462A1 (en) | File deduplication method and apparatus, and device | |
US9646014B1 (en) | Systems and methods for selective defragmentation | |
CN103064926B (en) | Data processing method and device | |
CN109582241B (en) | Board card and method for realizing performance acceleration of mechanical hard disk | |
CN110209343B (en) | Data storage method, device, server and storage medium |
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 | ||
WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200619 |
|
WD01 | Invention patent application deemed withdrawn after publication |