Herding elephants: Lessons learned from sharding Postgres at Notion
With an effort to make Notion faster and more reliable for years to come — we migrated Notion’s PostgreSQL monolith into a horizontally-partitioned database fleet.
All posts ← ← All posts Published October 6, 2021 in Tech Herding elephants: Lessons learned from sharding Postgres at Notion By Garrett Fidalgo Infrastructure Technical Lead Share this post Earlier this year, we took Notion down for five minutes of scheduled maintenance. While our announcement gestured at “increased stability and performance,” behind the scenes was the culmination of months of focused, urgent teamwork: sharding Notion’s PostgreSQL monolith into a horizontally-partitioned database fleet. The shard nomenclature is thought to originate from the MMORPG Ultima Online , when the ga
Explore this link on the map →related reading
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- Making 768 servers look like 1 — PlanetScaleplanetscale.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- Sharding with Amazon Relational Database Service | AWS Database Blogaws.amazon.com
- Nine ways to shoot yourself in the foot with PostgreSQLphilbooth.me
- The data model behind Notion's flexibilitynotion.so
- Schedule | POSETTE: An Event for Postgres 2024 - Citus Datacitusdata.com
- How Figma's Databases Team Lived to Tell the Scale | Figma Blogfigma.com
- How we migrated our PostgreSQL database with 11 seconds downtime – Government Digital Servicegds.blog.gov.uk
- Sharding - Database Manual - MongoDB Docsmongodb.com
- Benchmarking How Workflow Execution Scales on Postgres | DBOSdbos.dev
- Creating the Notion APInotion.com