Author Topic: BigChainDB - scalable, 1M writes, petabytes of capacity, priv and open chains  (Read 888 times)

0 Members and 1 Guest are viewing this topic.

Offline Akado

  • Hero Member
  • *****
  • Posts: 2752
    • View Profile
  • BitShares: akado
https://www.bigchaindb.com/

Does anyone know this? Just found it. It seems it can do 1M transactions vs ours 100k  :P

docs
https://bigchaindb.readthedocs.org/en/develop/

whitepaper
https://www.bigchaindb.com/whitepaper/bigchaindb-whitepaper.pdf



BigchainDB fills a gap in the decentralization ecosystem: a decentralized database, at scale. It points to performance of 1 million writes per second throughput, storing petabytes of data, and sub-second latency.

The BigchainDB design starts with a distributed database (DB), and through a set of innovations adds blockchain characteristics: decentralized control, immutability, and creation & movement of digital assets. BigchainDB inherits characteristics of modern distributed databases: linear scaling in throughput and capacity with the number of nodes, a full-featured NoSQL query language, efficient querying, and permissioning. Being built on an existing distributed DB, it also inherits enterprise-hardened code for most of its codebase.

Scalable capacity means that legally binding con- tracts and certificates may be stored directly on the blockchain database. The permissioning system enables configurations ranging from private enterprise blockchain databases to open, public blockchain databases. BigchainDB is complementary to decentralized processing platforms like Ethereum, and decentralized file systems like InterPlanetary File System (IPFS).

This paper describes technology perspectives that led to the BigchainDB design: traditional blockchains, distributed databases, and a case study of the domain name system (DNS). We introduce a concept called blockchain pipelining, which is key to scalability when adding blockchainlike characteristics to the distributed DB. We present a thorough description of BigchainDB, a detailed analysis of latency, and experimental results. The paper concludes with a description of use cases.
« Last Edit: February 11, 2016, 02:38:19 am by Akado »
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Theirs is 1M writes per second while we are talking about transaction-per-second (includes network and operation) here.

Interesting article. Thanks for sharing.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline sittingduck

  • Sr. Member
  • ****
  • Posts: 246
    • View Profile
Interesting.  It would be nice to see apples to apples comparison.

Offline bytemaster

BigChainDB is an impressive solution and certainly has a place in the market. But let's think about things from a purely information-theory point of view.

BCDB scales by adding nodes. This means the nodes are not processing the SAME information, instead each node is processing a subset of the information. 

I can reach 1 million transactions per second with Graphene through having 10 chains each operating on an independent set of data.  It could probably even all run on one computer.

There is inherently sequential business logic that cannot take advantage of BCDB's parallelism approach.


For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.