Clearly, you're a naturally gifted teacher. Great content.

#savetheducks

Love the way you teach. I almost didn't want the video to end.

I understand this is one of your older videos, but wanted to mention that your content is first class! Thank you!

Most interesting way of teaching I have ever found, learning can't be more fun than this!

The content of this channel is superb.

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!

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.

Visually clear, funny and interesting explanations, you are greatly talented.

One of the best explanations I had seen. Thanks man

Gives concrete examples of when column database operations are faster or slower than a row database. Thank you!

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.

Youre very entertaining to watch, listen, and learn from

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.

Your Accent and voiceovers make it more attractive to learn.

this dude is good, the channel is underrated

"Lets confused everybody by new names" : hahahaha well said ! great video thanks

I love your explanation, awesome!!! 🎉

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

You opened my eyes :D

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 :)

Great video, well explained, fun and infomative. I loved that, thanks dude!

Great explanation

Amazing content!

This just shows how much he loves what he does.

Funny and effective, loved it 👍

another banger of a video

Great information in so simple way..... It's clear the concept in best of best way 👍. I loves your all videos....

Nicely explained

Thank you very much for making this video with a real-time example. Much appreciated

I really loved your method in describing this topic .

Thanks bro, very useful

Absolutely amazing video. Thank you

Thank you so much!

Thanks. Good info. Never know how column dbs work

Thank you so much for explaining this concept so beautifully and in such a great depth...I am a fan of your teaching.....

Thank you Hussien. really simple, good and funny.

Great video and explanation, thank you.

awesome explanation for both row and column oriented db's

this was excellent it cleared up the fud👍 thanx!

Thank you so much for this explanation!!

nice explanation thank you

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

Thank you..

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!

ur awesome man .great explanation

Dude that was sweet. Any chance of doing a video on file systems and mapping them to DB OPERATIONS

Thank bro 🎉

Great explanation.

Thank you! That's very clear !

very clear. bravo!

u r the best

Really good video bro, I like what you do

Thank you so much ! it was so clear

Waiting for your udemy course. Great stuff as usual.

Great Video!

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 :)

"The devil!" "Save the ducks guys save the ducks" Now I understand databases.

hi! can you do a vid with indexes? the visuals are so helpful!

love you sir

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

Hussain Can you please make a short video of different kinds if DBs who are the providers.. what are the ideal uses.

nice demonstration

Perfect!

We generally want all the columns, that's what a record or document is

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.

great video!

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?

Which databases stores both rowbased and column based structures?

Lesson learnt from the video, Save the ducks :p

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?

Cassandra (NoSQL) uses LSM Tree which makes it a better choice for heavy writes in comparison to SQL databases, any thoughts on this?

Lmao, what's the reference to every time you write to a disk that a duck dies? 😹

This column store sounds similar to inverted indexes that search engines (eg elastic search) use. Are there key differences there?

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?

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?

Great Video Hussein.. when are you doing webrtc?

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?

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.

How do you work on 1 or less column table?? 🤔

Nasser, great video. But one observation, clearly you were High while making this video.🤣

Hahahahha you're so funny. Good video. Thanks

"...they have all this meta-data, mumbo-jumbo" -Hussein

Hussein I wanna know how you had that level of curiosity machallah? is it something gained by training?

Question, column oriented is the same with family column Db?

You’re hilarious 😂 and offer a great explanation. Thanks! #savetheducks

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?

Hey bit of an off topic question why did you change your name from igeometry?

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

"SAVE THE DUCK", guys, "SAVE THE DUCK".

interetsting video, shouldn't data in column oriented db be stored sorted ?

🦆🦆🦆🦆 Great video!

save the ducks guys!

Six Six Six, the devil... SUBSCRIBED

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

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

Awe man but ducks are delicious

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.

666 thank you for the laughter my friend

"Lets confused everybody by new names", make them look like a fool who can not understand things, thus makes us more "professional" and "experts"!