SQL vs NoSQL or MySQL vs MongoDB

SQL or NoSQL? MySQL vs MongoDB? Which database is better? Which one should you use?
Get our complete SQL (MySQL & PostgreSQL) course: acad.link/sql
Learn all about MongoDB: acad.link/mongodb
Exclusive discount also available for our MEAN (Mongo, Express, Angular, Node) course: acad.link/mean
Join our Academind Community on Discord for free: / discord
Don't miss the article on this video: academind.com/...
Want to learn something totally different? Check out our other courses: academind.com/...
----------
More on SQL Horizontal Scaling: stackoverflow....
----------
• You can follow Max on Twitter (@maxedapps).
• And you should of course also follow @academind_real.
• You can also find us on Facebook.( / academindchannel )
• Or visit our Website (www.academind.com) and subscribe to our newsletter!
See you in the videos!
----------
Academind is your source for online education in the areas of web development, frontend web development, backend web development, programming, coding and data science! No matter if you are looking for a tutorial, a course, a crash course, an introduction, an online tutorial or any related video, we try our best to offer you the content you are looking for. Our topics include Angular, React, Vue, Html, CSS, JavaScript, TypeScript, Redux, Nuxt.js, RxJs, Bootstrap, Laravel, Node.js, Progressive Web Apps (PWA), Ionic, React Native, Regular Expressions (RegEx), Stencil, Power BI, Amazon Web Services (AWS), Firebase or other topics, make sure to have a look at this channel or at academind.com to find the learning resource of your choice!

[@windar2390]

0:36 SQL 9:00 NoSQL 13:13 Differences

[@annyrose4218]

Thank you for this.

[@mohamedjolti572]

this course how to create the same web applcation using node js mongo db and php mysql: www.udemy.com/course/node-js-mongodb-vs-php-mysql-build-the-same-web-application/

[@Wenutz]

Not all heros wear capes!

[@floatingsaint8493]

U know this is the only useful🙂 comment in the whole comment section

[@EduardoSDiaz]

Thanks bro!

[@iterating_life]

I dont think I will ever be grateful enough for Maximilian. This man single-handedly taught me everything from HTML, CSS and basic JavaScript, all the way to Vue and React, Node.js, databases and REST API. Thanks to you I got a highly paying job, and can make anything that comes to my mind. Thank you sir from the bottom of my heart. :)

[@rodrigo-xy2cg]

A key concept in this comparative analysis is consistency of information. - SQL (Relational Databases): a good design (scheme and constraints defined correctly and transactions are used properly) allows the database engine to guarantee consistency based on that design. - NoSQL: lower consistency of information (it is a responsibility of the developer to ensure consistency... some time this could be very difficult).

[@jamesduncanlinch6322]

Yes that is key, and was not mentioned

[@suyuro_]

God bless this "vs" videos they are so good.

[@academind]

I'm very happy to hear that, thank you so much!

[@nicolasazoidis9064]

Man you knowledge base is beyond human scope...really. When i first started learning programming there where many times i coulnd't get you, after learning programming there a lot of times i realize how many miles ahead you are. RESPECT.

[@colinlee789]

This is the most clear explanation of SQL and NoSQL on KZbin.

[@akmalatkhamov8760]

Tremendous explanation. I have spent 3 days reading tons of information about differences between SQL and NoSQL, and have understood less than I expected, but this video made everything straightforward. Thanks to the author! Great work!

[@academind]

Happy to read that the video helped to make things clearer, thank you Akmal!

[@scvscades]

Thank you for this! I've been tasked to build a DB, but wasn't sure which type to go with. I tried using MongoDB and I can see where it has it's advantages. After watching this though, an SQL DB is better for our needs.

[@mikatu]

The rule is always, when in doubt go for SQL.

[@mbramante]

I really like this video with one singular exception. When discussing relational databases at 1:48 minutes into this video the narrator says: "The database we typically use is a relational database that means we have a database which works with certain assumptions". No other mention or explanation is given for this. Also there is never a mention of NoSQL databases working "with certain assumptions". I've designed/modeled and built relational databases for 19 years. I base every relational database design on one thing: Rigorous due diligence in requirements discovery and analysis. This means: 1) Requirements 2) All the requirements 3) Nothing but the requirements The one thing I NEVER base my relational designs on is "assumptions". No good relational database design should ever be based on assumptions.

[@gregborbonus4122]

The assumptions being made are within the database architecture. Such as assuming every user has a product id(for building out keys and references) so when you act on those relations, SQL engine expects corresponding data in other table(foreign keys as an example)

[@123rodrigo]

I stg i've been looking for a content explaining this subject everywhere and for some reason it was so hard to find your video, you just gave the most clear explanation about the topic ever, i can't believe im able to understand this now, thank you so much god bless !!!

[@MrAnonimR]

Hi, thank you for putting the effort and time to explain in such understandable way the differences between SQL and NoSQL. I appreciate your effort ! Good Luck!

[@bnmvbn654]

This is hands down the most concise and relatable explanation of a SQL-like database vs a NoSQL-like database I have ever seen. Random tips: -A good intro to SQL is reading Chapter 2 of the official PostgreSql manual. -As a frontend dev, it's easier to "pick up" NoSQL. Since NoSQL is literally a folder of JSON files that you can search(query) through. -But, it's easy to dig yourself into a hole if you duplicate your data in several locations and then need to update that same piece of data. -You can also hurt yourself when your not consistent with your property names. For example "first name" can be found as "f_name" or "firstName" in your NoSQL database -Just be careful, and very consistent when using NoSQL. For total beginners, I recommend to go with SQL and then migrate to NoSQL if needed. Think of SQL-databases as a really powerful sportbike motorcycle with really good training wheels. It's safe and you probably won't outride the bike.

[@academind]

Thanks a lot for your wonderful feedback and for providing the additional resources, I really appreciate both :)

[@janina_1412_]

Thank you for the great explanation! I've been looking up a lot of information about databases and this is by far the best and most helpful video!

[@krookbuzz]

More Mongo Db kzbin.info/www/bejne/i2O0hpVmnKmegbM

[@guolunli1908]

This is the best introduction to the difference between SQL v.s. NoSQL databases on KZbin. No wonder why this video gets near 2M views.

[@fabriziodutto7508]

There are special commands so called "choins" @8:31 :-) I really love this german accent! Thank you for this comparison, very interesting and complete.

[@TheRFracer]

Your ability to teach, explain things is absolutly awesome. Im watching a lot of diffrent famous IT youtubers but your content is gold and definitly the best. You probably created more IT devs than any university of the world ;)

[@academind]

That's awesome to hear, really means a lot to me! Thank you so much! :)

[@Relsig89]

Horizontally scaling SQL isn't very difficult but it requires a backend to do some extra work behind the scenes (which isn't terribly hard to program). Implemented properly and under certain conditions it can be slightly faster than NoSQL. You can use Schemas with NoSQL, see tools like Mongoose. Mongoose also makes relations very easy with the populate function. If the data isn't likely to change frequently it would still be better to just nest the data you need and update it as needed for speed though. So SQL horizontal scaling: possible but more difficult than NoSQL. NoSQL: Schema-optional with reverse-compatible changes via some well documented apis Aside from those excellent video

[@CodeSbyAniz]

I have watched a BUNCH of videos on this subject and this was the best one by far. THANK YOU!

[@shutterradio]

Brilliant explanation! I have a feeling that I can learn anything by watching your courses!

[@TheMaxie07]

It's so unfair dislike/thumb-down this resourceful video. Its 2020 and its so valid..Thank you.

[@cancer10in]

You have explained it very nicely Max. Cheers!

[@academind]

That's really great to read Soubhik, thank you very much!

[@prabalhalder2692]

Excellent video for people planning to move from SQL to No-SQL world. Concise and to-the-point comparison.

[@academind]

Thank you very much Prabal!

[@PetarLuketina]

Wow, this is a great information. As a beginning SQL learner, I got a good chunk of knowledge from your video. Thank you!

[@academind]

That's really cool to read Petar, thank you very much for your great feedback!

[@hemantvardani1436]

What a excellent explanation!!! Loved it

[@oubrioko]

Horizontal scaling (also called _scaling-out_ ) is challenging and can be inherently inefficient with a _shared-nothing_ SQL database like MySQL, as mentioned in the video. However, there *are* indeed _shared-storage_ SQL databases that are designed to dynamically scale-out (horizontal scale) seamlessly. This is accomplished by replicating the database _structure_ on each server node, but with virtual programmatic pointers in each table, rather than the actual rows (records) of data themselves. These pointers point to corresponding table structures on distributed Storage Area Networks (SANs) that contain the actual rows of table data. Given this complexity, an enterprise-grade dynamically scalable shared-storage SQL database solution like Oracle 18c is very expensive to acquire, implement, administer and support. During the mid-2000s, Larry Ellison used to love to brag about the horizontal scaling capability of Oracle's shared-storage SQL offerings verses IBM's DB2 shared-nothing SQL database.

[@communitycollegegenius9684]

I learned a lot from this video. I am now prepared for the conference call and will drop some wertical scaling on them.

[@grantharmer7110]

Great video. One of the other key things SQL databases tend to have over NoSQ databases are transactions. i.e. ACID (Atomicity, Consistency, Isolation, Durability) support. But, there is an argument that, if you structure your NoSQL documents well, ACID is not needed

[@yunli1333]

19:00 summary is pretty solid.

[@samislam2746]

13:00 you can save the user id in the user field of the orders collection, and when you query the orders collection, you populate the user field. this way the data does not get duplicated, it works just like a relation

[@TheDragonlove1]

Relations = Tables (Product Table) Relationship = Relationship (One to One) Relation != Relationship that's the db language as we learnt it from our teachers

[@theopeterbroers819]

This video disregards any and all relational theory. SQL is not the same language as Sequel. Both languages are interfaces to the database, not the thing itself. What do tables (correctly: relations) have to do with containers? Containers are like waste baskets. Tables are linked to each other through constraints, not "tables" through "relations". Rows or records are remnants from earlier database models, like Codasyl. We say tuples now. And I could only make it to 5:40. Better info here (I just googled this site): www.ntu.edu.sg/home/ehchua/programming/sql/Relational_Database_Design.html

[@bleys2417]

@theopeterbroers819 Totally agree. If the author wanted to simplify the material, it is better to don’t mention “hard” concepts at all.

[@raulbarriga7416]

Good thing I found this video, and from a web developer/full stack KZbinr. Needed to see which sql to choose to learn.

[@maxnaiir]

just was wondering about this topic and bam!!! the notification, sql vs nosql.. .. thanx max

[@academind]

Guess that was kind of the right timing for you then, so cool to read that :)

[@markololic8967]

I've watched a handful of videos explaining this and this was by far the best, great video.

[@whatsap6851]

Helpline📲📥⬆️ Questions can come in⬆️

[@gjermundification]

9:16 mongoDB may be the nosql with most tutorials, then again if you run postgres, mongodb and couchdb in strace, mongodb spends like 6 times the amount of resources to achieve the same performance compared to postgres or couchdb.

[@akramchebli]

My school paper just got a bit smarter because of you. Thanks!

[@ConsulthinkProgrammer]

Try this for some additional reference kzbin.info/www/bejne/m5-4eIuPgtBpeZo

[@JohnWeland]

We use an SQL database at work specifically PostgreSQL. Our "rules" for our schema all tables need a primary key as a sequence that is either called seq or id. If that tables p_key is not referenced in another table we call it seq if another table does use it, its called id so a user table would have a column id, then on the table referencing there would be a sequence and a column called user_id. All of out many to many tables we call tablename_xref (xref for cross-reference) so just looking at the database it makes a ton of sense. we also add control columns on every table prefixed with ctl we have an insert user, insert time, update user, update time the times are stored as dttm (time with timezone). any anytime a user inserts data or updates data its reflected in the control columns.

[@mobassirshamim3947]

👍🏻

[@tomazkoritnik4072]

Namig them seq or id doesn't make any sense. First, you're using two names for the same thing: object identification. Second, when your table has seq and you have a need in the future to reference it, you need to change the code and schema. Third, goes together with first, you're mixing the concerns by putting higher structure information into entities and this is bad because it introduces coupling.

[@Eddy-ly2ml]

2 years later from this video update and its super nice to hear all this information!

[@Nikolaik7777]

In terms of RDBMS a "relation" actually means a table (because it stores rows of "related data" - that is structured records vs just a bunch of values). What he calls "relations" are properly called "foreign key constraints".

[@dariolimatola386]

Thank you! I was just about to write it

[@ЕдвардГригорян-н6к]

I am glad that accidentally found your video on youtube. the best explanation sql vs no-sql i've ever seen.

[@Loppy2345]

This is one of the few "VS" questions that really is useful, it comes up all the time in job interviews.

[@hahmadzai23]

Appreciate the breakdown!

[@mcdonaldsonechendu5644]

Definitely needed this! I've hear NoSQL was faster than SQL, so it seemed very attractive. But most of my projects rely on the integrity of the data shared across different Models. This video has persuaded me to stick with SQL lol. The fact that updating one NoSQL Collection has no affect on linked Collections is a big downside. Thanks 👌👌

[@gabe4338]

The thing is: You need a place where your relation rules live. In a sql database this is (in my experience) both: There are some relations in the db but they get ignored more and more, because they are difficult to manage and so more and more of the rules just live in the (hopefully single!) backend that reads and writes from the db. In NoSql you just keep everything in the code. But yes: Mongo is not the solution to everything, you still need to make a good concept. But if you're not doing waterfall, your schema will definetly change over time and this is a lot easier with mongo.

[@mza1409]

Will this video get a sequel?😂

[@academind]

I see what you did there :D

[@filcondrat]

web witticism development

[@6884]

where is the NUCLEAR BAN button here??

[@colinmaharaj]

I will JOIN you there in that QUERY.

[@jded1346]

NoSequel :)

[@AlamKhan-yt9wd]

Thank you soooooooooooooooo much. Finally understand, it's not necessary to use MySql with PHP & MongoDB with NodeJS. Both the database has difference perspective depending on the scaling, reading/ writing, updating & relation factors.

[@osvaldoguzman3115]

Another important thing to consider for SQL databases is the amount of time conceptualizing a SQL database takes. For an effective SQL db you need a proper ERR Diagram and schema that takes into consideration a ton of user interactions. One wrong step at the conceptualization phase and your whole relational system breaks. Similarly, the modification anomalies that may come from NoSQL can break your db, but to a more manageable extent IMO. When agile development reigns king, quick development with short conceptualizing phases means your better off with NoSQL despite the downside to writing-heavy applications. What do you all think?

[@JoseWalderSilverio]

I have learned more with this video than with my university teacher in 2 months of classes.

[@academind]

Happy to read that the video was even more helpful for you than university Jose :)

[@mysterria_com]

It's actually not about SQL vs NoSQL but relational vs non-relational. SQL databases come with a lot of constraint and behaviors (triggers) and if your data is highly relational, you will have an advantage using SQL databases maintaining your data structural integrity. On the other hand NoSQL databases are very restricted in relational integrity enforcement tools, but they are faster, easier to operate and learn and are very convenient for specific tasks. In general, use relational database if you're not sure which type of DB to go with. It might require some extra planning but won't lead you to data integrity issues and migration to NonSQL will be mush easier. At the point you face the need of sharding you will surely be well aware of what type of DB you need and how to shard your data well. So I'd not worry about scaling at this point.

[@researchandbuild1751]

NoSQL is just a serialized dictionary for lazy programmers that would rather write schema in code than come up with table structures and normalize them...

[@saidheeraj1760]

Didn't expect to get this with one video. You did it man. Keep going ✌️

[@goodvibesonly926]

Great video 👍 Could you maybe have a part 2 of this that provide practical examples, eg. Pointing out a few tech companies that are using different type of DBMS and how do they store or work with their current data. For a fresh graduate like me that do not have industry experience, it will give some insights when searching for job roles

[@as_if]

So the diff lies mainly in: SQL - normalization leads to better updation of data > but read becomes slower (joining multiple tables) > horizontal scaling issue NoSQL - less relations amongst the collections > one collection holding info about other object of other collection as well (post document containing user's id, name, pfp etc) > easy to Read > hard to Update because of data redundancy > good horizontal scaling (having less relations/dependency among collections)

[@desertpillar5286]

Thanks for a great general comparison... I know this is old, but thought I'd mention one thing that I think is overlooked in this video although technically correct. Specifically regarding relations and schema consistency. While you are correct in saying that it is not directly supported in Mongo, this responsibility is instead handed over to the ORM layer. Typically, at least in Rails with Active Record, you add all the schema enforcements and relational requirements in that layer instead. By doing that you eliminate most of the downsides you mention regarding data consistency. One other key feature that I think should be mentioned too is that you can create much more advanced data structures in the documents themselves. This is a very simple example, but lets say you wanted to quickly wanted to know which users ordered a specific product. One way to solve that would be to have an array of user_ids on the product collection which essentially acts as a has_many relationship. When displaying products you could easily describe how many users bought this product and even show if friends of the user bought the product (provided you have a collection for that data too). Maybe a stupid example, but hopefully you get the idea. I would say that the biggest downside to using mongo is if you have a lot of requirements to run group by queries. Although it is possible in mongo with aggregations, it is not as straight forward. For me, unless I'm writing a banking application, I would select mongo for every web application I would build. :)

[@rbelatamas]

Really, really, good, clear description!!! Thank you so much!

[@CaptainSuperX]

A very important difference that is not mentioned in this video is transaction.

[@KeyhanHadjari]

Mongo supports transactions from version 4.

[@thabo5799]

@@KeyhanHadjari It does, but only for one object... still pretty bad.

[@ritsukasa]

exactly, very important, omited completely.

[@neilbradley100]

@@thabo5799 MarkLogic has supported multi-document ACID transcations since version 1 (it is now at version 10), and this is indeed still very unusual in NoSQL databases

[@arbdistress5592]

Yes To me single object transaction is simply no transaction.. it is just atomic document "save". Transaction is two or more changes they are either all done or nothing done.

[@a_1122_as]

I'm heading to a technical interview and your video really helped it made me more confident

[@jeffersonribeiro1669]

Off topic: I did the Complete React Course from this amazing dude and its great!

[@academind]

Thank you for your support here and on Udemy Jefferson! It really makes me happy to read that you enjoyed the React course :)

[@lardosian]

The burger builder course? I have to get around to that as well. The way packages change so much these days does this cause any issues. Im sure Max has this covered though.

[@degraphe8824]

That course started off my coding career and got me lots of jobs Thank you Academind!!!!!!!!

[@lovelyanu-v1x]

sql:-uses for shemas having relations and distributed across multiple tables only possible for verical scaling limitations are high for read and write queries nosql:-uses for schema-less having no relations and typically merged/nested in a few collections possible for both horizontal and vertivcal scaling great performence for read and write quaries

[@smanihwr]

Thanks for this video Max!! Comparison slide was more helpful.

[@academind]

Thanks for your nice and helpful feedback!

[@RsnRom]

That is impressive and very clear explained. Even I am not native English speaker, I have understood everything. Would like to see more from you

[@vinny142]

"Which database is better? Which one should you use? " PostgreSQL. That has a JSONB type whic means you can store Json documents and query them, and it has all the required features of a database: transactions, replication etc. Plus it has a large number of free extensions that enable you to connect it to mysql or oracle or even an XML or CSV file as a data source. PostgreSQL exlipses the abilities of MySQL, really, and it's also free.

[@bakatoroi]

What would you say are the major advantages of PostreSQL over MariaDB/MySQL? I'm just starting researching about them and just comparing their DATE fields makes me believe PostreSQL is much better but I'd love it if you could share more info.

[@oida10000]

@@bakatoroi postgresSQL supports recursive querys and nosql features.

[@barronanderson382]

PostgreSQL is a RDBMS and as such does not scale horizontal. If you require the performance of 10,000 concurrent servers you need a solution which scales horizontally. PostgreSQL is a nice RDBMS solution, I am not knocking it.

[@quicktecha3]

Great video, thanks for all the info!

[@ConsulthinkProgrammer]

Do it with apps script, and connect the output to your spreadsheet kzbin.info/www/bejne/m5-4eIuPgtBpeZo

[@RickoDeSea]

I struggled to learn database until this tutorial. Thanks alot.

[@LifeIsGood1992]

Thank you , To make it short : if you want more data customization use sql , and if you will do an archive-ish data (read and write a lot with rare update )use no sql

[@snnwstt]

Well, even for archive, who forbid to use a different field name, or attribute key name and doing so, as example, miss the criminal records of a multi-recidivist because these records were archived under another field name? What good is such an "archive" ?

[@Женя-р8ц3й]

thank you man!!! You are the best in this theme!

[@samislam2746]

and talking the presentation of data and visualizing it (for us, developers), both nosql and sql data can be represented as tables with columns and rows, this makes it simpler for the eyes to see and read.

[@bartlomiej-bak]

And one more comment about scaling. Horizontal scaling is possible in SQL world. Many servers offers 'replication', MS SQL Server offers also linked servers and so on. MySQL offers Clusters. So saying that in sql world only vertical scaling is possible is not 100% correct. Performance of the queries can be improved by indexes but also sql servers optimizes queries to be the most efficient. Also mysql offers few engines, eg. myisam with very limited functionality but very fast, and innodb which can be very strict and safe, but reduces performance. Additional question is which kind of database will require more hardware resources sooner, sql keeping just one entity of the data, or nosql storing same data multiple times ? ;)

[@FrostSpike]

Massively Parallel Processing (MPP) databases too especially for OLAP/Data Warehousing use cases; Teradata, EMC/Greenplum, AWS RedShift, (the database formerly known as) Microsoft Parallel Data Warehouse, Exasol, and Oracle Exadata (at least to some extent with push down filter parallelism in the storage arrays).

[@bartlomiej-bak]

hehe, good answer, but I think we are talking about different level ;) You mentioned about very advanced solutions, which are very expensive as well. That video, imho, was more for beginners than for senior database architects :) but, you are 100% right, we can also mention about IBM DB2 which is/was, I don't know if that db is still maintain or not, object oriented database, RDBMS of course.

[@hoaaahtube]

I strongly agree with this. Horizontal scalling in SQL world is possible, and not too difficult to implement. This videos have said it, vertical scalling have limitations, so developer often use replication as a solution to boost performance. In some case horizontal scalling are cheaper than vertical scalling.

[@BW022]

Horizontal scaling on a SQL database is also possible merely through switching databases or hardware. You can easily start off with housing it inside something like XML or dBase using ADO for a simply desktop or low-traffic web application. Then switch out the database to say MySQL. Then MS SQL Server. Then move it onto an 8 core monster with 64GB of RAM and RAID'd SSDs. All this before you need to look at clustering.

[@johnmadsen37]

Bartłomiej Bąk yeah. I had just finished writing this guy is a fucking idiot.

[@exact-itacademy1282]

This video is great. I like it. I 'm using mysql for 5 years now and when I heard for the first time about nosql, I didn't actually understand the way it wa structured, today I found out with this very video. thanks

[@academind]

Thanks a lot for this great feedback Mukinayi, happy to read that the video was helpful for you!

[@khalidelgazzar]

Thank you very much Max for explaining deep topics in simple and easy way

[@mohamedjolti572]

this course how to create the same web applcation using node js mongo db and php mysql: www.udemy.com/course/node-js-mongodb-vs-php-mysql-build-the-same-web-application/

[@webstylepress]

Working with MongoDB right now. Loving it.

[@kbor8491]

It means "not only sql" (= noSql,) but not NO sql at all

[@TheInfi]

@-.- Cat or just Mongoose, if JavaScript.

[@MarkKevinBesingaWebDev]

dynamodb has some structure so its not only.

[@dewinchy]

Really thanks for sharing, now I finally understand the difference. Some hints: horizontal scaling for SQL is possible (at least for MySQL and Oracle), of course it's trickier than the vertical scaling. The use of the same colors for SQL/NoSQL and Horizontal/Vertical Scaling is a bit confusing.

[@jamesduncanlinch6322]

Yes and more limited. For example oracle RAC depend on shared storage in some cases. Mongo is designed for clustering.

[@liquidpebbles]

I tried to get into NoSQL and every time I did I basically ended up creating a system and imposing schemas and basically just making it a somewhat messy SQL style db.

[@leathernluv]

SELECT location FROM places WHERE name = Waldo Joking aside, here's a summary from a retail perspective: SQL: user/supply tables that are fluid. NOSQL: order/purchase data that are concrete history Your app pulls up the purchaser/supplier from SQL (change in addy, change of name, change in credit), and then the complete exchange history from NOSQL.

[@gregborbonus4122]

Great video. I would add that with federated tables, json queries and so on, SQL is quite capable of doing everything you mentioned in a noSQL setup, but the cost is overhead. Ive never seen an instance where I couldn't horizontally scale an SQL database. Can you provide any examples of this?

[@bobslave7063]

Greenplum DB

[@pandabrain]

I like the nosql example for orders. It shows how nosql can easily retain historical data. When a product is changed, then a customer who ordered in the past, didn't actually buy the updated product. The order still shows the product how it was at the time of ordering.

[@vangxbg]

amazing. I finally understand now.

[@cruisniq]

It really does depend on your line of work as to which type of database to use. In my line of work, 95% of the time you would use a no-SQL type such as Elasticsearch. But, as he mentioned, something like an order database, you would be better off using either SQL or an hybrid approach.

[@brunocarvalho5578]

Thank you! Helped me alot! I was struggling to decide which one I would use in my project because I don't knew these core differences and concepts. (I really enjoy and understand most of what you teach and that's the reason why I bought some of your courses, even that english it's not my first language)

[@academind]

Thanks a lot for your awesome feedback Bruno, happy to read that the video was helpful for you! Thanks a lot also for your support, great to have you on board here and on Udemy :)

[@felipemedina2279]

Great! This content helped me a lot to decide wich db I have to learn now. Thank you bro, hugs from Brazil

[@jonathanaina4940]

Good video, but sounds like you are a pro NoSQL. However the disadvantages of SQL stated are not entirely true as scalable distributed framework becomes more developed. With the structure and reliability of MySQL and the high scalability of Hadoop and performance improvement offered by both worlds, what you get is a powerful Relational, very reliable, less messy database. NoSQL is great but I just hope the looseness doesn't over complicate an already complicated ecosystem. Some of the relatively poor designs of the Internet is still causing a lot of problem currently. Overall "All Models are wrong, but some are useful"

[@EqualConnectCoach]

Agreed

[@gregorymoore2877]

For somebody who is "pro NoSQL" he sure made SQL sound like the clear winner for most things.

[@billsantamaria1]

I like most of the description here since I was trying to better understand the NoSQL standpoint. However, I do want to point out that not all SQL implementations are limited on horizontal scaling. Oracle DB since 10g (and better since 11g) has the ability to RAC scale horizontally and keep the data synched between nodes (servers). You do have to properly design the data distribution for such a setup, but when properly designed there is little to no limitations on scale.

[@shin202j]

like your clear pronunciation

[@pinkdiscomosh2766]

This is an awesome break down between the two. I’ve always wondered what the big difference was between the two. Great video!

[@academind]

Thanks a lot for your great feedback!

[@vionel3493]

Well people, just don't be confused with this incorrect description of SQL horizontal scaling possibilities, it explained here completely wrong. SQL scaling very good and not hard at all last several years, just use correct DB for your purpose.

[@snnwstt]

Indeed. And furthermore, the presenter forgot about VIEWS, in SQL, which can act like a collection (the data seems already merged, and it is quite fast since it is done through indexing) in addition to be eventually dynamic too (if a value change in a table implied by the view, refreshing the record will automatically update the view). I fail to see how a NoSQL approach can index your stuff. It looks to me like having to find "who" has the telephone number 123-4567 when all I have is a phone book on paper, where the phone numbers are listed in order of the owner (from A to Z). I would have to walk through all the entries, one by one?

[@EqualConnectCoach]

If u want add column in Deb then have to stop ur process then only can add but this doesn't applicable for nosql

[@vionel3493]

This doesn't relate to what I said above about scaling.

[@dust2dust61]

Just amazing, the way you described both of those database system, really saved me a tons of time surfing through out the internet and reading tons of materials. Thank you so much.

[@jonnyjazzz]

Hey! I recognize your voice from my React Udemy course! Great job, sir! I highly recommend his courses on Udemy!

[@academind]

Happy to read that Jonny, thanks a lot for your great feedback!

[@freefireflow286]

@@academind Name of the course. I mean react one

[@arieltabuzojr2434]

True I tried other Courses but Academind Courses are worth the buck because they're really building real projects with the courses.

[@rprantoine]

Great video! Thanks for it. I would change the colors on the slide about horizontal/vertical scaling though. They are the same as when comparing SQL and NoSQL, and could lead to confusion, letting people assume Horizontal Scaling = SQL and Vertical Scaling = NoSQL

[@bartlomiej-bak]

Maybe I'm wrong but I think few things needs to be clarified, or at least discussed ;) 1. In SQL world 'relation' it's a synonym of 'table', connection between tables is called 'relationship', so all 'relations' from the video are 'relationships'. 2. Typical sql server like mysql, mariadb or so does not allow many-to-many relationships; That one shown in 5:09 is not many-to-many, there are two relationships one-to-many. Some languages, eg. C# or Java, allows to manage many-to-many relationships, but there are not done on sql server side.

[@richardpaulhall]

No. The two regular tables connected by a relationship table is a man-to-many rerlationship. You can have a group ordering a product or a bunch of products

[@bartlomiej-bak]

That's a bit academic talking. Imho, for sql server there are two one-to-many relationships. In the same way you can say that mysql/mariadb can store xml or objects. Of course it can, if you serialize them into string. MySQL knows `text` type but it has nothing common with xml support. MS SQL Server or postgresql have support for xml. There is a special type for it. Another example, GIS coordinates. Postgresql has special types for it. In mariadb you can store those coordinates as well. Again, as serialized array or bunch of columns, but is it 'support' for GIS things in mariadb? imho, it's not. You can handle it from application, not db server.

[@AbdelhameedG]

Thanks dude, first time to learn about NoSQL databases and you made it easy for me

[@academind]

That's great to read, thanks a lot for your comment!

[@supa1009]

wow, this was an amazing tutorial. Thank you very much sir!

[@kelvinotieno4381]

I think this is the best explanation I have got for this question...Thanks a lot

[@MrDevianceh]

Now do Graph databases like Neo4j or Multi-model databases like ArangoDB

[@matteodalmasso8915]

Your video let people easily understand this kind of stuff that is not easy at all. My compliment for the clarity of your communication, well-done video! If you allow me, I just don't "agree" about the word "impossible" in horizontal scaling an RDMS. Modern relational DB can have good, fast and efficient horizontal scaling as well (Multitenant with shards, connection routing based and read/write routing base for example) when used with some cluster manager like Galera or MaxScale. I agree that is not an easy implementation and can have some deadly pitfalls such as high costs, set up complexity, weak schema design.

[@Vainsang73]

When you start a project, just use the technology you know the best (SQL or NoSQL), it will save you some precious time. If you are successful enough to reach the limits, you will have the resources to migrate to a different system, may it be partially or completely.

[@John_Fx]

that is terrible advice.

[@grafgrantula6100]

why?

[@MsMyWayOrHighway]

This is my favourite comments!!

[@delavago5379]

@@John_Fx how. Cause it makes sense

[@decreer4567]

Lemme code a whole OS in Python, including the kernel...... crap it took me over 10k lines and now I have to rewrite this in C and C++....

[@inspiringstocks]

My quick summary SQL = Schema, Relational. Use JOIN to collect all data. Data store in one place. Scaling across many hardware is difficult. NoSQL = No Schema, No relation required. Stored as "Collection" so that it can be read without join. Same data stored in many place. NoSQL works when the system needs lots of READ and not much WRITE.

[@tuneup6]

I can tell you as a data analyst not organizing your data should be a punishable crime. Websites gather lots of data which is important to the business it is supporting. Without proper organization there is no practical way to use the information in any databases you create as reliable business tools. I work very hard every day just gathering haphazardly stored data into hopefully meaningful reporting with mixed results. Please whatever data storage technology you choose please consider how that data can be retrieved and used to inform the underlying business. This should not be an afterthought but it almost always is.

[@UnderappreciatedTechies]

As is often stated, the unwashed will accept "garbage in, gospel out". They expect the data expert to perform magic and miracles.

[@farwanqv]

I can totally relate to your situation.

[@elspethstetson-gumper2666]

Good rule of thumb for coders - write your code as if the next person that has to support it is a homicidal maniac who knows where you live.

[@raghvendra87]

Thank you very much. These 20 mins were great investment for me. I am from Python background and I can clearly see that my application will be better served with MongoDB. thanks again!

[@academind]

Happy to read that, thank you for your comment!

[@mijmijrm]

how about comparison in terms of clarity, reliability, maintainability of code for the two types of db? (my gut says the flexibility of nosql implies more sophisticated/complex code implies reduced clarity, greater likelihood of bugs, etc .. but .. my gut is not a reliable source of info.)

[@snnwstt]

NoSQL sounds like a big unstructured Excel spreadsheet where anyone can dump anything into a new row, inserted anywhere.

[@MaqsoodAlamShafiq]

Thanks for sharing a very elaborated comparison of SQL vs NoSQL. At 19:46 of the video you mention we can face issues if DB becomes really really big. I have a some questions here: 1- What are the issues and which DBMS is favored? 2- Can you give an idea in terms of Gigabytes or number of records where we start thinking its becoming really really big? 3- Which one is easier for writing code for CRUD ops ?

[@prajwal2005]

Thank you! Just what I was searching for 🤸

[@antonkarpovich4201]

Just an amazing explanation! Thank you for such a wide and comprehensive comparison.

[@임창수-c7c]

Database course plz

[@academind]

No concrete plans to create one at the moment, but this might of course change in the future :)