Тёмный

Relational vs. Non-Relational Databases 

IBM Technology
Подписаться 780 тыс.
Просмотров 98 тыс.
50% 1

Learn more about WatsonX: ibm.biz/BdPuQR
Relational DBs Explained → ibm.biz/relational-DBs-explained
Learn about Db2 on Cloud → ibm.biz/learn-Db2-on-cloud
Check out Informix → ibm.biz/ck-out-informix
In this video, Aisha Syed compares relational and non-relational databases and explains the strengths and weaknesses of each.
Get started for free on IBM Cloud → ibm.biz/BdPFpz
Subscribe to see more videos like this in the future → ibm.biz/subscribe-now
#database #Db2 #DBaaS #informix

Опубликовано:

 

28 июн 2022

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 75   
@user-fp4xm5ww5f
@user-fp4xm5ww5f 4 месяца назад
it feels very comfortable with pace of explanation that she provides, really easy to understand.
@doraneko141
@doraneko141 Год назад
she explained the concepts really well. Really easy to understand. Thanks a lot :D
@LoneLeagle
@LoneLeagle Год назад
I put GRAPH databases in the relational category because relationships are first class citizens in graph & the biggest strength of GRAPH is the ability to create complex relational that go levels deep with ease. I'd say the hardest part about learning software development is choosing which tech stack to learn & use.
@rojaachan
@rojaachan Год назад
This was such a great explanation. Thank you so much for the insight!
@philippeko-IBM
@philippeko-IBM 11 месяцев назад
Hi Aisha, I would have loved seeing the simple exemple Customer-Order explained with non-relational databases. Thanks for this consideration. -Philippe
@Edxylom
@Edxylom Год назад
Thanks Aisha. You explain very clean
@patrykwrobel5783
@patrykwrobel5783 9 месяцев назад
Great videos also great communication skills from Aisha
@samjones4327
@samjones4327 Год назад
Thank You very much for a clear and concise explanation! Cheers!
@minhajkhan504
@minhajkhan504 Год назад
superb explanation! thanks
@marcinbadtke
@marcinbadtke 6 месяцев назад
Thank you. In relational model data is structured as tables. NOT stored in tables. Table is logical entity. Data is kept in heap.
@manjithkumar_16
@manjithkumar_16 Год назад
Good explanation and easy to understand.. Thanks ..
@ChanceMinus
@ChanceMinus Год назад
Fantastic job! Thank you... 👍
@DianaAdamczyk
@DianaAdamczyk 4 месяца назад
Thank you, this was very clearly explained!
@iznabbas6020
@iznabbas6020 Год назад
Great video thanks
@olamy8403
@olamy8403 Год назад
Great job! Broken down so simply. She will make a great professor
@asemic
@asemic Год назад
5:28 i love how "value" is witted to combine the stick on the a and l characters :P
@moestaxx286
@moestaxx286 Год назад
she did a great job explaining these concepts. thank you very much!
@bigtaco4362
@bigtaco4362 Год назад
Yes. Important topic and well wxplained
@johanliebert2525
@johanliebert2525 9 месяцев назад
No , you thanks you for giving me this lesson thank you so much Aesha Sayed
@VeraxMusic
@VeraxMusic Год назад
I continue to be amazed at the educational material on this channel. I don't know why, but it just seems unexpected and almost arbitrary. It's like if I happened to randomly come to find that, say, Uber had some RU-vid channel that provided world class content about the infrastructure of roads, or something. I guess I shouldn't be that surprised, as that's what they specialize in, but was not expecting it to be at this level, and taught so well. Anyway, this channel is great.
@combeechan
@combeechan 4 месяца назад
What are some examples of non-relational databases?
@gregwoodin5630
@gregwoodin5630 13 дней назад
Great video, thanks.
@dadoll1660
@dadoll1660 2 года назад
Thank You.
@Marvelous404
@Marvelous404 9 месяцев назад
Thanks a lot for this lesson Emily willis.
@Tory_Rainman
@Tory_Rainman 2 года назад
Thank you 😊
@danjalosa
@danjalosa 4 месяца назад
Very useful.
@saburekennedy2283
@saburekennedy2283 11 дней назад
explained in a rather easy way to understand
@sriranjitharaghuraman1646
@sriranjitharaghuraman1646 5 месяцев назад
It was really hard to see from your example why relational DBs are consistent or secure and why no-sql DBs were cost effective or scalable. Everything was a bit vague and unclear. :(
@abigiyatadesse2672
@abigiyatadesse2672 Год назад
Thank you so much.
@Ashen-pw9zp
@Ashen-pw9zp Год назад
Thank you so much. keep it up
@puravupadhyay2961
@puravupadhyay2961 2 месяца назад
Nice video. I found the non-relational database types interesting, is there a detailed video about different types?
@LuisGustavo-dk4qy
@LuisGustavo-dk4qy Год назад
Are you writing backwards?
@billybuck2713
@billybuck2713 Год назад
i never got how these videos are made? With a mirror or what ?! im going insane
@pine_9356
@pine_9356 Год назад
they actually posted an explanation on their community page. Apparently all they do is flip the video horizontally in post
@nsshing
@nsshing Год назад
Of course. Everyone does that.
@alelokaoseumu
@alelokaoseumu Год назад
all they need to do is flip the image and it becomes readable to us.
@rjathar
@rjathar Год назад
She's no more writing backwards than she is left handed... All you have to do is laterally invert the video to get this The reason we have trouble with it is because it fuses 2 common experiences for us... If the image is mirrored (laterally inverted, as above), we expect the subject to be between the viewer and the writing surface. However, if the writing surface is transparent and seems to be between the viewer and the subject then we expect it to not be laterally inverted. Combining these 2 experiences is what results in the mind meld you're seeing here
@kaos092
@kaos092 10 месяцев назад
How do you scale horizontally without adding more resources? Would love to know.
@mostaphasaid7250
@mostaphasaid7250 8 месяцев назад
thank you very much
@chandansingh-sv3zv
@chandansingh-sv3zv Год назад
Good experience
@DrCroc100
@DrCroc100 7 месяцев назад
Relation in relational database doesn't stand for relation between tables. Relation means "table" in this context. It's database with tables. Scaling horizontally means we can scale out WITH more resources, not without.
@dilpreets7
@dilpreets7 Год назад
in your example, you said John Doe (customer ID 1) made the first 2 order however in the second table the second order (order ID 2) was made by Customer ID 2 which is Jame smith. please clarify.
@jeandy4495
@jeandy4495 Год назад
She made a mistake, indeed. John Doe made the first order and Jane Smith make order the second and third one.
@dougpoirier427
@dougpoirier427 Год назад
@@jeandy4495 Still a very helpful video for the basics.
@adityajain1989
@adityajain1989 Год назад
She explained well.... This happen when you are in flow of explaining something magical.... Good Job IBM
@Moonev_Fantasy
@Moonev_Fantasy 2 месяца назад
Thanks
@andrewswift2317
@andrewswift2317 Год назад
Every time she would start writing MIRRORED I would get distracted. What a talent XD
@oddeda
@oddeda 11 месяцев назад
My guess is she's writing regularly, but mirrors the video in post.
@darkpink_electronics4523
@darkpink_electronics4523 Год назад
thanks IBM, that was helpful. but, which one should i use?
@bristinborah
@bristinborah 2 месяца назад
If you look for speed and optimised data , you can proceed with NR
@simonb700
@simonb700 Год назад
Sorry but I think you are wrong that columnar storage is non-relational. Relational just means that data is held in different, but joined, tables (e.g. third normal form), and the database can be either optimised for on line transactional processing (OLTP) or on line analytical processing (OLAP). Non-columnar technology is generally best suited to OLTP and columnar to OLAP. However, both can have data structured to be relational.
@timucinbahsi445
@timucinbahsi445 Год назад
to this day, i'm yet to see how the advantages of nosql are not applicable to relational dbs. since we have json fields in sql now, i could just delegate all the flexibility to a json column. idk how sql dbs are considered not scalable. sure it takes more configuration but it sure is done. cost effectiveness is kind of vague. it could mean easier to maintain thus less dba or dev time. i'm probably missing something but until i find out what it is, nosql is just what you need if your indexing game is weak. there i said it
@AmarachiEzinwa-qp1rw
@AmarachiEzinwa-qp1rw Месяц назад
The video is very nice and I enjoyed but I don't quite get the scalability part
@damaroro
@damaroro Год назад
this simple question is often ask in job interview, so learn it carefulyy
@simersive
@simersive Год назад
ngl the handwriting was absolutely outrageous but w video
@plontulublalulu
@plontulublalulu Год назад
is she writing all of this backwards?? holy pro
@fatcat22able
@fatcat22able Год назад
I think it’s more likely they mirror the video
@SausageMachine
@SausageMachine 2 года назад
Great explanation, but perhaps it's worth mentioning IBM's fantastic Functional Database TM1!
@BradleyThomas
@BradleyThomas 11 месяцев назад
Is.... she writing backwards?
@Cliporis
@Cliporis Год назад
You are confusing me with "customers" and "clients". Seems like you are talking about the same people right?
@lilwolf6900
@lilwolf6900 3 месяца назад
How is she writing backwards?
@TooManyMonster
@TooManyMonster Год назад
Super nice explanation and cute presenter
@adityajain1989
@adityajain1989 Год назад
Wish she smiles a bit too
@churrundog
@churrundog 9 месяцев назад
I need to know if you're actually writing mirrored information on a glass, or how is our POV achieved on this video. I don't even care about databases anymore
@IBMTechnology
@IBMTechnology 9 месяцев назад
See ibm.biz/write-backwards
@jimer634
@jimer634 11 дней назад
not so clear explanation as to what their differences is?
@linmo8375
@linmo8375 Год назад
Really good explanation and it's weird that they choose such a way to show it. Normally the teacher would stand in front of the board, whereas in this case, it appears that the teacher stands behind the board??? My mind finds it hard to understand?
@astb01
@astb01 Год назад
Don’t think the first relational example was correct. You have a customer table, an order table, you then should end up with an order-customers relational table which should only have an order ID and customer ID reference (nothing else)😊
@Lightbeerer
@Lightbeerer Год назад
I disagree - there is only one customer per order, therefore the customerId can be stored in the order table.
@joshellis4966
@joshellis4966 8 месяцев назад
This is wrong. There would be a one-to-many relationship between customers and order. (one customer can place many orders). In this case, the "many-side" relation would have a foreign key to the "one-side" relation. The only time a new relation needs to exist is if the relationship is many-to-many. Then you'd have a table with the key mapping of both relations.
@pedrampanahi9031
@pedrampanahi9031 2 месяца назад
Better to change your pen!
@yashkumar6701
@yashkumar6701 7 месяцев назад
what the hell ibm is now in education field lmao
Далее
What is DBaaS? Should you use it?
7:40
Просмотров 26 тыс.
Volkswagen судится с Volkswagen?
01:00
Просмотров 1,9 млн
Containers vs VMs: What's the difference?
8:08
Просмотров 742 тыс.
How do NoSQL databases work? Simply Explained!
7:38
Data Pipelines Explained
8:29
Просмотров 139 тыс.
Primary & Foreign Keys
8:25
Просмотров 470 тыс.
MySQL vs MongoDB
5:30
Просмотров 150 тыс.
7 Database Paradigms
9:53
Просмотров 1,5 млн
API vs. SDK: What's the difference?
9:21
Просмотров 1,4 млн
SQL vs NoSQL Explained
11:37
Просмотров 326 тыс.
Volkswagen судится с Volkswagen?
01:00
Просмотров 1,9 млн