Clearly, you're a naturally gifted teacher. Great content.
@hnasr3 жыл бұрын
#savetheducks
@kharlcutie42426 ай бұрын
Love the way you teach. I almost didn't want the video to end.
@SrivatsanVenkatesan Жыл бұрын
I understand this is one of your older videos, but wanted to mention that your content is first class! Thank you!
@PrashantZombade Жыл бұрын
Most interesting way of teaching I have ever found, learning can't be more fun than this!
@adrianasensio42983 жыл бұрын
The content of this channel is superb.
@richboiii1711 ай бұрын
Incredible video. I was to solidify my understanding of the concept of columnar databases vs row based and this video not only made it easy to understand, but enjoyable too!
@videosforthegoodlife2253 Жыл бұрын
Great video man. I like a mix of column (for logging, source of truth) and table based RDBMS and also documented oriented (which could be either row or column) for quick trashy dirty data that makes you blush when you look at it too long. But I've seen columns used for quick trashy data - where sums or map reduce is the highest priority and it blows everything else away. I am digging ScyllaDB lately.
@HopeMlebe Жыл бұрын
Visually clear, funny and interesting explanations, you are greatly talented.
@foxtrotbr3 жыл бұрын
One of the best explanations I had seen. Thanks man
@haoyuanhuang50983 жыл бұрын
Gives concrete examples of when column database operations are faster or slower than a row database. Thank you!
@RooftopDuvet Жыл бұрын
Great work here! So many explanations of this are too high level, and miss the key differentiator: i.e. the way in which the data is accessed. You did a great job and did it at your own pace. Hope you find success with this style.
@vilewalker2343 жыл бұрын
Youre very entertaining to watch, listen, and learn from
@hnasr3 жыл бұрын
❤️❤️❤️
@vinny1423 жыл бұрын
13:35 Aggregates read more than you need. Only if you don't have indexes on the columns you query and if your core business is querying that data then you will have that indexed anyway. Also: if the amount of reads becomes a problem the first thing you do is de-normalize that value into a separate table. This is where database monitorring becomes essential, a nice topic for a ten-part series that will blow your viewers minds :-) I'd change the pro's and con's to "what kind of applications benefit from this." because every point you mention has some serious vaceats, related issues and known workarounds.
@hnasr3 жыл бұрын
Correct that is why didn’t include indexes in the mix. Thanks for the feedback as usual
@muhammadfarhanmughal61012 жыл бұрын
Your Accent and voiceovers make it more attractive to learn.
@OmarBela123 жыл бұрын
this dude is good, the channel is underrated
@ameyapatil11393 жыл бұрын
"Lets confused everybody by new names" : hahahaha well said ! great video thanks
@vmdcortesАй бұрын
I love your explanation, awesome!!! 🎉
@nishantgarg74973 жыл бұрын
Really awesome content. A really good source for me who is looking to improve the backend concepts. Really thank you for such good content. Just subscribed for updates
@hnasr3 жыл бұрын
Glad it was helpful! and welcome to the community
@swarajgupta30872 жыл бұрын
You opened my eyes :D
@azureabhik Жыл бұрын
Amazing visualisation of concept keeping the technicalities agnostic along with equally simplified narration. The quality of your material and narration is inversely proportional to the jokes :)
@williamfelippedeschamps70503 жыл бұрын
Great video, well explained, fun and infomative. I loved that, thanks dude!
@MohammedOmarBalousha2 ай бұрын
Great explanation
@andreabondanini250911 ай бұрын
Amazing content!
@adityasethi97943 жыл бұрын
This just shows how much he loves what he does.
@praveenX Жыл бұрын
Funny and effective, loved it 👍
@RandomShowerThoughts Жыл бұрын
another banger of a video
@virendrabhati66853 жыл бұрын
Great information in so simple way..... It's clear the concept in best of best way 👍. I loves your all videos....
@hnasr3 жыл бұрын
Thanks Virendra 🙏
@madanmohanpachouly61352 жыл бұрын
Nicely explained
@murugesanrm2 жыл бұрын
Thank you very much for making this video with a real-time example. Much appreciated
@muustafaaahmed9782 Жыл бұрын
I really loved your method in describing this topic .
@bigdata_journey9 ай бұрын
Thanks bro, very useful
@ap2077 ай бұрын
Absolutely amazing video. Thank you
@yxw91042 жыл бұрын
Thank you so much!
@antonsizou90753 жыл бұрын
Thanks. Good info. Never know how column dbs work
@harshitagrawal85562 жыл бұрын
Thank you so much for explaining this concept so beautifully and in such a great depth...I am a fan of your teaching.....
@michaelgeorge67652 жыл бұрын
Thank you Hussien. really simple, good and funny.
@lambdaboss5528 Жыл бұрын
Great video and explanation, thank you.
@prateekraj10843 жыл бұрын
awesome explanation for both row and column oriented db's
@srb18552 жыл бұрын
this was excellent it cleared up the fud👍 thanx!
@sujojohn29482 жыл бұрын
Thank you so much for this explanation!!
@OfferoC3 жыл бұрын
nice explanation thank you
@anikettiwari68852 жыл бұрын
@Hussein I love your database videos. Could you create a video on how to Alter large tables which has millions or maybe billions of records without a downtime in Postgres.
@ganeshbb12 жыл бұрын
Thank you..
@timbui55562 жыл бұрын
Could you please teach us how to do columnar partition in Postgres? It's easy to find lessons on horizontal partitioning, but I can't find writings on how to do vertical. Thank you!
@MercedeX7 Жыл бұрын
it's called horizontal partitioning. read about it on net
@vanigs87262 жыл бұрын
ur awesome man .great explanation
@oah84653 жыл бұрын
Dude that was sweet. Any chance of doing a video on file systems and mapping them to DB OPERATIONS
@rujhanarora78923 жыл бұрын
yup, I wonder if I increase the text value in a column or add a new column, how does it map to disk i/o
@dylanngo44548 ай бұрын
Thank bro 🎉
@tirthpatel83642 жыл бұрын
Great explanation.
@luckyboy19863 жыл бұрын
Thank you! That's very clear !
@pesetskyps2 жыл бұрын
very clear. bravo!
@aminebenkhouya72953 жыл бұрын
u r the best
@abderrahmanemabroukmerabet92743 жыл бұрын
Really good video bro, I like what you do
@gabriellegall82783 жыл бұрын
Thank you so much ! it was so clear
@prem9124900223 жыл бұрын
Waiting for your udemy course. Great stuff as usual.
@mohammedkandelhassan3 жыл бұрын
Great Video!
@chunheguo92303 жыл бұрын
Great vid. I am working with both data structure types :) Using the postgres as a row base to prepare it for a transformation into columnar for gpus to process :)
@hnasr3 жыл бұрын
Nice! Your going HTAP
@chunheguo92303 жыл бұрын
@@hnasr No, not going hybrid transactional, as the columnar data is being used as runtime in memory data until a bulk update changes it.
@minscj3 жыл бұрын
@@chunheguo9230 hi please could you give me more details how i can do the same? please reply
@chunheguo92303 жыл бұрын
@@minscj Hi, the solution we went is proprietery, so I can't really go into details. I can however suggest that you take a look at the concept of apache arrow. www.dremio.com/announcements/introducing-apache-arrow/ has a nice diagram. We went very low level and didn't use many of the existing open-source abstraction layers. It all came down to understanding how the GPU's processing cycle works and the alignment of the columnar data to said cycle.
@instantshinramen2 жыл бұрын
"The devil!" "Save the ducks guys save the ducks" Now I understand databases.
@darrenz55573 жыл бұрын
hi! can you do a vid with indexes? the visuals are so helpful!
@muhammaddavatgar49732 жыл бұрын
love you sir
@mrluismartinezzz3 жыл бұрын
Hussein, thanks for the videos. Today imma try & figure out how to download a KZfaq video with vanilla NodeJs if I don’t figure imma ask you guys for help
@saadowain35113 жыл бұрын
Hussain Can you please make a short video of different kinds if DBs who are the providers.. what are the ideal uses.
@umapathybabu83973 жыл бұрын
nice demonstration
@Firatayrilik2 жыл бұрын
Perfect!
@ianokay8 ай бұрын
We generally want all the columns, that's what a record or document is
@peterisawesomeplease3 жыл бұрын
Good video but a couple small things. I think the video was slower than it needed to be. Like too many tangent and repetition. We can pause and go back and forth so no need to artificially slow it down. Also i think for this topic leaving out indexes does not make sense. Almost no one is going to choose to use a column oriented db before trying indexes.
@Nicoblabla3 жыл бұрын
great video!
@darthmelbius2 жыл бұрын
8:56 I'm assuming that in your example the query will continue beyond the record (and block) it found as there is no index or keys? So it will scan all "blocks" even if it finds only one match?
@sexypradeepkumar2 жыл бұрын
Which databases stores both rowbased and column based structures?
@vinitsunita2 жыл бұрын
Lesson learnt from the video, Save the ducks :p
@maheshnarayan64409 ай бұрын
Great video. QQ: For columnar DB, if DB stores all the metadata about which block has 1006, won't it also store metadata about social security number 666? So we would need only 2 jumps instead of 3 jumps right?
@reactorscience9 ай бұрын
1006 is the row id(internal to the database). The db only knows in which blocks do these intern ids exist. It doesn't store any such metadata for the other columns
@rajbansal3663 Жыл бұрын
Cassandra (NoSQL) uses LSM Tree which makes it a better choice for heavy writes in comparison to SQL databases, any thoughts on this?
@jasont64212 жыл бұрын
Lmao, what's the reference to every time you write to a disk that a duck dies? 😹
@therealdrag02 жыл бұрын
This column store sounds similar to inverted indexes that search engines (eg elastic search) use. Are there key differences there?
@md.imrulhasan87573 жыл бұрын
Sir.... Here you said when searching for first_name it automatically load the final block.... it escape first block of first_name..... How can it find it? Is it because the the row_number is indexed in the db table? if not then why not find the final block using ssn?
@yanfung7299 Жыл бұрын
If let's say in a row oriented db, from your explanation the commas does not exist but just for displaying, how will the engine knows where to start to look for first name etc?
Жыл бұрын
For instance, PostgreSQL stores these sequences of values in tuple storage, one for each column in the table. The values are serialised and packed together to form the tuple. When querying data from a table, PostgreSQL uses the stored column names in the system catalogs to interpret the tuples' content correctly. The column names are used by the query planner and executor to map the data values from the tuple storage to their respective columns based on their positions in the tuple.
@eric77583 жыл бұрын
Great Video Hussein.. when are you doing webrtc?
@hnasr3 жыл бұрын
I am working on the slides, once thats done Ill work on the demos so maybe a week or two
@eric77583 жыл бұрын
@@hnasr Thanks
@KaranRaina952 жыл бұрын
Hey Hussein, wouldn't it be fair to say that to get the advantages of column db in row db, we end up making indexes in row db?
@gyhuj12352 жыл бұрын
Why can't we just do SELECT Salary from emp? will that be efficient or will it result in the entire row read and then it will be filtered? The table can be indexed for ssn or name.
@natem8893 жыл бұрын
How do you work on 1 or less column table?? 🤔
@shubhamjaiswal7608 Жыл бұрын
Nasser, great video. But one observation, clearly you were High while making this video.🤣
@Juasbhu2 жыл бұрын
Hahahahha you're so funny. Good video. Thanks
@07rohitpd2 жыл бұрын
"...they have all this meta-data, mumbo-jumbo" -Hussein
@ramadhan62733 жыл бұрын
Hussein I wanna know how you had that level of curiosity machallah? is it something gained by training?
@hnasr3 жыл бұрын
It is pure curiosity and asking why and having the humility to learn takes time.
@Juasbhu2 жыл бұрын
Question, column oriented is the same with family column Db?
@hnasr2 жыл бұрын
Yes same name. Columnar and column store are other names.
@pdeezz2 жыл бұрын
You’re hilarious 😂 and offer a great explanation. Thanks! #savetheducks
@sudharshantr87572 жыл бұрын
at 21:58 1006 was found directly using some "tricks".. Then why can't we use the same tricks to find 666:1006 in the first try?
@benevans13773 жыл бұрын
Hey bit of an off topic question why did you change your name from igeometry?
@hnasr3 жыл бұрын
Moving from GIS to personal brand so I get to cover multiple topics mainly.
@stormcorexz3 жыл бұрын
I think I can not imagin how locking are working on column oriented database, it is a nightmare unless it has it's own deifferent techniques
@07rohitpd2 жыл бұрын
"SAVE THE DUCK", guys, "SAVE THE DUCK".
@carlitoz4503 жыл бұрын
interetsting video, shouldn't data in column oriented db be stored sorted ?
@hnasr3 жыл бұрын
Not necessary, the table data aren't stored sorted usually otherwise writing becomes difficult. Indexes on the other hand are sorted
@icbm73 жыл бұрын
🦆🦆🦆🦆 Great video!
@vivekshah16644 ай бұрын
save the ducks guys!
@hectorge7533 жыл бұрын
Six Six Six, the devil... SUBSCRIBED
@therealdrag02 жыл бұрын
Clarification: “column stores” and “wide column stores” are quite different! I watched this expecting to learn about BigTable/Cassandra. But they have key differences so this video doesn’t apply to them. TIL
@hnasr2 жыл бұрын
Correct wide column is different. Group of columns into a column family. Best of both words
@sbylk993 жыл бұрын
omg, why only you can explain complicated problems in easy words! Tutorials always say "NoSql is good for fast write, scalable, not suitable for complicated query", but no one explain clearly as you! Column based NoSql is just for simple data write and AGGREGATE query. One example is number of likes of a video. Just define a simple table, (video_id, user_like_id), then sum(user_like_id), this scenario is the best for NoSQl. Or sensor data, not complicated(can tolerate write slow), but lots of aggregate query, like min(), max(), average().
@julianzhai63212 жыл бұрын
Awe man but ducks are delicious
@kumailn76623 жыл бұрын
hussein kindly be straight forward on the videos, you to much talkative i like that but i more information centric information seeker. if you provide to the point would be appreciated alot, second don't mixed or drag the words while talking.
@GerardBeaubrun2 жыл бұрын
666 thank you for the laughter my friend
@vraymond20483 жыл бұрын
"Lets confused everybody by new names", make them look like a fool who can not understand things, thus makes us more "professional" and "experts"!