Which Is Better? SQL vs NoSQL
ฝัง
- เผยแพร่เมื่อ 14 มิ.ย. 2024
- The age old debate of SQL vs NoSQL has been going on since the day NoSQL was conceived. In this video I will detail the pros and cons of each so that when you are ready to choose a database for your next project you will know exactly which one to choose.
🌎 Find Me Here:
My Blog: blog.webdevsimplified.com
My Courses: courses.webdevsimplified.com
Patreon: / webdevsimplified
Twitter: / devsimplified
Discord: / discord
GitHub: github.com/WebDevSimplified
CodePen: codepen.io/WebDevSimplified
⏱️ Timestamps:
00:00 - Introduction
00:40 - SQL Features
01:46 - NoSQL Features
03:53 - When To Use SQL Databases
05:52 - When To Use NoSQL Databases
08:57 - Conclusion
#SQLvsNoSQL #WDS #Databases
William Kylespeare
😁😁
hahahaha
Kyliam Cookspeare
@@blessingseverywhere3140 lmao. Way more creative than mine
@@dooddotjs3910 I don't care if it's more creative than yours or not, my friend. I just want you guys to smile.
the first 15 second I felt like I clicked the wrong video 😂
lol
Lmao
When he said 'To sequel or not to sequel that is the question' i was in tears. Truly one of the best lines of all times
In fact the "relational" part of database does not refer to the relations between different tables, but to the relational model as laid out by E.F codd. In this model, tables are called Relations and rows are called tuples.
Your explanation are nice
If you show slides and image to explain
it will be much better and much easier for beginners to relate things you say and understand better
Give taking your own notes a try! Serious, listen to a video more than once if needed, pause and take a short note.
Much better understanding AND better glued in memory, than just "consuming"/watching someone's slides! 🖖🏻👍🏻☕
@@maxfrischdev Yeah right
@@maxfrischdev expert tip, thanks Max.
Nice, quick explanation and that top-left corner perfectly aligned with room’s corner line👍
Was really stuck with what setup to choose for a new project. I use SQL at work and NoSQL for side projects and have always felt more comfortable with NoSQL. Your last point about choosing whatever you're most comfortable with really resonated with me, great video!
There are reasons why big companies use nosql for one thing and sql for another. Google Docs will probably use nosql to store your documents since most you do is write to it and only read the document once to start editing it. As a company its important because you can reduce costs since the performance is better but you also use less resources. Thats also why autoscaling is used to reduce useless resources.
I always get confused on these two DBs but you explanation was very clear and made a lot of sense
SQL can handle many connections (you made it sound like SQL can only manage a handful of connections). If there is an appearance of “slowness” it’s likely related to the isolation level \ locking, which can be managed with good database design (9/ 10 times perf issues are attributable to poor developer choices). The choice between the two systems should be about isolation level requirements , scale (data volume \ geo-distribution) and the actual data model being stored.
If you’re dealing with high transaction financial data, your likely not gonna go no sql. Likewise, if your storing IOT data then no sql is going to be better. If you’re never going to shard your data, mongodb is not worth it as SQL will outperform it.
best overview and comparison i've got so far! thanks a lot! 👍
3:05 Redis saves data to the disc periodically and loads it on startup.
But storage persistance strategies can be modified.
I love your channel!!! Can't stop watching. All your content is the best ☺️
Love this video! I greatly appreciate the perspective!
Thank you man, is just what I was looking for!
This actually really helped me understand both! Currently I’m learning MySQL with php and I may consider using react with it. I say MySQL I enjoy for your explanation of the great structure and columns and I care about readability. Though I may learn mongodb in larger scale applications in the future. Since mongodb sounds great for big projects
Ew php
@@Rust_Rust_Rust 😆 🤣 😂
@@Rust_Rust_Rust hahaha. your comment
@@Rust_Rust_Rust Most loved language not loving back
That sloved my confusion... thanks 😊
And im also waiting for Javascriptsimplified course to reopen registration.
That's the explanation I needed. Thanks a lot man.
I absolutely love the intro and the entire explaination
Huge thanks. I think if you add a table of comparing these two type would be much better for summarizing.
Really appreciate the way you explained this controversial topic. Keep it up bro
Correct me if I'm wrong but if you're familiar with DBMS concepts you can adapt to both SQL and Nosql right?
100% no brainer you need to how to connect foreign keys joins left join more specifically
Sure!
Amazing explanation , always motivates me to learn futher
Hey what do you think of services like Firebase in context of whether or not it'd be the future of database? Also is the pricing worth it?
This was helpful. It would be even more helpful if you provide brief reasons for each claim on why SQL or NoSQL is better. For example, why is it usually quick to write but harder to read from a NoSQL DB?
i think its because NoSQL you can just shove objects in the database because order doesnt matter since the processing is done upon queries, hence why its harder to read.
it's not entirely accurate either - it depends on the scenario - there are some query examples that have nosql being 100x faster at reading compared to a sql query that involves multiple joins compared to a nosql read where it's just pulling a full document based on id
whether sql or nosql is better fully depends on use case
Because NoSQL is for the times you don’t need to READ the data
Man, you speak very fast but with a excellent pronunciation. It is really good for me, since I'm learning english. xD. Excellent comparative, and thank you for comment about Json in PostgreSQL.
I like your keyboard typing sounds , Can I ask you for a link on amazon for this keyboard? Thank you. : )
A legit conclusion. Both technologies are proportionally good. The SQL allows vertical scaling, while NoSQL - horizontal scaling. The SQL simplifies the usage of MVC, MVVM, Object Validation and bindings, while the NoSQL simplifies the ability to make changes into projects (very useful for e-commerce dbs).
The idea to use JSON data as TEXT in SQL is promising as something intermediate.
Amazing explanation sir!
4:54 Isn’t one of the benefits of a nosql database like mongodb is that you optimize for reads by having denormalized data at the cost of more costly writes?
Please make this series of comparing different technologies like SSR vs CSR, React vs Vue, Tailwind vs Bootstrap etc
That's a good idea
@@WebDevSimplified A humble request for more TypeScript content please _/\_
bigger companies use tons of different database types for different purposes but imo if u learn how to optimize SQL databases really well then u can apply these concepts to the other types
I've been dabbling in SQL a lot more lately. I'm actually considering building my newest project using it as the database. Most likely going to go with PostgreSQL. Thanks for the content Kyle. Much love my friend!
a video I wish I had watched when I was making my research on the topic a while ago
Hey man, usually a fan of the videos but I feel like this one fell pretty short. Alot of surface explanation without any real world examples which I feel would help extremely
An example: Suppose you are storing customer shipping addresses.
On a SQL database, you might have columns for house number, street, city, state, zip code; which works for US addresses, but not necessarily for addresses in other countries. On MongoDB, you could format their address differently depending on which country they are in. But the database would not check the address is in the correct format, it would accept anything, you would need to do your checks in the application logic.
Kyle, I never thought to ask.. did you do the intro riff yourself??
Great explanation!
I wonder, what about encoding foreign characters?
I made a project with MySQL and I had lots of problems with encoding Japanese (language learning website). I hope other databases are set to support utf-8 by default.
I had to set up encoding in like maybe 4 places for it to work...
you could specify charecter encoding when creating column
Really nice start with the William Shakespeare
I thought it was an ad
Imo you missed the most important feature of sql databases, which is ACID transactions. That's the fundamental stone of pretty much every enterprise application
True, although the larger enterprises have been transitioning to microservices and cloud architectures. Due to the CAP theorem, these distributed solutions are ACID non-compliant*.
Hello Kyle, big fan of your videos ! I don't understand why wou say that non-relational databases can be more "fuzzy" because the data written goes though less checks compared to a SQL db. If I take MongoDB for example you have to create a model that define what kind of data to expect (and possibly further restrictions) and to setup some validation criteria that data has to go through to be stored in the database. Have a nice day.
The thing with mongodb is that you DON'T HAVE TO define models, but you CAN if you want to.
Kyle, you're great teacher!
Fast Fast and very every useful. Thanks
This guy legit looks better than most of the male models appearing on product advertisements and could easily land ads showcasing hair products.
He reminds me of the Winklevoss twins for some reason lol (the movie actors not the real ones)
thank you for this!
Nice explained 💪🏻
This is first unbiased video I have watched till now. Everyone else telling that NoSql is just better and whatever advantage they tell can also be applied on SQL
Watched the rest of your video, is NoSQL databases easier to use in comparison to MySQL?
I still do not understand why would I use noSQL when I could simulate it in mySQL by (for example) adding a text field that contains some json. Is ti much faster? Or is there something else I'm missing)
I will learn both of these.
Awesome, thank you.
Another excellent video
Hi Web dev Simplified; I would like to create my first CRUD app learning REACT at the moment. Soon I will start learning node.js and afterwards MySQL. I know how to perform basic queries within tables in a database but not between multiple tables. I am familiar with creating new database and creating new tables too. My question is I am decent on the front end could you provide resources which teach how to use a backend technology alongside MySQL or even postgreSQL to store your data for a basic blog app. My thoughts are to create a blog app which will allow a maximum of at least 10 people to create a very simple profile and post messages on a board. No securities, no cookies something locally from my hard drive. Figured I start small and work my way up. Any guidance would be appreciated.
If i use a SQL database as a NoSQL the performance would be the same? For example, using PostgreSQL Json column.
Best practice for me : Sql for Database and Firebase Remote Config as a json config for the App
For Internet of Things like Smart Energy Meters, which will be a better solution for storing the data?
i personally would go with MySQL/MariaDB, but NoSQL like ElasticSearch/Apache Solr is fine too - this heavily depends on your application needs.
In my exp (only done small projects at university/intership), noSQL are a little better for IoT but it still depends on the application
My home automation (power usage, solar generation) is in MongoDB. First few years it was in SQL-Server, then switched to MongoDB. I'm storing about 130 samples per minute for the past 5 years, I aggregate the date / device into 1,15,30,60 min, 24, month, year. It's simply flawless.
I came here to appreciate PostgreSQL and your Ibanez lady
Hello! Coming from NoSQL (Mongo) to SQL
What I don't like with Mongo is that if you delete a document (A) in one model that references another document from another model (B), then B is not deleted, you need to handle this manually
If I understand well, there is no such problem with SQL databases ?
the video says that SQL pretty slow to query if there are a lot of users accessing it
It depends on DBA. Problem that you mentioned is called referential integrity. If you don't implement correct technique during the design you might get a situation when a row from table A is deleted and another row in table B still references deleted row in table A. Thus, you will end up with inconsistent or redundant data. SQL server for example uses a way to CASCADE the changes (either update or delete) by primary key, this way all the references to the deleted or update data will propagate through out the database :)
What database should I use for a messenger app
Nearing 500k subs! What an achievement!
Thanks!
@@WebDevSimplified This escalated quickly
bro sold his all furniture to buy a guitar 🎸
Thanks
Hmmm, I'm storing json data to MySQL atm.
yup you can store anything and then just parse the string back into JSON....
Win win haha.
@@chizuru1999 How are you going to search through the string then? With NOSQL you can search and select on the Objects
There is always some rebel who do this. LMAO
@@chizuru1999 That is not a win win. Parsing data takes time, decreasing performance. If you want speed, actually use columns and rows.
@@hnccox how can you search on select objects in nosql.. nosql doesn't have schema and there would be only 1 unique key to differentiate the data
oh man, you brought Sheksphere....
love you man.
ah yes, sheksphere
Shreksphere
Will you make a tutorial on game development
I want to create a database in order to receive data from the Arduino meteorological monitoring device (temperature - irrigation speed - humidity). The degree of measurement is sent every 30 minutes, so what is the best type of database
influxdb
sorry love your vids super strong content but wasn't the quote from hamlet, or was that part of the joke ??
you missed one of the main points, the acid vs base model.
most of the time, I see those models as one of the main decision maker on what to use.
Thank you.
Which one is better for mobile?
I get the feeling that you've never worked as a database administrator for any large-scale system. Some of the things you said make no sense to me at all. There's a huge difference between a normalized, relational database in a production corporate database vs. a transient data store in an app or a website.
can you detail more? Which are the differences?
If you use it properly then there are zero joins in NoSQL database and reading is faster than SQL. Cost of 1 GB storage is super low. So you can repeat data without worry.
how can i work on SQL as Team in local host database ?
thanks
thx a lot
I use Mongo cause the logo looks cool 😎
ahahahah, im switching to ruby cause it sounds cool and logo is just so beautiful
@@arthurweasley5857 nobody uses ruby nowadays in the industry, better use mongodb or mysql
thanks your explanation is very good. SQL is the best for relational data.
Make video about mysql or mongodb with redis as a cache
Sir plz plz make a video on blob type url in js
So to sum-up
SQL
- fast to read
- you can count on constant a format
NoSQL
- fast to write
- hard to update
- better at handling lots of connections at the same time (why?)
- better at scaling
- good for unstructured data
omg I swear I just thinking about this question in few minutes before open youtube and then... this happened
Have you ever tried thinking of a couple of millions of dollars?
You absolute dreamer.
I know it's ridiculous right. but the same time it was mindblowing to me
But, you know.. I couldn't hold back my own thoughts, it just randomly passed
@@elmyllo4219 may be it’s not that ridiculous. 😂
I would like this entire video as a text document 😂
Among the people who talk about programming on youtube, I prefer your approach. You always bring the subject well summarized, contextualized and didactic. It is complex to do simple things, isn't it? ... Only those who have very clear reasoning can do this. The simple fact that you put the noSQL image as branches of a tree, already shows your skill. Keep it up... and you will be helping to build a solid foundation for the evolution of technology.
MySQL do have JSON type column too
Definitely need some images, slides during the explanations.
What is Chris Pine doing here ?
Also sick Jackson ,just chillin in the corner
Just depends on what your app needs.
love you sir
What a creative intro 😂😂
i was looking for it 🤣
MySQL also supports JSON columns.
good video, userfull for me
MySQL is great for correlational studies, especially for routine data. However, it takes time to organize the tables.
No-SQL is great for chaotic and dynamic based data. Think of data tracking a bipolar person.
Is there some morse code or som'n in how much he's blinking?
good job
Play something with that guitar
Plz make it on AWS Terraform
at first I thought that you're gonna be explaining Shakespeare's play 🤣
With some illustration and diagram the video would have been much more interactive and interesting
Framer Motion for React please 🔥🔥🔥
great boss