MongoDB Schema Design Best Practices

love the energy

If an array can not grow without bound how to we manage something like a users posts? We obviously wouldn't want to limit a users posts so how do you work around that?

great work Joe!. In fact, it is very interesting to watch your videos about MongoDB, but I am confused about one thing🧐🤨

Explains the conept very well...thanks

I have never knew MondoDb schema design can be this entertaining. Thank you, Joe.

💯

I need more video from you Joe

Excellent demo thanks 👍

he is so full of energy. bless him!!!

I loved your video Joe. Fantastic. You are such a character! hahaha

Unwatchable. Just get to the point.

What is going on with that painting back there?

So, for many-to-many relationships, Joe suggests to store the relationship data in BOTH tables (very unlike SQL dbs where we avoid redundancy). This helped me resolve a quarrel with myself on the db schema for my first MongoDB Atlas Collections. Thanks Joe

Oh wow, super clever way to handle squillions of data relationships 💯

NO RULES 🤯
NO ALGORITHM 🤯
NO PROCESS 🤯

One to squillions 😂

I can see the passion
video quality is awesome
upto the mark
not just learnt but njyed learning from you
thanks

dude is awesome

Thank you . that's what i was looking for ;)

You're the best Joe, I had a filthy schema structure until I saw this video.

okay that Pam's bit was funny

Excellent explanation. Thanks Joe

Just read the same blog on the mongodb site. Both are great for beginners.

Grok! Nice 😊 thanks! This was a super informative and fun video explainer

SQL => business/enterprise 'storage'
MongoDB => application state !!! =]

is joins in mongodb slower than sql server?
because if I use objectids, I will always need joins.

i'm new on your VDO, Love it ! Great tutorial. you make learning super fun

This helps a lot! Thanks Joe!

My app shows a profile page of a student with a list of classes she's enrolled in. Classic Student/Class/Enrolment tables in SQL. In Mongo I would want to just embed everything in 1 document. What if I change the name of a class, or a student drops a class previously enrolled? How do I do this WITHOUT joins? "Throw away" the document (delete) and just make a new one (like a piece of physical paper) with the updated stuff?

Things people really need to consider before moving everything to MongoDB. It isn't a relational database management system. Saying MongoDB is better than any RDBMS without first specifying the data shows a real lack of knowledge.

Key constraints don't exists in MongoDB. There are no referential integrity checks. We use MongoDB for blob storage and store the MongoDB keys in SQL Server. It's great for that but I would never outright replace a normalized SQL Server or a MySQL RDBMS instance with MongoDB.

Maybe a lot of people see MongoDB as being better because they don't want to worry about optimizing indexes and execution plans, and they see the "read" performance gains...but that comes at a cost of data integrity. It's a schemaless structure which means consistency doesn't exist. It will eat anything you feed it which can be dangerous.

Think about what happens over time as you add/remove properties from your JSON or add/remove reference data based on changing business rules. Think about what that conversion would look like in MongoDB compared to a RDBMS instance. Using the example in this video what if there was a business rule that allowed someone to remove a profession (physical or logical) from all users. Ask yourself what that would look like in MongoDB vs a Relational Database.

I know I sound pretty critical of MongoDB but I don't mean to. We use it and it works well for our needs but it's not a replacement for RDBMS. More of a supplement. NoSQL shines in write-once-read-many scenarios.

Not sure if i am fan of this delivery style but he was getting the point across.

Coming from a SQL mindset to MongoDB is an interesting experience, but also kinda freeing in a way.. thanks for making this video!

Can anyone please please help me with how can I make combination of 2 field values unique , should i use a pre save or method to implement it or mongo has something for it

1 i want to have unique anime name for a particular user , so i use a createdBY userid to identify it but I cannt make anime title unique

thank you, really helping

Joe is kind of person that make learning fun

I love the style of this video so much. It makes learning tech so much more fun compare to other monotone tech videos.

I don't find this video helpful sorry, wish you would of shown actual code using schema and models and how to connect two schemas together. This video is just saying we have to do this and do that but you never show us code wise. VERY HELPFUL

Omg. I really love about how Joe explain the all of these schema design. Never feel exciting like this when learning new concept. Thanks Joe ❤️.

What's the best way to model a one to many relationship within a single collection. E.g. users following users? I always use a followers array on the user document that stores other user IDs, but it feels clanky (unbounded array?)

Love the content <3 by the way you're so cute !

I am not sure why, but for some reason it looks like you are filming inside a bar before it opens. Weird.

I have a collection called "hospitalization" that stores two collections ids a hospital_Id and a patient_Id. My question is I want to query hospitalization collection and search by keyword of field of hospital collection of hospital collection. how can I do so?

You are extremely likeable

Rule 1: embed unless there is a compelling reason not to
Rule 2: avoid JOINS if they can be avoided
Rule 3: array should never grow without bound
Rule 4: an object should not be embedded if it needs to be accessed individually

Thanks Joe! That is gold. Very clear and so fun to watch!

Good job explaining/confirming my loosely established notions about how to design a NoSQL database. Thanks Joe.

MongoDB is a low-resistance (easy to use) database that’s become my go-to data store for standing up products.

Great explanation. Just what I was looking for.

iam new to mongodb .and i want to know how what is best practices and what is not best but optimum for my needs
1) get all the data and sort and filter client side (i know this is bad)
2) filter data on mongo atlas and then sort client side (dose it make any difference to save resource on server )
3) filter and sort on server and just show data on client

what should i do and what are best practices.

like i get a list of documents from server with embedded objects.
1) should i use project and remove embedded objects i dont need.( does this use more server resource)
2) or i get all the embedded objects and hide them with client side logic