What does "Document-oriented" vs. Key-Value mean when talking about MongoDB vs Cassandra? -
Do you buy at a KV store with a document-based NoSQL option, and vice versa?
A key-value store provides the simplest possible data model and Its name suggests: This is a storage system that stores values indexed by a key, you are limited to the query by the key and the value is opaque , about the store anything Do not know this allows for very fast reading and writing operations (a simple disk) Kses) and I see this model as a non-volatile cache (that is well suited if you need instant access to data with long-lasting).
An document-oriented database increases the previous model and the value is stored in an structured format (a document, hence the name) that can understand the database is. For example, a document may be a blog post and comments and tags stored in a denormalized manner, since the data is transparent , store more work (Such as the indexing field of the document) and you are not limited to the query by the key. As I have indicated, such a database allows the data from the whole page to be obtained from the same query and is well-suited for content-oriented applications (which is why big sites like Facebook or Amazon are like them) .
Other types of NoSQL databases include column oriented stores , graph databases and even object databases