title: How to Structure Mongo Database for REST API
body: <p>I'm writing a REST API with Mongo and was intrigued by the whole document modeling strategy. It seems like a very divisive issue where people say to denormalize first, then normalize or vice-versa. </p>
  
  <p>I'm interested to see how the resource structure of a REST api influences the structure of a document-based db. It seems like with a REST api resource structure, it almost makes sense to have separate collections for everything (i.e. locations, tenants, transactions) although this seems like it would be working against one of Mongo's benefits.</p>
  
  <p>My question is how would you model the resources of a REST api in a NoSQL (specifically Mongo) document database.</p>