I am so impressed by this. Everything from your articulations to your drawings to the video editing. And of course, your knowledge base is impressive yet you make it so consumable.
beautiful! perfection! I was having a hard time trying to understand what the difference is, and many videos just talked about sql and nosql, but yet I couldn't understand. This video visualizes the differences and is easy for a beginner like me who has no experiences in dbms. Simple, yet very efficient!
This was the best and easiest-to-understand video on this subject. Since I just started taking database classes, it is good to know that The Cloud Girl thought about some of us: the rookies in the Database field. Thank you!!!
I love NoSQL Databases. It's been a long time since I don't use relational database in my projects and some customer projects. Thanks for you video! Additional information: RavenDB is BASE and ACID 100% 👍
By "data changes", do you mean changes to the * of the data? It seems so from the context. SQL databases handle frequent data changes (inserts and updates) just fine, but changes to the structure of the data (altering tables) are more difficult than in NoSQL. In my experience, NoSQL is better at frequent-reads-infrequent-writes whereas SQL has no trouble with frequent writes. Thus SQL being preferred for OLTP as you said. Very good presentation, thank you!
Thank you Priyanka! I was finding it surprisingly hard to find a suitable explainer in terms accessible to me. I will enjoy poking around your channel more!
Wau! Amazing description of the topic! Thank you, it is great pleasure to watch your video - it would be nice to see practical usecases for each DB from you, maybe one case with 100000000 data items but realization by this two ways -> and there we can see practically what DB is better for
Amazing explanation. I was also hoping to see the horizontal vs vertical scaling in your words but nonetheless it's really a one stop video for SQL vs NoSQL on RUclips. :)
Excellent material & presentation though have to say i'm a noob & probably not the intended target demographic. Curious about any differences in how secure they are
Excellent video ...very short to the point and no nonsense beating around the bush .... If SQL Databases are required to be vertically scaled then how does it meets the scaling needs as vertical scaling has limits in terms of CPU / MEM / Storage ? On event day how is it possible to achieve scaling out when horizontal scaling is not possible in SQL databases and also scaling in ?
Great video. thanks to everyone involved. always a blast to see someone who knows about the subject so much, she has to be mindful she doesn't introduce too many concepts. cheers. u introduced just the right amount imo. though, i still am not clear on how nosql is not just a usecase of sql. all the advantages of nosql seems to be available due to its limitations. i mean, i can just create a table on an sql db with two colomns, key and value. a primary key and a json field. then i can scale it horizontally as i don't have to worry about keeping related rows on the same node. there won't be any related nodes. it will be very flexible too as all the data is json. i mean, all the advantages of nosql are still available in sql if u give up sql advantages. obv, i'll still use nosql regardless. it's easier to just use redis than configuring postgres to hold a cache table on RAM. however, i wouldn't develop redis as a whole new system instead of a postgres plugin/extension if i were to be in that position
Hi, I have two questions. Q1. Can non -structured database be designed into 2 parts : static(structured) and other being(dynamic) thus can imbibe both ACID and BASE. Q2.Also is no-SQL not better for API versioning improvements?
9:03: NoSQL are bad for analytical processing. I dare to say they are also bad for being queried on anything other than their primary key. They are good for allowing loose structure and keeping their one to many dependencies together.
I do not agree with the scaling and big data argument in the sql vs nosql decision. Working with both for years I can guarantee its not about data sizes nor structure, sine non structured data can't be fetch until structured. It's about how and when the data is structured and scaling is about horizontal vs vertical scaling. Individual databases scales differently, so it's not about sql or not. Oracle databases can scale both ways and handle as large data amounts as any. It's about how you need your data fetched and how large a subset of the total data set you need to search through.
I am curious, whether the things mentioned here for NoSQL databases are true for Graph databases as well. For me it seems a database where the joins are more important and easier than in the SQL. So for me graph databases seems to be on the other side of SQL than the document based once. So is it faster too and can store that large data volume, can use horizontal scaling and can they be just eventually consistent?
Choose a NoSQL database because you might decide to add fields as the application grows. And you will be able to easily do that in NoSQL database. On Google Cloud I would recommend Firestore.
but, the DATA is usually NOT stored on the SAME SERVER....the Tables are stored Separately from the Actual Data Being Stored for Retrieval.....Example: A Letter Form needs Data put in. Hmmm....The Data has already been entered by the Data Input Person in a Document. It was entered by a Word Processor and Saved to a Letter Storage for the Word Processor. Now a person looking for the Data to Send a Letter to Customers but, there is No Data Available at the SQL Program Server -- So the Letters cannot be sent -- UNTIL -- the Location to Said Data has been Entered on a Table Sheet so that Every Person Needing to send that Letter -- or Letters -- has been told where the Data can be found and the Whereabouts of the Form. This description might be too simple....sorry! Is my view correct? Or no. Thank you.
@@pvergadia I can tell! I really enjoyed your video it was super clear and well explained. Wish my uni teachers were half as good... Seems like you're running two front lights, I would turn the shadow side one up just a fraction too. Best of luck!
![Hunxho - Ball Forever [Official Video]](http://i.ytimg.com/vi/nki9ZTF9Uls/mqdefault.jpg)
This was a fantastic overview. Clear, Concise, Accurate, and brilliantly visualized.
I am so impressed by this. Everything from your articulations to your drawings to the video editing. And of course, your knowledge base is impressive yet you make it so consumable.
Thanks @Marcella!
I hope you do more videos soon ❤
I will surely create more soon! Thanks for the encouragement.
beautiful! perfection! I was having a hard time trying to understand what the difference is, and many videos just talked about sql and nosql, but yet I couldn't understand. This video visualizes the differences and is easy for a beginner like me who has no experiences in dbms. Simple, yet very efficient!
This was the best and easiest-to-understand video on this subject. Since I just started taking database classes, it is good to know that The Cloud Girl thought about some of us: the rookies in the Database field. Thank you!!!
Finally! She's got her own channel!
Great content, thanks to RUclips algorithm for suggesting this video and thanks to you as well.
Amazing to hear, thank you!!
I love NoSQL Databases. It's been a long time since I don't use relational database in my projects and some customer projects. Thanks for you video!
Additional information: RavenDB is BASE and ACID 100% 👍
This was incredible! I hope you come back to make more videos you’re a remarkable teacher
Wow this channel is a Gem! Needed a refresher on this topic and found gold. Subbed!
I have to take this as a class and I have been intimidated by this subject. I was recommended your video by RUclips and I’m happy to have found you.
The best video on this topic I found on YT. Thank You!
By "data changes", do you mean changes to the * of the data? It seems so from the context.
SQL databases handle frequent data changes (inserts and updates) just fine, but changes to the structure of the data (altering tables) are more difficult than in NoSQL. In my experience, NoSQL is better at frequent-reads-infrequent-writes whereas SQL has no trouble with frequent writes. Thus SQL being preferred for OLTP as you said.
Very good presentation, thank you!
This is so well explained. You are so clear and informative. Thank you for your excellent delivery!
simple explanation shows how good you are, some explain with new confusion to arise, so good job
You produce some of the most outstanding videos. I especially like you tone, pace, and comprehension.
Thank you Priyanka! I was finding it surprisingly hard to find a suitable explainer in terms accessible to me. I will enjoy poking around your channel more!
That was a great explanation.
And a simple person with a non CS background can understand DBs well by watching this video
So great to hear that you found it helpful.
Some SQL based MPP databases do offer Horizontal and elastic scaling as well. They are not limited to vertical scaling only.
Really good overview, thank you!
Concise, chewable bytes, easy-to-digest explanation. Thanks for sharing!!!
Clearly articulated .. Thanks for the video
Beautifully explained with simple and concise examples, well done!!
Best explanation I've seen yet. Thank you and well Done.
Wonderfully done.
Yooo this is the pub sun playlist girl from google channel! Good to know she has her own channel!
Best ever explanation on the databases I came up so far. Thank you!
neat handwriting, thanks
A great presentation of SQL and non-SQL databases nicely organized presented and explained bravo! Thank you for a lesson well delivered.
Big Fan ... Loved the way you explained it!!
simply awesome, loved the way you explained and quoted the examples.
Absolutely wonderful, from delivery to knowledge shared to beautiful layout. I learn so much from you Ms. P!
Thanks for sharing you feedback, glad you found it helpful.
This is the best channel! You have a talent to simplify complicated topics. ✨✨
Thank you!
Wau! Amazing description of the topic! Thank you, it is great pleasure to watch your video - it would be nice to see practical usecases for each DB from you, maybe one case with 100000000 data items but realization by this two ways -> and there we can see practically what DB is better for
Great explanation. I understood everything perfectly.
Very clear. Nice clean diagramming as well as explanations of the differences at a high level. I love it!
Best explanation I have come across on these concepts. Thanks so much!
Amazing explanation. I was also hoping to see the horizontal vs vertical scaling in your words but nonetheless it's really a one stop video for SQL vs NoSQL on RUclips. :)
That's the best explanation of sql nosql relevant to gcp
Excellent material & presentation though have to say i'm a noob & probably not the intended target demographic. Curious about any differences in how secure they are
This was explained so well. Thank you!
Thank you!!
Well explained and completely awesome!!
Beautifully outlined. Thanks!
Fantastic video! Probably the best explanation on the topic
Excellent video, excellent explanation
Clearly explained. Thank you
You are an amazing teacher, Thank you very much
Fantastic video! Thank you so much for making this 😄
Best explanation. Thanks!
This tutorial is great! Thanks so much.
Thanks for this! It helped me make a decision on what kind of database to use on a side project.
Nicely explained, thanks for explanation
Excellent video ...very short to the point and no nonsense beating around the bush .... If SQL Databases are required to be vertically scaled then how does it meets the scaling needs as vertical scaling has limits in terms of CPU / MEM / Storage ? On event day how is it possible to achieve scaling out when horizontal scaling is not possible in SQL databases and also scaling in ?
Great video. thanks to everyone involved. always a blast to see someone who knows about the subject so much, she has to be mindful she doesn't introduce too many concepts. cheers. u introduced just the right amount imo.
though, i still am not clear on how nosql is not just a usecase of sql. all the advantages of nosql seems to be available due to its limitations.
i mean, i can just create a table on an sql db with two colomns, key and value. a primary key and a json field. then i can scale it horizontally as i don't have to worry about keeping related rows on the same node. there won't be any related nodes. it will be very flexible too as all the data is json.
i mean, all the advantages of nosql are still available in sql if u give up sql advantages.
obv, i'll still use nosql regardless. it's easier to just use redis than configuring postgres to hold a cache table on RAM. however, i wouldn't develop redis as a whole new system instead of a postgres plugin/extension if i were to be in that position
Amazing explanation. Very succinctly put.
Thanks Vineet!
Nice explanation. Thank you
Very clear mam thank you very much
Really good explanation. I have seen this after going through a lot of material on this topic.
So good to hear!! thank you.
Hi, I have two questions.
Q1. Can non -structured database be designed into 2 parts : static(structured) and other being(dynamic) thus can imbibe both ACID and BASE.
Q2.Also is no-SQL not better for API versioning improvements?
Informative and a fusion of art and logic. Great videos!
Great content! thank you so much it's so clear and mindblowing video editing 😮😍
Mam what'about MySQL and mongodb
Great job! Your explanation was very detailed and understandable! Thank You.
Thank you for this video. I really love the way how you explained it. The best one I found! :)
Thanks Polina!!
This was very clear!
9:03: NoSQL are bad for analytical processing. I dare to say they are also bad for being queried on anything other than their primary key. They are good for allowing loose structure and keeping their one to many dependencies together.
you can index the other fields which your going to query
Good Articulation. thank you.
Very well explained
what a beautiful explanation .
Great explanation!
excellent explanation. Nicely organized and very clear. Thank you!
Good job .Well explained.
what Google product is similar to ms access?
I do not agree with the scaling and big data argument in the sql vs nosql decision.
Working with both for years I can guarantee its not about data sizes nor structure, sine non structured data can't be fetch until structured.
It's about how and when the data is structured and scaling is about horizontal vs vertical scaling. Individual databases scales differently, so it's not about sql or not.
Oracle databases can scale both ways and handle as large data amounts as any.
It's about how you need your data fetched and how large a subset of the total data set you need to search through.
great video liked it
So clear, thank you so much.
It helped me a lot, thanks!
Sql vs no sql vs hybrid use cases?
I think it’s important to note Firestore offers acid transactions.
I am curious, whether the things mentioned here for NoSQL databases are true for Graph databases as well. For me it seems a database where the joins are more important and easier than in the SQL. So for me graph databases seems to be on the other side of SQL than the document based once. So is it faster too and can store that large data volume, can use horizontal scaling and can they be just eventually consistent?
Such a great explanation!
Can I use Cloud SQL with Firebase? Or if I use Firebase, am I bound to NoSQL?
Great question, you can use Cloud SQL with Firebase if you need a relational database.
Very informative video.
Thank you for such described videos. Can you please advice, what DB to choose, in case of social media app, like facebook?
Choose a NoSQL database because you might decide to add fields as the application grows. And you will be able to easily do that in NoSQL database. On Google Cloud I would recommend Firestore.
@@pvergadia I am always see, the answers, that SQL is better. :( I really want to use MongoDB
And also, SQL reading data faster than MongoDB, but MongoDB handle more users at once. I am confused 🤔
Thank you for the great video!
Can you make videos on data modelling, please?
I will add it to my list, thanks for the topic idea.
Thank you so much!!!
very nice explanation!
Thank you for the video Priyanka. I was hoping to see if you did any video on RDBMS vs MPP and MPP vs NoSQL DBs. Can you please share?
Thank you!
Excellent 👌
What is database? Still to here it now even..
I am very good understand and your video plz make more videos thanks
but, the DATA is usually NOT stored on the SAME SERVER....the Tables are stored Separately from the Actual Data Being Stored for Retrieval.....Example: A Letter Form needs Data put in. Hmmm....The Data has already been entered by the Data Input Person in a Document. It was entered by a Word Processor and Saved to a Letter Storage for the Word Processor. Now a person looking for the Data to Send a Letter to Customers but, there is No Data Available at the SQL Program Server -- So the Letters cannot be sent -- UNTIL -- the Location to Said Data has been Entered on a Table Sheet so that Every Person Needing to send that Letter -- or Letters -- has been told where the Data can be found and the Whereabouts of the Form. This description might be too simple....sorry! Is my view correct? Or no. Thank you.
You are great 😊
looks like a great video, might like to add a little rim light behind you on the shadowed side to make your hair pop :) thanks for the content
I am constantly improving my setup. Thanks for the advice on the light.
@@pvergadia I can tell! I really enjoyed your video it was super clear and well explained. Wish my uni teachers were half as good... Seems like you're running two front lights, I would turn the shadow side one up just a fraction too. Best of luck!
From your point of view, are you writing backwards? I enjoyed learning something new.
Is she writing backwards?
Great explanation thanks.