简体   繁体   English

Hyperledger Fabric:是否可以在不使区块链饱和的情况下保存数百万个位置寄存器?

[英]Hyperledger Fabric: Is it possible to save milions of registers of locations without saturate the blockchain?

The title practically says everything. 标题几乎说明了一切。

In a near future I'm going to implement a real-time tracking system using possibly, a blockchain, and for certain reasons Hyperledger Fabric seems to be the chosen technology. 在不久的将来,我将使用一个可能的区块链来实现实时跟踪系统,并且出于某些原因,Hyperledger Fabric似乎是首选技术。 After the information is recorded, it should be accessible in a map in a web application. 记录信息之后,应该可以在Web应用程序的地图中访问它。

So the question is: If we save every one or two minutes the location of a truck to the blockchain using gps, it will hurt the general performance of the blockchain in a near future? 所以问题是:如果我们使用gps将卡车的位置每隔一两分钟保存到区块链上,会在不久的将来损害区块链的整体性能吗? (milions and milions of registers) (数以百万计的寄存器)

In the end I have to decide if I should save this information in the blockchain or, knowing that it would cause some serious issues, leave that information out of it and use an hybrid system with a classic database for that and a blockchain for other functionalities that won't cause performance issues. 最后,我必须决定是否应该将此信息保存在区块链中,或者在知道会导致一些严重问题的情况下,将该信息排除在外,并使用具有经典数据库和其他功能的区块链的混合系统不会导致性能问题。

Thanks. 谢谢。

There is no storage limitation on the Fabric Ledger other than the disk space. 除了磁盘空间外,Fabric Ledger上没有存储限制。 The current value of a key (say, the latest position of the truck)can be read via Fabric query which are saved in the world state for quick retrieval. 钥匙的当前值(例如,卡车的最新位置)可以通过Fabric查询读取,并保存在世界状态中以便快速检索。 There is also mechanism to look up the history of a key quickly via the historyDB that Fabric maintains. 还有一种机制可以通过Fabric维护的historyDB快速查找密钥的历史记录。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM