Which Is Better? SQL vs NoSQL

Bro learn you put some diagrams or illustration than just talking with you face on the screen , its hard to understand what you are talking about .

That hair though!

bro sold his all furniture to buy a guitar 🎸

How hard would it be to create an online database that voters could voluntarily use to add their Presidential vote. A system that can confirm your state and status, legal, alive or dead etc.? A system independent from the official election but still confirms the vote entered is accurate and legit. A system that is obviously not 100% accurate but can still be used to possibly expose extreme discrepancies in the official election data?

Is there some morse code or som'n in how much he's blinking?

You look like Henry Cavill , withcer

SQL HANDS DOWN

Awesome, thank you.

I've always heard people hating on mongo, like theo, but I've never quite understood why? I like postgres and find it to be pretty good, but a lot of times it feels stricter and slower, in my experience. I'm far from a database expert, but I really find it odd that people are so obsessed with the "relational" model. As if you can't essentially use foreign keys or do joins in mongodb. You pretty much can, though they might go by different names, and I've heard many people point out how silly a JSON oriented database is, but I can't really see an argument for why excel spreadsheets are so much better. I don't see anything wrong with either approach, but I'm struggling to see a lot of advantages for using antiquated SQL dbses other than certain key performance metrics and data integrity. That being said, it's just weird because NOSQL gets a lot of hate, but I've yet to hear the legitimate criticisms of it. I mean, I'm sure there are some, but I don't really understand why people think that data can't have relationships in MongoDB. I mean, you could argue that the structure of SQL databases causes them to more often return the data that you are looking for, but it also creates a lot of complexity in rules, functions, schemas, writing, etc. On the flip side, with NOSQL it always seems like the structure of your queries is a lot more important than the structure of your data. The end result tends to be pretty similar, but the approach is quite different. Is this just the angry grumblings of devs that don't like to change their process for doing things or are there greater issues with MongoDB "underneath the hood" so to speak? I'd really like to know because on the surface most of these arguments seem kind of arbitrary unless you get into the details. Good video. I mostly agreed with the points. I could certainly see the devil being in the performance metrics, but it doesn't really seem to be in the capabilities.

Everything I've been reading and watching has been saying an opposite conclusion, that nosql is better for reads while sql is better for writes.

This is all confusing me, but what I got was nosql expects you to duplicate data wherever you need it. So when making requests, all the relevant data you need is right there and the database doesn't have to do any extra searching for it. Sql wants you to have data in one place, and just make references to it wherever you need. So if you ever want to update data, you just do it in that one place it's defined and it'll be accessible everywhere.

That'd make sql way better for writing data (as you only have to do it in 1 place), and nosql way better for reading data (as all your relevant information is already together)

Can someone correct if I'm wrong, but isn't this the exact opposite of what this video is saying?

This guy loves camera time. Show some diagrams like in thumbnail geez. Useless.

"To sql or not to sql, that is the question. Whether tis nobler in the mind to suffer the keys and joins of outragous databases, or to take arms against a sea of tables and by opposing end them."

thank you for this!

please how did you grow your channel to over a million subscribers. thanks, if you would like to share

Kyle, I never thought to ask.. did you do the intro riff yourself??

SQL: for times you need to read & write data

NoSQL: for times you want to hoard json that you don’t want to bother parsing and you rarely need to look anything up.

I absolutely love the intro and the entire explaination

Definitely need some images, slides during the explanations.

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)