SQL vs NoSQL Explained

In this video, I talk about the difference between SQL and NoSQL. I talk about the main features of both technologies categorized by Structure, Storage, Scale, and Accessibility. I provide some tips on how to decide between them when starting a project, and example use cases on when to use SQL over NoSQL and vice-versa.

00:19 What is SQL?
04:58 What is NoSQL?
07:38 When to use SQL vs NoSQL
09:47 Example Scenarios

🎉SUPPORT BE A BETTER DEV🎉

📚 MY RECOMMENDED READING LIST FOR SOFTWARE DEVELOPERS📚

🎙 MY RECORDING EQUIPMENT 🎙

💻 MY DESKTOP EQUIPMENT 💻

📚 References:

☁Topics covered include:
What is SQL
What is NoSQL
SQL vs NoSQL
How to pick between SQL and NoSQL
Example use cases

🌎 Find me here:

#AWS
#SQL
#NoSQL
#Serverless

[elenaperez]

The' when to use what' section was really helpful and just when I thought it couldn't get any better, you included a 'how to pick' section. Good job! Thank you.

[GRIEFify]

No clutters only content. Well articulated and explained. Thanks.

[haldur]

Looked at another walkthrough, had no Idea what NoSql was afterwards. Looks at this video with pictures and examples, gets it in 2 minutes.

[princeofgonville]

Great summary. The main motivation for development of non-relational databases is around scaling. A relational database scales out reasonably well for reads (there is a clue in the name "Read Replicas"), but there is still a single master, hence a bottleneck for writes. The design of KV stores was largely to get around this problem. Some of the constraints of a relational DB are relaxed to provide scalability (see CAP theorem).

[Larryjazzy]

Finally!!! I've been looking for a straight to the point video on relational vs non-relational database and this video explains it succinctly and even more. Thanks a bunch

[pravinupadhyay]

I had to login to youtube just to subscribe to your videos. I really like them, easy to follow and very relevant. Thank you for these wonderful videos.

[hunterwei]

One of the best explanation for SQL vs NoSQL on Youtube！

[kino-xwxg]

thank you so much for this video, I have been struggling to understand what NoSQL is but this video really helped

[rickrackleyjr.]

Great example! Information was presented very clear and easy to understand.

[andrest.]

your videos are incredible. I am from another background (electronic engineering) and I am trying to move into the cloud computing field. So I find your videos really useful. Thanks!

[LadyPixyCompany]

Finally I find what I looked for. It is quick and simple and clear explanation and I looked for this short and complete answer it for my aws interview. Thanks thousands

[marcello]

missing out one important scenario .. transaction actions where integrity and atomic writes are key.. but rest of the video was quite good to understand thanks!

[yashsolanki]

This is by far the best explanation I have come across🙌Your channel is a gem

[altayezekariyas]

The best explanation i found on internet

[chriszhang]

Great video! Flexible access patterns is definitely a big Pro for choosing a database like postgres.

[MouradMourad]

Very good, thanks a lot. However I am not sure to understand how SQL can be better when access patterns are not well defined ? To me SQL is to used when data model and schema is strictly defined, when it is predictable and not going to change a lot ...

[drizztyang]

My experience is that NOSQL can also fit you if the data models is small and the primary key is natural. It is easy to change the data structure or add new attributes.

[nagatouzumaki]

You really clearly explained in a lucid way!

[harikrishna]

Very helpful. Thank you for your time creating this

[hyiux]

2:22 Relation ≠ Relationship. "Relation" in relational databases refers to the concept of finitary relations in mathematics. In mathematics, a relation is a subset of the Cartesian product of multiiple sets. In database world this translates to a table. So, Relation = Table.