3 ms·
I would go further than just saying "reasonably efficient and powerful". More like "extremely powerful and optimized". No offense to the grandparent, but that
by dasil003 18y ago
I would go further than just saying "reasonably efficient and powerful". More like "extremely powerful and optimized".
No offense to the grandparent, but that comment strikes me as a direct result of the hype around these key-value store DBs. The idea that you could build out a relational database using a key-value store as the backend and the end result would somehow have the underlying system's scalability properties needs to be shot down with extreme prejudice.
The philosophy behind a key-value store DB is that, if we don't need 99% of the powerful features and ad-hoc queries of a relational database, we can build something that scales much better. There is some (growing) subset of relational functionality that can easily be implemented on top of a key-value store, but the developer better know what that is.
Emulating a full-on relational database is not going to perform at anywhere near the level of a real relational database. You'd be better off working on the problem of better ways of replicating and sharding regular relational databases rather than conflating two different models with competing assumptions.