CODEWITHSUNDEEP
javascriptmongodbdesign-patternscollectionsdocuments
Eugene Vilder
Eugene Vilder

Reputation: 562

How to properly create collections in Mongodb?

I have a huge experience with MySql and Oracle as relational DBs, but I'm very confused about how properly create collections in MongoDB.

I was reading so many articles and watching youtube videos, but didn't get any real example of how properly create the structure and relationship between two or three collections (properly, best practice or whatever...)

For example... Assume we have three collections Users, Comments, and Posts. What will be right design to use? If the Comments is embedded inside of Posts, then what I have to do in case an User changed his name? Should I run through all comments related to a post in order to update his name in Comments collection? If it's a referenced one, then how to fetch data from all three collections (Post->Comment->User)... Aggregation? If it does, then how MongoDB will behave if the collection will grow up and reach, let's say, 100,000 documents...

Well... I hope you've got my point.

I'll be glad if you guys will post your comments and thoughts about all this stuff and "clarify" all this.

Tnx.

Upvotes: 0

Views: 83

Answers (2)

user2613226
user2613226

Reputation: 1

I think you can embed comments with user ID inside Post, then used a separate doc of userid inside post for collecting all users contribute to the post (comments etc). Since userid is key, when you return post you can flat taht doc with user's info. Then on client side you can use user document with names etc to recreate the user name etc with the post and comments.

Upvotes: 0

Tal G.
Tal G.

Reputation: 493

You are still thinking SQL, there are no 3 collections, just one or two if the number of posts is huge and so is the number of comments. Let's look at the Posts as a collection. Post is created by user and so are the comments (different users). User will not change his name that often if at all and when one does just run an update. { _id : PostID, title: string, body: string, meta: {...}, user: { id : UserId, name: string }, comments: [ { id: CommentId, by: { id : UserId, name: string } }, ... ] } If a user will change his name then you run two updates. One for owner and one for comments using positional operator. Personally I don't think this will happen often. If the number of posts is huge and they are active with comments and such, then one can think about 2 collections one for posts and one for comments or consider sharding but not as a first option. 100K is not a very big number at all.

Upvotes: 0

Related Questions