1:35 - Interesting 'Notes' under Patient Visits.

I came here because the devs in my team kept talking about MongoDB. Having watched this video I now have a much better idea of what they’re talking about. Thank you.

Good video! Two points I like to add that were not addressed. One, RDBMS do have their purpose and can be a better choice than NoSQL databases such as MongoDB. Two, NoSQL DBs need data validation somewhere in the pipeline. Even though it is easy to throw new records into the database with new fields, you won't want duplicate entries like "Washington", "Washington, USA", "Washington State", etc.

Instead of bashing relational databases and presenting MongoDB as their perfect replacement it would be more useful if you presented use cases in which MongoDB is superior and ones in which it is not. It would be a big mistake to choose a DB engine based on the info presented in this video!

Nice video. MongoDB can be simple to get started, which is great. But it can get hard later if you try to access data in unexpected ways (not navigating from the top of a document) or you want to do a summary report fast. A lot of code for navigating documents gets put into the app rather than having the database do it for you. An interesting kind of "third way" is the approach used in MemSQL where it is relational and has SQL, it has sharding and is a distributed database like MongoDB, and it has JSON columns for the truly "document" parts of your data.

Relational databases are not made to mimick real life storage or to be easy to read. It's about efficiency and integrity. Sure NOSQL databases has its own benefits but that does not overrule the way relational databases can be much more useful.

I get why people are complaining but I thought it was a good basic rundown. I just needed to know the difference from the relational databases I'm used to and this provided that in a few minutes. Thanks! The graphics were really nice and made it clear.

Relational databases aren't inefficient, nor hard to read once you learn SQL concepts. But NoSQL does have its places.

best video to understand the difference between the relational and sql databases

Amazing work, guys, and thank you for offering reasonable free options for development and testing that are enough for small projects like mine until we reach the production stage and upgrade. Geospatial queries in particular are a blessing!

Good, clear vid, i actually understood!

Feels a little like an attack on RDMS's. Neither is the future, or the past, they are just 2 different tools each with examples of appropriate/inappropriate uses cases. I was not keen on the part where Mr Horowitz builds a metephor of how RDMS's work using filing cabinets and then attacks his own metaphor as to why RDMS's are terrible. I hope he realizes that a SQL database doesn't "actually" store or fetch data from separate filing cabinets and as for complexity, his example requires a SQl statement of around 8-10 lines long and doesn't cause me any confusion.

Good video. Summarized the general idea very quickly.

Very clear, thx to the team

"Imagine if you had to physically store them in cabinets and move pieces of paper around" Well it's a fucking good thing we don't then. That's not a valid reason to use NoSQL over SQL

Great explaination!

did I hear 'legacy' associated with relational (transactional orientated) databases?

wow! this was one efficiently organized overview on something so "unstructured." here for the genteel discussions 🍿

4:50 drives my Google Home crazy: "You got tails"

This is revolutionary! 🤘🏽

Bold statement referring to relational dbs as 'legacy.' 😃 I like it though, as a JS/MERN dev. I will 💯 look to Mongo (or similar) first and only consider relational if there is driving motivation for it. W/o doubt it is simpler and easier to reason about, and as a JS instructor, it's easier for students to start getting 'immediate gratification' in a short time using Mongo as opposed to all of the things that go into the planning for relational.

This is a great example of how to do explain a technology - break down the problem and how the solution fixes the problem.

This video is basically an Ad on steroid 🤣😂

Thank you.

It was a Great Insights

So good explanation in video nice job guys! I had always same view about relational databases

Love how the haters are complaining that traditional database models are better for software development while ignoring how relevant the usecase you presented is to real-world businesses.

Ooh, fancy chairs in the background.

I've used mongo many times yet i always go back to relational. Maybe i am doing something wrong but i dont see that many disadvantages in using rbdms if the app is not that big. Could be that mongo is better for larger apps ? I dont know. i havent noticed that much of a productivity / development boost by using mongo personally. Interesting video though makes you want to use mongo more

The illustration helped a lot. But How is NoSQL different from text files?

Thanks a lot....

Would be interesting to find out if they do their own payroll accounting for their personal oder invoices is done on mongodb or in a plain old relational db...

very impressive, Mr Horowitz. I am beginning to like MongoDB a lot, despite having worked on oracle databases for 25 years. Is there a video that explains just how much "denormalization" (pardon the legacy jargon:) can be done. e.g. would you say put EVERYTHING for a patient into a SINGLE document? (basically all the entities you showed in the video - contact info, visits, lab tests, and others). at what point does the model run into performance issues in the practical world (updates are expensive, and they would be especially expensive for updating large records/documents as would be the case here and I can't imagine how MongoDB can get around that). Any link to videos that explain such things would be very helpful. Thank You Very Much.

from his explanation of MongoDB, I got the impression that it is very similar to LDAP concept?

5 min, main key points, good vid.

Evidently MongoDB designers knew very little about DBMS tables. There's a thing called view in DBMS which would do what MongoDB the same thing. Distribution of database is the implementation. You can design redundancies as much as your heart content. I knew that the database would be more than 32-bit pointer could handle in the late 80's and early 90's, Oracle gave free licenses to universities. Unless there is something that makes MongoDB standing out, other than that it's not much different from other DBMS's.

im sold

thanks you so much :)

Weak video. Expected better. They address different use cases. Just as RDBMS is "Excel on Steroids", in simple semantics MongoDB is Microsoft Word on Steroids.

This video focuses on reading, or 'reporting' data. Sure, when you compare this solution to a 3NF model, Mongo DB comes out on top. 3NF is best suited writing. But there are other modelling techniques when aiming at reading/retrieving/reporting. I'd be interested to see a Star Schema model (Kimball methodology) compared to this, as far as performance and ability goes. Slice and Dice, baby! From what I can tell from this video, Mongo DB would be a PERFECT solution for 1-off Applications. Especially since programmers aren't data engineers; they just think they are. I want to learn more about Mongo DB in an Enterprise environment. Piqued my interest, and I'm not hating.

Beautiful concept ...

I owe you a beer, Mr Horowitz.

You could have done MongoDB without attacking RDBMS. I am an Oracle Developer and I love it. I personally believe that each product is unique in their own way.

I watched this video for 5 minutes and if this was base for my decision to use it, I would not use it at all. What you are saying is like because we figured out opening 4 screws to reach content of the PC case is too hard and cumbersome, instead we put a single nail in middle of it so if you want to open it just pull the nail. also since data being where customer is, we split the motherboard to 14 pieces and put each piece in one part of house (toilet, kitchen, bedroom, living room, ....)

Microsoft Excel on steroids! I LMAO when I heard that. So good.

Sweet.

All objects should have parent, own and 'kept' properties. Own properties are added on a per object basis on top of inherited properties. Any object can be a parent. 'Kept' properties are not inherited by subs. Tables are objects too. This is a superior model.

you are amazing

nailed in 5 min.

The whole "teardown" section on relational databases is comical. If normalization were so freaking awful and inefficient you could (but you shouldn't) just jam all your data in a single table. Of course that is ludicrous and so is this argument against SQL databases>? On top of that, why do NOSQL developers inevitably try to recreate relational concepts in the ill-equipped NOSQL databases?

As other orders in life. An honest review/introduction have to mention de bad sides too IMHO.

Wait, 2:30 isn't this what a traditional DBMS does??

This is the future.

Is it web scale?

Good overview of RDBs. Only if MongoDB's was that good.

Good

Why compare with MS Excel? Should compare it with MS Access RDBMS.

I still don't understand the advantages of MongoDB in comparison to a rdbms. Can someone explain?

There is always the wrong tool for doing the job and a better one. Same applies to the database system you chose. I also don‘t agree with the statement about hard to maintain and enhance. There was also a reason why relational databases were invented. Nobody wanted to store redundant information and be economical with resources on your system. Today, resources almost don’t matter anymore and allows a more „wasteful“ type of system. Nothing wrong with that but it’s just wrong to say it is always superior.

Use Postgres JSONB.

coming from mysql, this is heaven.

I have zero experience with mongoDB but from this presentation it looks like you have tons of redundant data for example you have worker and company that he works in right? In relational database the company name would be store once in company's table and in worker table you would have only id number of this company, but in mongo you have huge document with company name explicitly declared there so it's clearly have some cons not only pros.

Wow, "A relational database is Microsoft Excel on steroids". What a terrible analogy or lack of understanding.

Isn't 0:15 "Microsoft Access on steroids?"

This is nonsense. You will for sure end up with many copies of the same data in different places with this design. All updated from different processes. I don't care how fast you can read and write data if it is not correct. And it can not be correct because there's no referential integrity enforcement. Please stop giving bad advice.

"the document model is the key design choice we made" im only here for the free storage space LOL

As you see the replies below, the people calling out Mr. Horowitz seem to be experienced folks. Whereas newbies would completely fall for Mr. H's pitch. That probably explains why new programmers are leaning toward Mongo. Later it catches up with them. Schools should teach multiple ways to structure and access data. For example storing JSON like documents is supported by Postgres, a relational db. So now, you have the ability to take advantage of both database paradigms within a single database/table.

MongoDB really hates relational databases XD But I still think it was a good explanation.

Such a stupid interview. Barely spoke about NoSQL and Mongo, just trashed SQL and likened all SQL database systems to "Excel on steroids". I like both, but this interview did absolutely nothing for those people on the fence and those considering to use Mongo. Both have their purposes, don't let their short sighted CTO put you off.

Feels more like a sales pitch to me.

So RDBMS only run on mainframes and any little change breaks them according to this guy.

1:31 "numbness in third arm" 🤣

well the people complaining about the content, haven't watched the video past the half point.

isn't that just json?

Well and then there is Oracle 😂😂😂

haaa lol SQL Database is fundamentally Ms Excel in Steroids 0:15 makes sense

How it is build??? Other models explaibed, but not own. Fk this sht. In background just a regular relation structure???

How distributed MongoDB is different from Blockchain?

UNLEASH THE DRONE JAMMERS

Like Excel on steroids......lulz

Dude needs a nap.

Seriously, the strawman of "Excel on steroids", and then the strawman of saying a relational is like separate physical file cabinets? Jeez, who told him to do that? Makes him look like he doesn't understand efficient data storage. Mongodb is just another tool in the arsenal, and I'm sure it has its uses, and I'm sure it has a different set of headaches that relational doesn't have.

👍

WOW, this guy does not know how RDBMS works compares to Excel LOL. Basically this is a Sales Video to Say that MongoDB is a replacement for every database in the world. I would rather see a practical use case scenario.

hi

"no third arm actually present".... lool

This video is providing an extremely biased view. This bias if fairly widespread in the developer world today. If that patient record db was stored in Excel as he shows, it would NOT make the file size larger. It seems that way, but it is not. Both Excel and relational db's take as much room as there's data. They don't allocate storage for NULL fields. BIG LIE HERE! Second, they say breaking data into multiple tables causes complexity. Let's dig into that. ADDRESSES is fairly easy to understand. If someone asked how many patients live within 5 miles of our office, i just need to go through ADDRESSES and not have to pull all the patient data, along with their medical history and all other patient related data, embedded within the Mongo patient document. The complexity is only in the JOINS in relational db's. However, the language of SQL is very english like. The language of Mongo is very abstract (sending objects with meta phrases (e.g. `$set`)), making it difficult to do complex queries with it. SQL on the other hand is so so flexible with what you can do, and it is easy to understand what's going on.

i want a perfect tutorial of mongodb on ubuntu

MongoDB = Future :)

AI brought me here after 20 years of SQL datawarehousing

So...no sql?

Advertising MongoDB to amateur developers so they use it when they shouldn't and few years later BOOM!!! MongoDB is not bad but this video is misleading

Very weak advertisement video.. I am shocked about the BAD really BAD BAD BAD analogy of the file cabinet, because it's not how SQL works...when looking up data.. (it doesn;t open up one "cabinet" after another until it has all data... among many other lies presented in the analogy. ) next time. mongodb as a company should tell the truths, like where SQL and noSQL is prefered, and where not... (being honest is key!) Also the WHY!

👍👌🏻

postgreSQL feels so smooth while MongoDB is trying to enjoy a fish with a lot of bones. Err!

It's laughable how the entire comment section is filled with people who probably learned RDBMS from tutorialspoint and are so afraid to learn a new technology that they are trying to make a bad impression on literally any other technology that comes up. If you think something is not suitable for you, it's simple - don't use it. The only reason yoy people are here is because you know you are afraid you are gonna be left behind because you are such DINOSAUR.

I hoped this video will show any benefit of mongo vs any other storage but it failed.

You make it sound like using many tables is difficult. It's not. It's easy. Be honest and outline the real advantages of MongoDB. Like it is scalable. Also, adding data isn't the only problem, when you need to query data, a relational database is better.

I love MongoDB but this video is a misrepresentation of relational databases. In relational databases you build upon "relations" this means that you don't dump everything on a single table as if the database were a spreadsheet.

Presenting wrong RD schema as an argument for using MongoDb? Come on, you can do better.