4 ms·
I think one major distinction is that Foundation DB can be used to build most of the databases you mentioned above because of its architecture.
by owaislone 8y ago
I think one major distinction is that Foundation DB can be used to build most of the databases you mentioned above because of its architecture.
- marknadal 8y agoI'm pretty sure that is true the other way around though: Back in 2011 I built a couple DBs with Redis, and I've definitely seen people swapping other databases (MySQL, MongoDB, etc.) storage engine for RocksDB and others. I also know the storage engine we wrote (Radix Storage Engine) could be used to build LevelDB and Cassandra on top. Even Cockroach makes for a pretty solid storage engine. Could you give an example of why you couldn't use VoltDB to get FoundationDB like properties?
- owaislone 8y agoIt is possible to write code to add a compatibility layer on top of any DB to make it work like any other DB. Foundation DB's architecture specifically accounts for this. It was designed from the ground up to allow building different interfaces/layers. We can write compilers for any language to compile it to Python bytecode. That does not make python VM and .NET CLR the same thing. CLR clearly has a design goal of allowing multiple languages to run.