Relational vs. Non-Relational Databases

[@UmamaheswararaoPotula]

it feels very comfortable with pace of explanation that she provides, really easy to understand.

[@marcinbadtke]

Thank you. In relational model data is structured as tables. NOT stored in tables. Table is logical entity. Data is kept in heap.

[@sriranjitharaghuraman1646]

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. :(

[@philippeko-IBM]

Hi Aisha, I would have loved seeing the simple exemple Customer-Order explained with non-relational databases. Thanks for this consideration. -Philippe

[@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.

[@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]

She made a mistake, indeed. John Doe made the first order and Jane Smith make order the second and third one.

[@dougpoirier427]

@@jeandy4495 Still a very helpful video for the basics.

[@adityajain1989]

She explained well.... This happen when you are in flow of explaining something magical.... Good Job IBM

[@doraneko141]

she explained the concepts really well. Really easy to understand. Thanks a lot :D

[@jjj262]

+1

[@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 KZbin 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.

[@13YearOldTalksAboutTech]

It was the same for me! Gosh! I was trying to find videos for my half yearly examinations and found this channel. Being the huge tech fan I am, I of course clicked on the video and was thoroughly surprised by quality of the video. Thanks IBM

[@asemic]

5:28 i love how "value" is witted to combine the stick on the a and l characters :P

[@rojaachan]

This was such a great explanation. Thank you so much for the insight!

[@kaos092]

How do you scale horizontally without adding more resources? Would love to know.

[@LuisGustavo-dk4qy]

Are you writing backwards?

[@billybuck2713]

i never got how these videos are made? With a mirror or what ?! im going insane

[@pine_9356]

they actually posted an explanation on their community page. Apparently all they do is flip the video horizontally in post

[@simonsmashup]

Of course. Everyone does that.

[@alelokaoseumu]

all they need to do is flip the image and it becomes readable to us.

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

[@andrewswift2317]

Every time she would start writing MIRRORED I would get distracted. What a talent XD

[@oddeda]

My guess is she's writing regularly, but mirrors the video in post.

[@DrCroc100]

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.

[@johanliebert2525]

No , you thanks you for giving me this lesson thank you so much Aesha Sayed

[@olamy8403]

Great job! Broken down so simply. She will make a great professor

[@moestaxx286]

she did a great job explaining these concepts. thank you very much!

[@bigtaco4362]

Yes. Important topic and well wxplained

[@puravupadhyay2961]

Nice video. I found the non-relational database types interesting, is there a detailed video about different types?

[@darkpink_electronics4523]

thanks IBM, that was helpful. but, which one should i use?

[@bristinborah]

If you look for speed and optimised data , you can proceed with NR

[@DianaAdamczyk]

Thank you, this was very clearly explained!

[@Marvelous404]

Thanks a lot for this lesson Emily willis.

[@manjithkumar_16]

Good explanation and easy to understand.. Thanks ..

[@combeechan]

What are some examples of non-relational databases?

[@patrykwrobel5783]

Great videos also great communication skills from Aisha

[@saburekennedy2283]

explained in a rather easy way to understand

[@dushyantchaudhry4654]

7:01 how can you scale out without adding resources? horizontal scaling would mean adding more servers instead of adding compute to the same server (vertical scaling)

[@dushyantchaudhry4654]

Am I wrong if I disagree entirely with the statement data is stored in tables? I could be wrong but I don't think it is. The data is stored in binary bits either in-memory or in persistent storage like SSD or HDD. In addition to storing this binary data, the relationships between the various bits, bytes of data values are stored as well. Allowing a DBA to define these relationships is the facility provided by the DBMS. The DBMS does not store data. Stores is an entirely incorrect verb in the context. In the case of RDBMS, these relationships are mentioned by linking data to different columns and rows (Name is the column and John is the value). In the case of NoSQL DBMS these relationships are defined in other ways such as linking a data value to a dat key (Name is the key and John is the value). In RDBMS the relationships are rigidly defined. An employee can't have information in an additional column (example middle name) if that column is not there for other employees. In NoSQL there is flexibility in defining these relationships between stored data values.

[@Edxylom]

Thanks Aisha. You explain very clean

[@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.

[@gregwoodin5630]

Great video, thanks.

[@minhajkhan504]

superb explanation! thanks

[@iznabbas6020]

Great video thanks

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

[@MhmdMhmd-xz6sk]

Good video, in the nosql db you didn't give examples!

[@AmarachiEzinwa-qp1rw]

The video is very nice and I enjoyed but I don't quite get the scalability part

[@EliseeMbusa-z4i]

May you give several examples about relational database

[@danjalosa]

Very useful.

[@damaroro]

this simple question is often ask in job interview, so learn it carefulyy

[@Ashen-pw9zp]

Thank you so much. keep it up

[@ChanceMinus]

Fantastic job! Thank you... 👍

[@dadoll1660]

Thank You.

[@mostaphasaid7250]

thank you very much

[@abigiyatadesse2672]

Thank you so much.

[@simersive]

ngl the handwriting was absolutely outrageous but w video

[@medical-wl9qc]

Bubba, a single table is also called a relation. Not having to be linked but often so because of normalization.

[@BradleyThomas]

Is.... she writing backwards?

[@Moonev_Fantasy]

Thanks

[@plontulublalulu]

is she writing all of this backwards?? holy pro

[@fatcat22able]

I think it’s more likely they mirror the video

[@Tory_Rainman]

Thank you 😊

[@chandansingh-sv3zv]

Good experience

[@Cliporis]

You are confusing me with "customers" and "clients". Seems like you are talking about the same people right?

[@folklore_of_beth]

This has no description of what a nonrelational database is...

[@kahnfatman]

OBJECTION: Intro is totally misleading. What is a relation? It is an algebraic concept how two or more sets are related to each other. You don't need TWO tables to have this kind of relation. Each row in a data table is in and by itself a relation. For example: Column name forms a set of names, column date of birth is another set. Each item from column name is related to a date of birth item for every row.

[@lilwolf6900]

How is she writing backwards?

[@jimer634]

not so clear explanation as to what their differences is?

[@churrundog]

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]

See ibm.biz/write-backwards

[@SausageMachine]

Great explanation, but perhaps it's worth mentioning IBM's fantastic Functional Database TM1!

[@TooManyMonster]

Super nice explanation and cute presenter

[@adityajain1989]

Wish she smiles a bit too

[@samjones4327]

Thank You very much for a clear and concise explanation! Cheers!

[@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]

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]

I disagree - there is only one customer per order, therefore the customerId can be stored in the order table.

[@joshellis4966]

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]

Better to change your pen!

[@yashkumar6701]

what the hell ibm is now in education field lmao

[@blakwingz]

Thank you.