I’m new to the whole NoSQL game and it seems I can’t get my mind or of many collections and distributed data models so I thought I’d just ask a real basic question: what’s wrong with using one collection for the bulk of my data? Say I have a ToDo app with appointment reminders and events. Why not store all tasks, events, and reminders in one collection with a
type fields to distinguish the data? Is there any gain? If there’s no schema restrictions can this work? Thoughts, opinions, and anecdotes welcome!
This example from eBay offers a take on my example from above. If modeling a blog, one collection is for each blog post that has child documents for comments, tags, and categories. So if you took the example above and boiled it down to a single item like an event, say a due date for example. Each event would have child documents for associated tasks and reminders on the parent doc of an event. Even if you wanted to relate the event to say a project which can have many events, couldn’t you still model that on one collection?