Designing a Wide-Column database on a Key-Value Store

[@kartikmahajan4405]

great explanation. very helpful. thanks a lot for this.

[@core_dump]

Thanks for watching!

[@user-dc9zo7ek5j]

I don't get why they don't use a relational database. Speed?

[@core_dump]

I don't know the actual reason internal to Pinterest, but if I have to guess... It seems like they are using this DB for analytical use-cases. In these scenario, the database is written to much more often than its read from. LSM Tree indexes are great for writing at scale in comparison to B-Tree indexes (in Relational databases). The strong relational data consistency guarantees are also not required here since it should be okay if there are few inconsistent data-points in a sea of data. (I have seen postgres being for a scenario like this and the data-model becomes quite complex. Although performance was decent, I am not sure how it would fare at Pinterest's scale) Of course, there might be multitude of other reasons, like ease of scaling, simpler data model, team expertise, established internal frameworks and infra etc.

[@prashlovessamosa]

Great explanation

[@nishitpatel7981]

Hey really great video 🙌

[@core_dump]

Thanks for the visit

[@yurii.matsak]

Great thank you!

[@core_dump]

Glad it was helpful!

[@prashlovessamosa]

1 month no upload 🫠

[@core_dump]

New video on geosharding and hilbert curve coming soon! Was dealing with some stuff lately