1. What have the authors contributed in "Blockchaindb - a shared database on blockchains" ?
In this paper the authors present BlockchainDB, which leverages blockchains as a storage layer and introduces a database layer on top that extends blockchains by classical data management techniques ( e. g., sharding ) as well as a standardized query interface to facilitate the adoption of blockchains for data sharing use cases.. The authors show that by introducing the additional database layer, they are able to improve the performance and scalability when using blockchains for data sharing and also massively decrease the complexity for organizations intending to use blockchains for data sharing.
read more
2. What are the future works in "Blockchaindb - a shared database on blockchains" ?
In future, the authors thus want to extend the query interface to shared tables to full SQL with verifiable transactional semantics.
read more
3. How does the storage layer detect failed transactions?
in order to detect failed/rejected transactions, the storage layer still has to poll the blockchain regularly for the transaction status.
read more
4. What is the effect of a lag on the faster peer?
In general, the authors see that if ∆e is set to a value smaller than the lag, then the faster peer is always slowed down by the slower peer which decreases the overall throughput.
read more
