✳flâneur — a map of the web's best reading
Making 768 servers look like 1 — PlanetScale
planetscale.com · 2,271 words · saved by 1 readers
How to make 768 distinct Postgres servers look like 1 to your applications.
Making 768 servers look like 1 Ben Dicken [ @ BenjDicken ] | July 15, 2026 This is 768 servers. To some, that looks like a lot of computers. To those managing the infrastructure for apps with millions of customers, executing millions of queries per second, pretty normal. Products at this scale frequently require thousands of servers working in unison. The most difficult infrastructure component to scale is almost always the database. A single database server cannot handle such demand, so we must spread the queries and data out across many servers with database sharding . Database sharding is t
Explore this link on the map →saved by
related reading
- Scaling PostgreSQL to power 800 million ChatGPT users | OpenAIopenai.com
- An Overview of Distributed PostgreSQL... | Crunchy Data Blogcrunchydata.com
- Herding elephants: Lessons learned from sharding Postgres at Notionnotion.so
- Benchmarking How Workflow Execution Scales on Postgres | DBOSdbos.dev
- Sharding with Amazon Relational Database Service | AWS Database Blogaws.amazon.com
- Sharding - Database Manual - MongoDB Docsmongodb.com
- How Figma's Databases Team Lived to Tell the Scale | Figma Blogfigma.com
- Schedule | POSETTE: An Event for Postgres 2024 - Citus Datacitusdata.com
- Just Use Postgres for Everything | Amazing CTOamazingcto.com
- PgBouncer PostgreSQL performancejfrog.com
- The only scalable delete in Postgres is DROP TABLE — PlanetScaleplanetscale.com
- Nine ways to shoot yourself in the foot with PostgreSQLphilbooth.me