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

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. :)

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

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

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.

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!

Thanks for the quick overview... I really needed that!

Appreciate the breakdown!

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!

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

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

You have explained it very nicely Max. Cheers!

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

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.

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

Will this video get a sequel?😂

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

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

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

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

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!

19:00 summary is pretty solid.

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

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

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.

amazing. I finally understand now.

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

Quite clear and smooth explanations. Much appreciated. Looking into taking your MongoDB course in the near future.

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.

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

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

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.

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

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?

Max, thank you for this video.. I really like all your videos which you have put on udemy as well.. your clear and simpler way of describing makes it very easy to understand the concepts... in this video, it would be helpful if you could add the differences related to ACID properties too.. is NoSQL DB a good choice where secured and strict locking is required while reading or updating data for example like banking environments? thank you

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

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

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

Thanks a lot for the quick and informative overview.

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

Thank you so much!) Great explanation))

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

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

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

Thank you! Just what I was searching for 🤸

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?

Best video out there on this topic! Thanks a lot!

Thanks a lot for making this video! Really cleared up some things for me.

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.

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)

21:00 My personal preference is to combine the index of elasticsearch and postgres

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.

thank you so much! this was very easy to understand and really well explained

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

This clarification was much needed. Thank you

The best explanation. I remember the no-sql (database/aplication) format from Lotus Notes/Domino. Based in a colection of documents like a database with many referenses (Document ID, ID, DB ID, Field ID, etc) to link to another Lotus notes/Domino documentes from another "databases/aplications".

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.

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.

Right on point! Thanks for the video, max!

Great video. Super clear, concise and useful. Well done!

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

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

Thanks. You just made it super clear!

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

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. :)

thanks bro you're amazing teacher

Great video and very clear on the differences. Thanks a lot! :)

Very clear explanation and visuals, thank you to point out the differences!

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

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 ? ;)

Awesome explanation comparing the both technologies! Thanks a lot for sharing it!!

Years ago I took a course of ObjectStore, it's like NoSQL where you store objects like in memory but in a object database.

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

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

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 ;)

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

like your clear pronunciation

This video explains the basic difference, there are few points I want to add: 1. NoSQL is more intuitive in real life. Think about a patient filling up a form in a clinic. SQL needs to break the data down into few tables, set all the columns and check all the types to process it. but NOSQL just save the whole document into the collection. It can be a complicated structure with array and nested obj in the document. This is the idea of row based vs document based. I found that I have saved lots of time of dealing with the database structure in SQL. That makes my development more effective. But of course, you need to know what you are doing or you will mess it up. 2. A major factor of choosing is what language you use in your service layer. If you use Node.JS (this is the most famouse one now), very high chance you will choose NoSQL becuase it just work so great together. The data you store and the object you process in Node is exactly the same (JSON)! This just save lots of conversion and mapping work. 3. Most of the people using MongoDB will define a schema on top of it, so that schema-less selling points just go away. But it is still a lot easier to modify the schema. You don't need ALTER statement to alter the table. That's save lots of hassle in deploying a new version. 4. The more experience I get with NoSQL, the more I realise how much it can replace SQL. It looks messy and you won't feel good in the beginning. But it's just the other way of organizing your data. You will have less relationship, and your relation join will be happening in the service layer. But if you are doing highly transaction application (Like a bank or payment stuff), you should still use SQL. The way you can open transaction, commit it, or roll back. You can never do this so well in NOSQL because of it's nature of lacking relationships across documents and collections.

I used to work with Lotus Notes about 20 years ago - it was like a document database - is that similar to NoSQL?

Its a great video.Well done. Absolutely liked the flow

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

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

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 ?

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

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

Simplified.. thanks

Love the way you explained the differences. Very helpful.

Keep en mind there are appliances like: PDW, Exadata, Teradata that support horizontal scaling easily, also it is possible to scale in a smp db (cluster deployments)

Database course plz

awsome explanation, thank you!

Great introductory video. It seems that collections are linked lists where each datum has its own meta-data, while entries in tables rely on the column headers. Are there hybrid systems that take advantage of both SQL and NoSQL? Maybe an id column in a SQL table that points to a NoSQL collection or a NoSQL collection of tables? BTW, do block-chains use NoSQL? Anyway, thanks much for a clear presentation.

Thanks for this, very clear and informative!

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.

You convinced me: I'm going to stick to SQL.

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

Great video! Thanks for the crystal clear explanation.

Thanks for this explanation!

School or no school?

The best video on the topic I saw so far 💪

Very nicely summarized, clear explanations as always!