The battle of relational and non-relational databases | SQL vs NoSQL Explained

แชร์
ฝัง
  • เผยแพร่เมื่อ 2 ก.ค. 2024
  • Which database is right for your application? SQL or NoSQL? Are you confused between relational and non relational databases? Want to know how they SQL and NoSQL databases are different?
    In this video I explain the difference and help you decide which database to use in which type of application.
    I am Priyanka Vergadia, Developer Advocate for Google Cloud, for more content
    📌 Follow me on Twitter - / pvergadia
    📌 Follow me on Instagram - / pvergadia
    📌 Follow me on LinkedIn - / pvergadia
    📌 GCPSketchnote Playlist - bit.ly/3jA8Ylz
    📌 Visit my website to download the sketchnote image - thecloudgirl.dev/
    #databases #nosql #sql #relationaldatabases #nonrelationaldatabases #db #dbms #rdbms
  • วิทยาศาสตร์และเทคโนโลยี

ความคิดเห็น • 115

  • @marcydoes
    @marcydoes 2 ปีที่แล้ว +41

    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.

    • @pvergadia
      @pvergadia  2 ปีที่แล้ว +1

      Thanks @Marcella!

  • @lalala-mh6kh
    @lalala-mh6kh 2 ปีที่แล้ว +12

    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!

  • @a_simpmel_life
    @a_simpmel_life 2 ปีที่แล้ว +2

    Very clear. Nice clean diagramming as well as explanations of the differences at a high level. I love it!

  • @joyyou100
    @joyyou100 2 ปีที่แล้ว +1

    The best video on this topic I found on YT. Thank You!

  • @narenandu
    @narenandu 3 ปีที่แล้ว +2

    Clearly articulated .. Thanks for the video

  • @muzaffarali5870
    @muzaffarali5870 2 ปีที่แล้ว +2

    Beautifully explained with simple and concise examples, well done!!

  • @anuragsharma7331
    @anuragsharma7331 2 ปีที่แล้ว +2

    simply awesome, loved the way you explained and quoted the examples.

  • @adamjenkins3065
    @adamjenkins3065 10 หลายเดือนก่อน

    Beautifully outlined. Thanks!

  • @DennisIvy
    @DennisIvy 2 ปีที่แล้ว +1

    Wow this channel is a Gem! Needed a refresher on this topic and found gold. Subbed!

  • @khayla_matthews
    @khayla_matthews 2 ปีที่แล้ว +1

    Best explanation I have come across on these concepts. Thanks so much!

  • @nkengchrist
    @nkengchrist ปีที่แล้ว

    Concise, chewable bytes, easy-to-digest explanation. Thanks for sharing!!!

  • @Vollidiot39
    @Vollidiot39 2 ปีที่แล้ว +1

    This tutorial is great! Thanks so much.

  • @sylviamohos8541
    @sylviamohos8541 ปีที่แล้ว +3

    This is so well explained. You are so clear and informative. Thank you for your excellent delivery!

  • @BlaBlaBlaInDaHouse
    @BlaBlaBlaInDaHouse ปีที่แล้ว

    Fantastic video! Probably the best explanation on the topic

  • @TheKyleHuss
    @TheKyleHuss ปีที่แล้ว

    Best ever explanation on the databases I came up so far. Thank you!

  • @Velo1010
    @Velo1010 ปีที่แล้ว +1

    You produce some of the most outstanding videos. I especially like you tone, pace, and comprehension.

  • @danielhughes5250
    @danielhughes5250 ปีที่แล้ว +1

    Best explanation I've seen yet. Thank you and well Done.

  • @luxxart
    @luxxart ปีที่แล้ว +1

    Really good overview, thank you!

  • @bornkool
    @bornkool 2 ปีที่แล้ว +1

    A great presentation of SQL and non-SQL databases nicely organized presented and explained bravo! Thank you for a lesson well delivered.

  • @hobbesnblue
    @hobbesnblue ปีที่แล้ว

    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!

  • @sagarbarge6706
    @sagarbarge6706 5 หลายเดือนก่อน +1

    Clearly explained. Thank you

  • @patbhavik1
    @patbhavik1 ปีที่แล้ว +1

    Well explained and completely awesome!!

  • @Diaba_dos_compiuter
    @Diaba_dos_compiuter 2 ปีที่แล้ว +1

    You are an amazing teacher, Thank you very much

  • @darnellgranberry9204
    @darnellgranberry9204 2 ปีที่แล้ว +1

    Fantastic video! Thank you so much for making this 😄

  • @mattgoodman1699
    @mattgoodman1699 9 หลายเดือนก่อน +1

    This was incredible! I hope you come back to make more videos you’re a remarkable teacher

  • @fatriantobong2097
    @fatriantobong2097 ปีที่แล้ว

    simple explanation shows how good you are, some explain with new confusion to arise, so good job

  • @EugenePetrash
    @EugenePetrash 2 ปีที่แล้ว +1

    Best explanation. Thanks!

  • @bjm1100
    @bjm1100 ปีที่แล้ว

    Informative and a fusion of art and logic. Great videos!

  • @fuckingeasyprogramming9843
    @fuckingeasyprogramming9843 ปีที่แล้ว +2

    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

  • @elizabethmilonas2249
    @elizabethmilonas2249 2 ปีที่แล้ว

    excellent explanation. Nicely organized and very clear. Thank you!

  • @LuizFelipeBom
    @LuizFelipeBom ปีที่แล้ว

    So clear, thank you so much.

  • @savinda3036
    @savinda3036 ปีที่แล้ว +1

    Great explanation. I understood everything perfectly.

  • @ganeshpalve266
    @ganeshpalve266 2 ปีที่แล้ว

    That's the best explanation of sql nosql relevant to gcp

  • @4Meghasharma
    @4Meghasharma 2 ปีที่แล้ว +1

    Big Fan ... Loved the way you explained it!!

  • @tpenn2
    @tpenn2 ปีที่แล้ว +1

    Wonderfully done.

  • @gibbslm
    @gibbslm ปีที่แล้ว

    Great content! thank you so much it's so clear and mindblowing video editing 😮😍

  • @ankit1703
    @ankit1703 2 ปีที่แล้ว +2

    Great content, thanks to TH-cam algorithm for suggesting this video and thanks to you as well.

    • @pvergadia
      @pvergadia  2 ปีที่แล้ว

      Amazing to hear, thank you!!

  • @VictorSantos-yb8ir
    @VictorSantos-yb8ir 2 ปีที่แล้ว +1

    It helped me a lot, thanks!

  • @jimmycheong7970
    @jimmycheong7970 2 ปีที่แล้ว +1

    This was very clear!

  • @sumitkothalikar
    @sumitkothalikar 3 ปีที่แล้ว +1

    Nicely explained, thanks for explanation

  • @upendertadewar8454
    @upendertadewar8454 2 ปีที่แล้ว +1

    Nice explanation. Thank you

  • @shaunrashidYT
    @shaunrashidYT 9 หลายเดือนก่อน

    Thanks for this! It helped me make a decision on what kind of database to use on a side project.

  • @mohammadkhalid7885
    @mohammadkhalid7885 ปีที่แล้ว

    what a beautiful explanation .

  • @timucinbahsi445
    @timucinbahsi445 ปีที่แล้ว

    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

  • @rebeccadejesus5256
    @rebeccadejesus5256 ปีที่แล้ว

    Great job! Your explanation was very detailed and understandable! Thank You.

  • @bhargavigoud4524
    @bhargavigoud4524 2 ปีที่แล้ว +1

    Very clear mam thank you very much

  • @lsdimontenegro5705
    @lsdimontenegro5705 2 ปีที่แล้ว +6

    Absolutely wonderful, from delivery to knowledge shared to beautiful layout. I learn so much from you Ms. P!

    • @pvergadia
      @pvergadia  2 ปีที่แล้ว +1

      Thanks for sharing you feedback, glad you found it helpful.

  • @pabloqp7929
    @pabloqp7929 8 หลายเดือนก่อน

    Thank you for the great video!

  • @dianna5619
    @dianna5619 10 หลายเดือนก่อน

    I have to take this as a class and I have been intimidated by this subject. I was recommended your video by TH-cam and I’m happy to have found you.

  • @dharmendracherukuri7530
    @dharmendracherukuri7530 ปีที่แล้ว +1

    Good Articulation. thank you.

  • @TanmaySarkar
    @TanmaySarkar ปีที่แล้ว +1

    Thanks for the brief lesson, I am learning PostgreSQL recently and wandering the big picture of databases.

  • @powerbis.1794
    @powerbis.1794 2 ปีที่แล้ว

    Such a great explanation!

  • @sarthaknikhal5540
    @sarthaknikhal5540 3 ปีที่แล้ว +3

    That was a great explanation.
    And a simple person with a non CS background can understand DBs well by watching this video

    • @pvergadia
      @pvergadia  3 ปีที่แล้ว

      So great to hear that you found it helpful.

  • @anastasiakutsevolova1320
    @anastasiakutsevolova1320 2 ปีที่แล้ว +1

    Great explanation!

  • @polinastamenova6655
    @polinastamenova6655 2 ปีที่แล้ว +2

    Thank you for this video. I really love the way how you explained it. The best one I found! :)

    • @pvergadia
      @pvergadia  2 ปีที่แล้ว

      Thanks Polina!!

  • @EnglishwithTerry
    @EnglishwithTerry 2 ปีที่แล้ว +1

    Excellent video, excellent explanation

  • @cynthiaclark6157
    @cynthiaclark6157 ปีที่แล้ว +1

    This was explained so well. Thank you!

  • @lex8799
    @lex8799 ปีที่แล้ว +1

    Thank you so much!!!

  • @JoyFay
    @JoyFay 2 ปีที่แล้ว +1

    Very well explained

  • @AniketBankapur
    @AniketBankapur ปีที่แล้ว +1

    great video liked it

  • @thebluefox100
    @thebluefox100 ปีที่แล้ว

    very nice explanation!

  • @lex_dojo
    @lex_dojo ปีที่แล้ว

    Very informative video.

  • @glenbrown4132
    @glenbrown4132 2 ปีที่แล้ว

    Great explanation thanks.

  • @vineetdave7323
    @vineetdave7323 3 ปีที่แล้ว +2

    Amazing explanation. Very succinctly put.

    • @pvergadia
      @pvergadia  3 ปีที่แล้ว

      Thanks Vineet!

  • @greendsnow
    @greendsnow ปีที่แล้ว

    Finally! She's got her own channel!

  • @rajalanka1563
    @rajalanka1563 ปีที่แล้ว +1

    Some SQL based MPP databases do offer Horizontal and elastic scaling as well. They are not limited to vertical scaling only.

  • @mdnooruzzaman6832
    @mdnooruzzaman6832 3 ปีที่แล้ว +2

    Excellent 👌

  • @njuniorba
    @njuniorba ปีที่แล้ว +2

    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% 👍

  • @recursion.
    @recursion. 7 หลายเดือนก่อน

    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 TH-cam. :)

  • @stuti.sharma.ranchi
    @stuti.sharma.ranchi ปีที่แล้ว +1

    Really good explanation. I have seen this after going through a lot of material on this topic.

    • @pvergadia
      @pvergadia  ปีที่แล้ว +1

      So good to hear!! thank you.

  • @ppnehe
    @ppnehe 2 ปีที่แล้ว

    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 ?

  • @cedricsarigumba4370
    @cedricsarigumba4370 หลายเดือนก่อน

    This is the best channel! You have a talent to simplify complicated topics. ✨✨

    • @pvergadia
      @pvergadia  22 วันที่ผ่านมา

      Thank you!

  • @strengthproject
    @strengthproject ปีที่แล้ว +1

    I hope you do more videos soon ❤

    • @pvergadia
      @pvergadia  ปีที่แล้ว

      I will surely create more soon! Thanks for the encouragement.

  • @swamynyc
    @swamynyc 3 ปีที่แล้ว +1

    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

  • @EmperorFool
    @EmperorFool ปีที่แล้ว +1

    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!

  • @Goody495
    @Goody495 2 ปีที่แล้ว

    You are great 😊

  • @coding3438
    @coding3438 ปีที่แล้ว

    Yooo this is the pub sun playlist girl from google channel! Good to know she has her own channel!

  • @lifeissnowpiece4505
    @lifeissnowpiece4505 2 ปีที่แล้ว

    I am very good understand and your video plz make more videos thanks

  • @prashanthtalla
    @prashanthtalla 2 ปีที่แล้ว

    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!

  • @puchesjr07
    @puchesjr07 3 ปีที่แล้ว +2

    I think it’s important to note Firestore offers acid transactions.

  • @ArpadHorvathSzfvar
    @ArpadHorvathSzfvar 2 ปีที่แล้ว

    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?

  • @powerbis.1794
    @powerbis.1794 2 ปีที่แล้ว +1

    Can you make videos on data modelling, please?

    • @pvergadia
      @pvergadia  2 ปีที่แล้ว

      I will add it to my list, thanks for the topic idea.

  • @thiru2605
    @thiru2605 ปีที่แล้ว +1

    Mam what'about MySQL and mongodb

  • @peterpiper5300
    @peterpiper5300 2 ปีที่แล้ว

    what Google product is similar to ms access?

  • @lefteriseleftheriades7381
    @lefteriseleftheriades7381 ปีที่แล้ว

    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.

    • @navaneethpk3535
      @navaneethpk3535 ปีที่แล้ว

      you can index the other fields which your going to query

  • @krishnareddyyerram4615
    @krishnareddyyerram4615 ปีที่แล้ว

    Sql vs no sql vs hybrid use cases?

  • @AmarMishra
    @AmarMishra ปีที่แล้ว

    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?

  • @user-ms2jf1eg3j
    @user-ms2jf1eg3j ปีที่แล้ว

    Thank you for such described videos. Can you please advice, what DB to choose, in case of social media app, like facebook?

    • @pvergadia
      @pvergadia  ปีที่แล้ว

      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.

    • @user-ms2jf1eg3j
      @user-ms2jf1eg3j ปีที่แล้ว

      @@pvergadia I am always see, the answers, that SQL is better. :( I really want to use MongoDB

    • @user-ms2jf1eg3j
      @user-ms2jf1eg3j ปีที่แล้ว

      And also, SQL reading data faster than MongoDB, but MongoDB handle more users at once. I am confused 🤔

  • @MO-hq4iz
    @MO-hq4iz ปีที่แล้ว

    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.

  • @JohlBrown
    @JohlBrown 2 ปีที่แล้ว +1

    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

    • @pvergadia
      @pvergadia  2 ปีที่แล้ว +1

      I am constantly improving my setup. Thanks for the advice on the light.

    • @JohlBrown
      @JohlBrown 2 ปีที่แล้ว +1

      @@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!

  • @Maestrotoy
    @Maestrotoy ปีที่แล้ว

    What is database? Still to here it now even..

  • @jinskim7615
    @jinskim7615 2 ปีที่แล้ว +1

    Can I use Cloud SQL with Firebase? Or if I use Firebase, am I bound to NoSQL?

    • @pvergadia
      @pvergadia  2 ปีที่แล้ว

      Great question, you can use Cloud SQL with Firebase if you need a relational database.

  • @TheBavaNeche
    @TheBavaNeche 2 ปีที่แล้ว

    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.

  • @jramirezdearellano
    @jramirezdearellano 9 หลายเดือนก่อน

    From your point of view, are you writing backwards? I enjoyed learning something new.

  • @superxereu
    @superxereu 2 ปีที่แล้ว

    Is she writing backwards?

  • @suck-myballs1152
    @suck-myballs1152 ปีที่แล้ว

    great video!