MySQL vs MongoDB

Database management systems (DBMS) are software tools that allow users to store, extract, and query large sets of data. IBM’s Martin Keen explores the key differences between two of the most popular varieties – MySQL and MongoDB - and explains how each got its unusual name.

#mysql #mongodb #database

[when_life_gives_you_limes]

I can tell this guy is a fun teacher, more of him please!

[ovuokeaghwotu]

This couldn't have come at a better time. Thank you for this!

[kader]

LEWANDOWSKI what are you doing at IBM 💀

[Keenok]

I have been using SQL for 30 years and mongo since it started. I fervently hate that I can't write a single query in mongo that will tell me what services a subscriber has purchased, since the subscriber table cannot be related directly within a query to the services table. I used to write single queries that could tell me every optical node in a circuit and spit it out in an easy to read manner. Now I would have to write a significant program in another language to manage what I did in 100 lines of human readable SQL. If I could write queries that correlate multiple collections at the command line, I would love mongo. Yeah, it is fast and flexible, but as the guy who has to figure out what went wrong at a telecom that has 5 9's uptime, I can't do it in mongo. In SQL I can.

[buddhikabandara]

This guy is a good teacher. Good luck with the GizNormDB :D

[jinhunpark]

Nice video! But love your homebrew channel more ;)

[rogerkim]

these videos actually tempt me so hard to try and apply to IBM. Great video, thanks!

[KyleHarrisonRedacted]

Made a blog platform that could run on MySQL and MongoDB by switching a flag, and pumped them full of facade data (couple authors, long and short posts, bunch of users, comments) I just wanted to see which one would run faster at the end of the day with a real world application.
The results to me were that while they were fairly even with a little data at the beginning, Mongo really started falling behind with page load times as the data ballooned
Now, bare in mind my test structured the Mongo data in a similar way to how I’d store in a relational table. I wanted to run the same test but with the idea that I’d be combining the documents but it required quite a bit of conditional refactoring, especially in the admin portions.
And then MySQL introduced its own indexable json document column type. I just never bothered looking back to Mongo after that

[xenonozhid]

Great presentation - thank you. A comparison with DB2 would be appreciated.

[yavuzsert]

I'm a bit familiar with both db's but this is the first time that i learned where their names are coming from 🙂

[nickelnc]

I hope to see GizNormDB in the future. Good luck 🤞

[QzBoy]

Hi Bro, excellent video, btw, what software/hardware you're using to record your handwriting on a transparent screen?

[severtone]

Since becoming a GizNormDB developer, my life has changed significantly. 😂

[fabienpineau]

What the method used to face the screen and write on the screen like IBM video?

[thomascollins]

I was trying to explain the difference between relational and document databases to my partner. I was met with confused looks and more questions. Thankfully I found this video and I can get back to my evening.

[andrewmartinez]

What's the security part that you don't get with mongodb?

[pprocacci]

I'd love for you to do a postgres (legacy) vs a mongodb comparison.
I say this not only because postgres can act in a document driven manner, it's also 7x faster in writes and 2x faster in reads than mongodb.
Sometimes, even if the original design of a "legacy" system wasn't intended to be used in a certain way, those "legacy" systems have adapted to incorporate both.
Postgres is one such system that can do what mongodb can do, but better. Postgres can also do time series related stuff better than the competition as well.

Now I happen to work in finance, and we're using postgres for all the above ... a document store, a time series database, and even table driven data. It just works and there is no need to run 3 different systems for 3 different use cases.

[DanielOpitz]

Nice video, but the term "legacy" is just not correct in this context.

[RogerHolden]

Never heard JSON pronounced that way!!😃

[aravindmuthu]

Is this guy writing in reverse? Bruh, that's a skill I would like to learn