How Notion shards Postgres?!

Discover the Engineering Magic Behind Notion's Scalability! 🚀 In this video, dive deep into how the popular company Notion effectively sharded their PostgreSQL database to handle massive amounts of data while maintaining performance.
Some links:
The original blog: www.notion.so/...
Transaction ID wraparound: blog.sentry.io...
Like the video ;)
#systemdesign #notion #sharding #postgres

[@shreyahehe]

Loved this video! Very clearly explained. Great to have you back!! ❤

[@versacebroccoli7238]

Glad your back! I like that you use real world examples in your videos it's very helpful.

[@eyadkhayat]

The perfect balance between keeping it simple and detailed

[@glokta1]

So happy you're back!

[@core_dump]

Thanks! more videos to come...

[@chrismuga]

I always enjoy your content bro

[@core_dump]

Thanks!!

[@shashankpathak63]

Bro you keep me updated with dev design stuffs really nice video. I was thinking whenever sharding is done whether it's on block level or logical shards level , how they ensure that the requests or basically data does not get biased to a certain physical server/node? How to maintain a balance such that they have minimum cross block calls? I just remember something called consistent hashing is used to handle this but in case they have something new !!

[@zachlandes5718]

Any info on how they actually organize the block data and relationships?

[@user-dc9zo7ek5j]

It sucks that postgres stops being useful once you have 5GB of data on a single table. The queries just take way too long.