Column vs Row Oriented Databases Explained
ฝัง
- เผยแพร่เมื่อ 16 มิ.ย. 2024
- In this video, I explain the differences between Column vs Row Oriented Database Storage how efficient each method is, and their pros & cons. We will also see how different queries perform against both types of databases.
0:00 Intro
2:50 Row-Oriented Database
15:30 Column-Oriented Database
26:30 Pros & Cons
Download slides here
payhip.com/b/JVHIM
🎙️Listen to the Backend Engineering Podcast
husseinnasser.com/podcast
🏭 Backend Engineering Videos
• Backend Engineering (B...
💾 Database Engineering Videos
• Database Engineering
🏰 Load Balancing and Proxies Videos
• Proxies
🏛️ Software Archtiecture Videos
• Software Architecture
📩 Messaging Systems
• Message Queues & PubSu...
Become a Member
/ @hnasr
Support me on PayPal
bit.ly/33ENps4
Stay Awesome,
Hussein - วิทยาศาสตร์และเทคโนโลยี
Clearly, you're a naturally gifted teacher. Great content.
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!
Love the way you teach. I almost didn't want the video to end.
#savetheducks
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!
The content of this channel is superb.
One of the best explanations I had seen. Thanks man
Thank you very much for making this video with a real-time example. Much appreciated
Great video, well explained, fun and infomative. I loved that, thanks dude!
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.
Gives concrete examples of when column database operations are faster or slower than a row database. Thank you!
Thank you so much for explaining this concept so beautifully and in such a great depth...I am a fan of your teaching.....
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.
this dude is good, the channel is underrated
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
Glad it was helpful! and welcome to the community
I really loved your method in describing this topic .
Thanks. Good info. Never know how column dbs work
Thank you Hussien. really simple, good and funny.
awesome explanation for both row and column oriented db's
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 :)
Youre very entertaining to watch, listen, and learn from
❤️❤️❤️
Absolutely amazing video. Thank you
Your Accent and voiceovers make it more attractive to learn.
Thank you so much for this explanation!!
Thank you! That's very clear !
Thank you so much ! it was so clear
Really good video bro, I like what you do
@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.
Waiting for your udemy course. Great stuff as usual.
Great video and explanation, thank you.
this was excellent it cleared up the fud👍 thanx!
Great information in so simple way..... It's clear the concept in best of best way 👍. I loves your all videos....
Thanks Virendra 🙏
hi! can you do a vid with indexes? the visuals are so helpful!
nice explanation thank you
This just shows how much he loves what he does.
Amazing content!
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.
Correct that is why didn’t include indexes in the mix. Thanks for the feedback as usual
Great explanation.
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?
Great explanation
Great Video!
ur awesome man .great explanation
very clear. bravo!
Thanks bro, very useful
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 :)
Nice! Your going HTAP
@@hnasr No, not going hybrid transactional, as the columnar data is being used as runtime in memory data until a bulk update changes it.
@@chunheguo9230 hi please could you give me more details how i can do the same? please reply
@@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.
great video!
Nicely explained
Dude that was sweet. Any chance of doing a video on file systems and mapping them to DB OPERATIONS
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
This column store sounds similar to inverted indexes that search engines (eg elastic search) use. Are there key differences there?
Hussain
Can you please make a short video of different kinds if DBs who are the providers.. what are the ideal uses.
You opened my eyes :D
Funny and effective, loved it 👍
"Lets confused everybody by new names" : hahahaha well said ! great video thanks
nice demonstration
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?
Thank you so much!
Cassandra (NoSQL) uses LSM Tree which makes it a better choice for heavy writes in comparison to SQL databases, any thoughts on this?
another banger of a video
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!
it's called horizontal partitioning. read about it on net
Great Video Hussein.. when are you doing webrtc?
I am working on the slides, once thats done Ill work on the demos so maybe a week or two
@@hnasr Thanks
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?
Which databases stores both rowbased and column based structures?
Hussein, thanks for the videos. Today imma try & figure out how to download a TH-cam video with vanilla NodeJs if I don’t figure imma ask you guys for help
Perfect!
u r the best
Thank you..
How do you work on 1 or less column table?? 🤔
Thank bro 🎉
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?
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
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.
Awesomeeeeee
Question, column oriented is the same with family column Db?
Yes same name. Columnar and column store are other names.
love you sir
"The devil!"
"Save the ducks guys save the ducks"
Now I understand databases.
Hussein I wanna know how you had that level of curiosity machallah? is it something gained by training?
It is pure curiosity and asking why and having the humility to learn takes time.
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.
Hey bit of an off topic question why did you change your name from igeometry?
Moving from GIS to personal brand so I get to cover multiple topics mainly.
We generally want all the columns, that's what a record or document is
Lmao, what's the reference to every time you write to a disk that a duck dies? 😹
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.
interetsting video, shouldn't data in column oriented db be stored sorted ?
Not necessary, the table data aren't stored sorted usually otherwise writing becomes difficult. Indexes on the other hand are sorted
You’re hilarious 😂 and offer a great explanation. Thanks!
#savetheducks
Lesson learnt from the video, Save the ducks :p
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?
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
"...they have all this meta-data, mumbo-jumbo"
-Hussein
Nasser, great video. But one observation, clearly you were High while making this video.🤣
Hahahahha you're so funny. Good video. Thanks
"SAVE THE DUCK", guys, "SAVE THE DUCK".
Six Six Six, the devil... SUBSCRIBED
🦆🦆🦆🦆 Great video!
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
Correct wide column is different. Group of columns into a column family. Best of both words
save the ducks guys!
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"!