Blog
Nick Van Wiggeren [@NickVanWig] |
Neki, sharded Postgres by PlanetScale, is now available in platform preview. →
How Neki only decodes the parts of a PostgreSQL result the router actually needs. →
Simeon Griggs [@simeonGriggs] |
What makes a good sharding strategy today might not work so well tomorrow. What happens when you have one tenant hitting your database orders of magnitude more than any other? Or product managers knocking down your door with new requirements? If you're already on Neki, fortunately these are issues we can solve. →
Ahmed Darwich [@AhmedDarwich] |
ARM and x86 can give you different performance at the same vCPU count. Here's what differs, what to measure, and how to choose. →
Sharded Postgres, from the team behind Vitess →
Florent Poinsard, Hirad Pourtahmasbi |
We ran a massive, sharded Postgres database at 118.5 million queries per second, with 200k queries per second on each shard across 512 shards. →
Follow a SQL query through the router, across four Postgres shards, and back. →
Andres Taylor, Harshit Gangal, Ahmed Darwich [@AhmedDarwich] |
A Neki router gives applications a Postgres connection to one database while planning and coordinating queries across the shards behind it. →
Josh Brown [@imjosh] |
Why has it taken so long to get good Postgres sharding? The last 20 years are the answer. →
Harshit Gangal, Ahmed Darwich [@AhmedDarwich] |
A data topology describes the sharding scheme a Neki router uses to map logical PostgreSQL tables to physical shards and route queries. →
PlanetScale backs up petabyte-scale sharded Postgres databases in hours using parallel infrastructure, object storage, and WAL replay. →
Andres Taylor, Dirkjan Bussink, Harshit Gangal, Nick Van Wiggeren [@NickVanWig], Noble Mittal, Rohit Nayak, Roman Sodermans, Shlomi Noach, Sam Lambert [@samlambert] |
Sharded Postgres by the team behind Vitess →