Updated Database System (markdown)

Noah 2014-09-11 23:22:45 -07:00
parent fc2146d670
commit 03067c1956

@ -19,6 +19,8 @@ The document URIs are hierarchical and that's how the database is organized. Exa
* `blog/entries/172` - the blog post with ID #172 * `blog/entries/172` - the blog post with ID #172
* `blog/index` - an index (high level summary) of all existing blog posts * `blog/index` - an index (high level summary) of all existing blog posts
For a simple personal homepage site, this database model is sufficient. If you need data to be available in a way that doesn't fit the document-based structure (in what MongoDB would call a View), you make a new JSON document that pre-caches the data when it changes (i.e. `blog/index` is a high level cache of basic blog entry details, like their subject, creation date, author ID, etc. -- but not their contents, comment counts, avatars, or other details)
# Example DB Structure # Example DB Structure
``` ```