Topic: KahaDB vs LevelDB: ActiveMQ // bitcoin core (Read 384 times)
Yes, I was actually thinking of Kafka, but thought it might be confusing to the forum for me to bring that up right away. We've also had good experiences with using it.
So most Ethereum clients also use Leveldb. But its at a very low level, just the underlying storage for the network. It doesn't effect the design of the actual crypto design. Different clients could use different underlying databases. The main benefit is performance/error correction/support for multithreading. I don't think there is a strong compelling reason to switch to KahaDB. It probably makes more sense for Kafka cause thats an incredibly high throughput system. I regularly push 100gbs an hour through Kafka, which is nearly the size of the whole bitcoin blockchain.
I'm guessing many contributors have followed this, but ActiveMQ shifted from LevelDB to KahaDB.
http://blog.klocwork.com/open-source/activemq-community-deprecates-leveldb-what-you-need-to-know/
I'd be curious the Bitcoin Forum's sense for LevelDB vs other options. We're developing some new ideas for our bitcoin network, and are considering also using KahaDB. Any pros/cons or issues that might be good to consider?
http://blog.klocwork.com/open-source/activemq-community-deprecates-leveldb-what-you-need-to-know/
I'd be curious the Bitcoin Forum's sense for LevelDB vs other options. We're developing some new ideas for our bitcoin network, and are considering also using KahaDB. Any pros/cons or issues that might be good to consider?
Jump to: