DocumentDB implementation behaves as a simple cloud hosted .json file

[Daniel Jacobson]

DocumentDB has a lot of power. Ideally, the DocumentDB implementation would do the following:

• For each calendar month, a new collection is generated in the code with a unique label based on month and year
• For each calendar day, a new document is created (within the appropriate monthly collection) to record all events for a specific day
• When reading/writing to the documents in the code, first check to see if the document/collection that should be operated on exists; else, create the document/collection
• Use DocumentDB NoSQL queries to operate on the data rather than doing data operations on the client app