2009年1月14日 · Document based databases have a big advantage over relational databases as they do not require defining a schema upfront- before being able to enter any data. Also, you should use a document database if your data is not relational and cannot be stored in a table but rather is a set of images, or for example newspaper articles.

2008年12月3日 · And I'm begining to think that a Document-based database isn't the best choice to address these requirements. Furthermore, I can't imagine a use for a Document based database (maybe my imagination is too limited). Can you explain to me if I am asking pears from an elm when I try to use a Document oriented database for these requirements?

2012年1月11日 · Document Based doesn't necessarily mean they are stored entirely on file system. Some parts can still be held in memory like an index. Document based only means the database stores data in packages (like sheets of paper where every sheet is a dataset and you can write freely on it) instead of a very specific structure like a table.

You could implement some kind of key/value-store on top of MySQL without too much work, or use something like Friendly, but going for a proper document database is probably a much simpler way. MongoDB would be my choice, but there's a lot of things to consider, and others may say that Cassandra would be better.

2009年12月18日 · This points out why document-oriented databases exist. They are designed to solve a problem that the relational paradigm has chosen not to support. But document-oriented databases don't do some of the cool things that relational databases do, like referential integrity and even data type coherency.

Why should I use document based database instead of relational database? Pros/Cons of document based database vs relational database; I don't know much about Google's Bigtable but am wondering what the difference between Google's Bigtable and relational databases like MySQL is. What are the limitations of both?

Ayende has given a nice explanation regarding the difference between Key-Value and Document database: A document database is, at its core, a key/value store with one major exception. Instead of just storing any blob in it, a document db requires that the data will be store in a format that the database can understand (i.e. JSON, XML etc). In ...

2015年3月24日 · Don’t document the obvious – don’t write description “Document date” for document.date column. If there’s nothing meaningful to add just leave it blank, If objects stored in tables have types or statuses it’s good to list them in general description of a table,

In one case the "value" is opaque the database doesn't have any knowledge of what one puts inside in the value - one can query only by the key. In the other case ("document") the database understands what's put inside the value a bit better and indexes etc can be generated based on some attributes of the value and queried for later.. –

We store an "action history" against the document. This tracks views, whether someone emails the document from within the system, and other "future" functionality (e.g. faxing). We have control over the document load process, so we can manipulate the data however it needs to be to get it in the document store (e.g. assign unique IDs).