@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.

@buddhikabandara9256

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

@AlexanderWatson-d7w

Thank you for breaking down the differences between MySQL and MongoDB! It was helpful to see how the  two DBMS deal with different issues and which one is better in certain conditions. It has helped me  understand which one I should use for my projects and the reasons behind my decision.))

@PeterB_California

Great job as usual @martin!

@rogerkim7794

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

@severtone263

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

@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

@cattrader-r

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

@yavuzsert6765

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

@WhyIsGhostInTheArena

For some reason I was thinking that mysql and mongodb weren't both databases. I thought MongoDB was just a server. Will definitely learn both

@TonksMoriarty

You can't convince me that MongoDB isn't named after Ming the Merciless' home planet Mongo in Flash Gordon.

@gooo1762

Thanks a lot!

@thomascollins7955

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.

@trollol_

this is like explaining what a car is by saying it is a thing that has a steering wheel, pedals, etc.

@robertananda1207

wow, that was some quality video

@QzBoy

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

@Octal_Covers

Hi, I develop an application that uses MongoDB, I've found that Mongo can be used for the same applications as SQL, given you structure your data properly, which you should be doing anyways if you're making a database intended for production. Initially for the application we used SQL, but it quickly devolved into code that's hard to maintain. Mongo using JSON for query allows you to easily define queries in code, instead of relying on code-in-code. I believe Mongo is the future of databases.

@MithunMukherjee-y7p

How do you write the text? On a glass?

@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.

@aaron5877

If you work with data, a Rigid Schema in MySQL is a good thing. Flexible in MongoDB translates in to developers being lazy and simply creating a pile of data no one understands.