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.
I'm sure E.F codd was a smart guy, but I think it's misleading to say that all tables should be called relations. SOME tables represent a set of relations while other tables represent a set of entities. I also don't like the tuple term. "Tuple" means a thousand different things now.
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.
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.
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
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!
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.
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.
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.
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*.
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.
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
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.
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.
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.
"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."
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 ?
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 :)
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.
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)
Video title is click bait & I feel you didn’t explain WHY the different NoSQL exist. What issue are they each trying to solve (i.e. why would they out perform a solution implemented in SQL)? NoSQL is a collection of DB paradigms (key-value, docstore, search engine, graph, etc). It would have been good if you had explained the key points that differentiate each type… imho
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...
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
MongoDB isn't a relational database management system. Saying MongoDB is better than any RDBMS without first specifying the data shows a real lack of knowledge. Key constraints don't exists in MongoDB. There are no referential integrity checks. We use MongoDB for blob storage and store the MongoDB keys in SQL Server. It's great for that but I would never outright replace a normalized SQL Server or a MySQL RDBMS instance with MongoDB. Maybe a lot of people see MongoDB as being better because they don't want to worry about optimizing indexes and execution plans, and they see the "read" performance gains...but that comes at a cost of data integrity. It's a schemaless structure which means consistency doesn't exist. It will eat anything you feed it which can be dangerous. Think about what happens over time as you add/remove properties from your JSON or add/remove reference data based on changing business rules. Think about what that conversion would look like in MongoDB compared to a RDBMS instance. I know I sound pretty critical of MongoDB but I don't mean to. We use it and it works well for our needs but it's not a replacement for RDBMS. More of a supplement. NoSQL shines in write-once-read-many scenarios.
I had a talk with a software architect who completely messed up my head by giving me multiple reasons on how a nosql is better than mysql for any large scale app. His arguments were mostly on how mysql can be a headache on architectural level when an app grows.
Ummm... he is not a software architect; if an app grows, you can create more tables, you can "alter table", just matter of seconds. The freedom he/she lets you believe you have in no-sql will be a nightmare very soon....
Sure. The trick is getting hired without one. if you plan to work for yourself, this isn't an issue. If you're looking at a small company, it's less of an issue. They're more likely to see what you can do than focus on paper credentials. If you're looking to get into a large corporation, you're going to need a degree as the HR departments will ignore you. I had a boss a few years ago that never finished his degree as he got hired out of college for a hefty some of money back in the mid-90s. Fast forward and he's applying to work for a large company and had what interviewed with the PM and several of the architects. They all have him the green light. HR sees he didn't have a degree and blocks the hire as the company requires a degree for that position.
05:15 - I beg to differ, that NoSQL is slower in reading data than SQL. Actually it’s the other way around. NoSQL was created to circumvent the bottleneck SQL creates with complex queries as in NoSQL databases the query is practically build in. That’s the main advantage 😉
Probably MongoDB would use less, because MySQL would add not just the data itself, but would also update indexes. However, this very same additional space consumed is what makes reading MySQL data faster.
@@boenrobot i think MongoDB uses more space, because you can't normalize your data (make it redundancy free), without a performance penalty. so you will have the same data in multiple places in MongoDB. i don't think indexes aren't that common in comparison
Thanks Kyle. I'm a more passive subscriber I would say, as time is limited and youtubers are not 😂 And so, very good video for my spontaneous question "hm, what is the difference between SQL and NoSQL databases anyway?!" Thanks for that 👍🏻🖖🏻☕
no. in my opinion, it should be exactly the other way around. you want strict rules on persistent data (the important stuff). less persistent data is less important
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! 🖖🏻👍🏻☕
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.
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.
I'm sure E.F codd was a smart guy, but I think it's misleading to say that all tables should be called relations. SOME tables represent a set of relations while other tables represent a set of entities. I also don't like the tuple term. "Tuple" means a thousand different things now.
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.
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.
I always get confused on these two DBs but you explanation was very clear and made a lot of sense
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
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!
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 _/\_
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.
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)
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.
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.
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*.
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
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.
Really nice start with the William Shakespeare
I thought it was an ad
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!
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
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
I love your channel!!! Can't stop watching. All your content is the best ☺️
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.
Really appreciate the way you explained this controversial topic. Keep it up bro
That's the explanation I needed. Thanks a lot man.
a video I wish I had watched when I was making my research on the topic a while ago
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. 😂
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.
Kyle, I never thought to ask.. did you do the intro riff yourself??
Um, Sql and NoSql are opposite ? Not so, just somewhat different take on structure vs flexibility, both are records of data.
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.
how can i work on SQL as Team in local host database ?
Nearing 500k subs! What an achievement!
Thanks!
@@WebDevSimplified This escalated quickly
Amazing explanation , always motivates me to learn futher
"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."
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 :)
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.
i was like woah where the hell am i in the first 10 seconds
If i use a SQL database as a NoSQL the performance would be the same? For example, using PostgreSQL Json column.
Is there some morse code or som'n in how much he's blinking?
Watched the rest of your video, is NoSQL databases easier to use in comparison to MySQL?
thank you for this!
With some illustration and diagram the video would have been much more interactive and interesting
Awesome, thank you.
thanks
Nice explained 💪🏻
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)
What database should I use for a messenger app
Video title is click bait & I feel you didn’t explain WHY the different NoSQL exist. What issue are they each trying to solve (i.e. why would they out perform a solution implemented in SQL)? NoSQL is a collection of DB paradigms (key-value, docstore, search engine, graph, etc). It would have been good if you had explained the key points that differentiate each type… imho
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
at first I thought that you're gonna be explaining Shakespeare's play 🤣
wow 16 seconds in, what a intro 😂
Most data is relational.
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
Will you make a tutorial on game development
Thank you.
Thanks
MongoDB isn't a relational database management system. Saying MongoDB is better than any RDBMS without first specifying the data shows a real lack of knowledge.
Key constraints don't exists in MongoDB. There are no referential integrity checks. We use MongoDB for blob storage and store the MongoDB keys in SQL Server. It's great for that but I would never outright replace a normalized SQL Server or a MySQL RDBMS instance with MongoDB.
Maybe a lot of people see MongoDB as being better because they don't want to worry about optimizing indexes and execution plans, and they see the "read" performance gains...but that comes at a cost of data integrity. It's a schemaless structure which means consistency doesn't exist. It will eat anything you feed it which can be dangerous.
Think about what happens over time as you add/remove properties from your JSON or add/remove reference data based on changing business rules. Think about what that conversion would look like in MongoDB compared to a RDBMS instance.
I know I sound pretty critical of MongoDB but I don't mean to. We use it and it works well for our needs but it's not a replacement for RDBMS. More of a supplement. NoSQL shines in write-once-read-many scenarios.
That hair though!
I personally prefer NoSql
please how did you grow your channel to over a million subscribers. thanks, if you would like to share
I had a talk with a software architect who completely messed up my head by giving me multiple reasons on how a nosql is better than mysql for any large scale app. His arguments were mostly on how mysql can be a headache on architectural level when an app grows.
Ummm... he is not a software architect; if an app grows, you can create more tables, you can "alter table", just matter of seconds. The freedom he/she lets you believe you have in no-sql will be a nightmare very soon....
What about NewSQL?
'To Sql ' or 'Not to Sql ' OR 'what all to SQL ' are the three qustions :) 😀
thx a lot
good job
love you sir
Other than scalability n maybe high performance in specific cases SQL beats No SQL any day
Hey!!
need to ask one thing ??
is it possible to become a software engineer without a cs degree??
pls reply??
🙏🙏❤❤👍👍
Sure. The trick is getting hired without one. if you plan to work for yourself, this isn't an issue. If you're looking at a small company, it's less of an issue. They're more likely to see what you can do than focus on paper credentials. If you're looking to get into a large corporation, you're going to need a degree as the HR departments will ignore you.
I had a boss a few years ago that never finished his degree as he got hired out of college for a hefty some of money back in the mid-90s. Fast forward and he's applying to work for a large company and had what interviewed with the PM and several of the architects. They all have him the green light. HR sees he didn't have a degree and blocks the hire as the company requires a degree for that position.
can you win a gold medal in the olympics without doing any training and without representing any country?
you can but good luck with that
PostgreSQL for the win.
Hello, Kyle. Are you Jewish and from Jersey as well?
great boss
LIKE for the intro 😂
sir plz plz plz make a video on blog again with adding images also with nodejs express
05:15 - I beg to differ, that NoSQL is slower in reading data than SQL. Actually it’s the other way around. NoSQL was created to circumvent the bottleneck SQL creates with complex queries as in NoSQL databases the query is practically build in. That’s the main advantage 😉
SQL for me
Bro, it's time you do something with your empty gray background. 😉
Thanks! You are rock!
I hate algoexpert ads in between 🙏🙏
So you want to a software engineer at google?
Money from Clement's pocket into Kyle's LOL
NoSQL is Cool especially when working with modern stuffs
such as Django and Nodejs
But Much respects go to SQL shit! #KeepSimplifyingWebDev
for the same data, which database uses more space? MySQL or MongoDB and how much difference is there?
Thank you for the amazing content!
Probably MongoDB would use less, because MySQL would add not just the data itself, but would also update indexes.
However, this very same additional space consumed is what makes reading MySQL data faster.
@@boenrobot i think MongoDB uses more space, because you can't normalize your data (make it redundancy free), without a performance penalty. so you will have the same data in multiple places in MongoDB. i don't think indexes aren't that common in comparison
Thanks Kyle. I'm a more passive subscriber I would say, as time is limited and youtubers are not 😂
And so, very good video for my spontaneous question "hm, what is the difference between SQL and NoSQL databases anyway?!" Thanks for that 👍🏻🖖🏻☕
it was Hamlet lol rshkkjk
Neither: en.wikipedia.org/wiki/Relational_algebra
Gold mine.
this guy went to google searched SQL vs no SQL and made a video about what he read. useless video offers no insight or useful info
Stop looking at me like I'm the only person in the world who matters!
You look like Henry Cavill , withcer
My General rule of thumb is NoSQL for highly persistent data, and SQL for less persistent data such as Data Lakes. That's my axis.
no. in my opinion, it should be exactly the other way around. you want strict rules on persistent data (the important stuff). less persistent data is less important
SQL HANDS DOWN
That's Hamlet, not Romeo & Juliet.
I know but it didn't sound as good when replacing the name Hamlet with a DB name.
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 .
SQL
release your haircut simplified
It is S.Q.L. I can't watch this, every time I hear you say it I cringe 😫. I love your other videos tho!
first
Kylespeare 😂
Spoiler Alert: Redis and JuliaDB both die in the end.
the first 15 second I felt like I clicked the wrong video 😂
lol
Lmao
bro sold his all furniture to buy a guitar 🎸
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
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.