I'm unclear how this is any different from a centralized mongodb as a service platform. It seems that it doesn't offer any proof of work related security or consensus building other than a centralized "trust our cluster" policy [1].<p>[1] <a href="https://docs.bigchaindb.com/en/latest/bft.html" rel="nofollow">https://docs.bigchaindb.com/en/latest/bft.html</a>
I find it very amusing that "scalable blockchain database" is the core selling point here. I must be experiencing buzzword fatigue I think. Why would I want to Chuck my boring MySQL installation for this?
Some types of data need to be geographically stay in a certain area. For example, European PII data cannot be hosted on servers outside of the EU. That's easy to handle if you're using AWS for example.<p>How can a company comply to these kinds of laws using a distributed system like BigChainDB? Is there a some kind of geo fencing possibility?
just a suggestion but it might be worth having in your FAQs some technical questions like "why would I want to use this over a SQL alternative?" and "what kind of applications can I build with this?"
"Scaleable BlockChain" is redundant, isn't it? Same with "BlockChain Database"?<p>The abstract also seems to imply that this in fact IS NOT a blockchain?
What if I don’t need a scalable blockchain, but I need a tamper-proof persistent ledger? Are there tools that are lighter-weight that can help me there?