Sign in

PlanetScale

@planetscale.com
1.9K followers 9 following 282 posts

The database platform built for scale. Postgres and Vitess/MySQL. planetscale.com Discord: discord.gg/pDUGAAFEJx Status: planetscalestatus.com

PostsRepliesMedia
PlanetScale @planetscale.com · 1h
What happens to your database if the data center goes down? Build it right and it just keeps working.
youtube.com
The data center caught FIRE (but my app is fine)
AWS regions and availability zones are how applications stay online...
000
PlanetScale @planetscale.com · 29/09/2026
Ever wonder what happens to a query when your Postgres database is spread across 1000s of servers? Follow one through auth, the wire protocol, parsing, planning, and connection pooling, then back to your app with the results.
planetscale.com
The lifecycle of a sharded Postgres query — PlanetScale
Follow a SQL query through the router, across four Postgres shards, and back.
141
PlanetScale @planetscale.com · 28/09/2026
Suffering from success? When a huge tenant starts stressing your shards, Neki has the tools to scale up, isolate, and reshard without stress.
planetscale.com
Handling hot shards — PlanetScale
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.
010
PlanetScale @planetscale.com · 25/09/2026
ARM or x86? Your choice has a big impact on Postgres performance. Here's what to know before you pick: planetscale.com/blog/when-to...
planetscale.com
When to choose x86-64 vs aarch64 — PlanetScale
ARM and x86 can give you different performance at the same vCPU count. Here's what differs, what to measure, and how to choose.
000
PlanetScale @planetscale.com · 24/09/2026
Join us for PlanetScale Movie Night on October 17. We'll be watching "You Can See Everything" at AMC Kabuki 8 in San Francisco. Tickets are limited, so make sure to RSVP: luma.com/qjw9i5a9
luma.com
PlanetScale Movie Night: You Can See Everything · Luma
Nathan Fielder made a documentary about Elizabeth Holmes, we got a bunch of tickets to watch it with you. Join us at AMC Kabuki 8 to watch You Can See…
020
PlanetScale @planetscale.com · 23/09/2026
SELECT name FROM search_engines WHERE description ==> '"fast text search"'; name ------ TIN (1 row) Read the blog: planetscale.com/blog/searchi...
planetscale.com
TIN Postgres search is faster, better, and cheaper — PlanetScale
A good Postgres search demo was doing the rounds online. Let's see what happens when we upgrade it to TIN.
010
PlanetScale @planetscale.com · 23/09/2026
PlanetScale is at Rails World this week in Austin, Texas. Come by our booth for merch, a product demo, and to meet some of the team.
020
PlanetScale @planetscale.com · 22/09/2026
How do you make text search fast? Inverted indexes, tokenizers, BM25, segment merges, and more. Our latest article covers what it takes to build a search engine inside Postgres.
planetscale.com
Anatomy of a (Postgres) search engine — PlanetScale
How a full-text search engine works, and how it works in Postgres
040
PlanetScale @planetscale.com · 21/09/2026
How do you build the fastest text search in Postgres? Ask the two engineers who did it. TIN TALK: live Q&A with Eric and Patrick on our Discord, Monday 11am PT. Join to ask your questions: pscale.link/community
000
PlanetScale @planetscale.com · 21/09/2026
A Postgres replica can finish replaying WAL and still not be safe to promote. If it doesn't have your logical replication slots, your change stream breaks on cutover. See how PlanetScale solves this:
planetscale.com
Blocking cutovers to save replication slots — PlanetScale
Postgres understands high-availability architecture, but its defaults assume you don't have replication slots. This can get you into trouble in a cutover event. The combination of what Postgres can do and what PlanetScale lets you do is what keeps connected applications safe.
120
PlanetScale @planetscale.com · 18/09/2026
Let's take a closer look at how Neki is built. Starting with real Postgres, we unpack the architecture one component at a time:
planetscale.com
The architecture of Neki — PlanetScale
Sharded Postgres, from the team behind Vitess
040
PlanetScale @planetscale.com · 18/09/2026
We wanted more from full text search in Postgres, so we built TIN. It gives you fuzzy matching, NEAR, wildcards, boolean grouping, and BM25 scoring. Plus, it's really fast. See it in action in our latest video:
youtu.be
We fixed search in postgres
Check out https://planetscale.com for more Postgres and MySQL conte...
000
PlanetScale @planetscale.com · 16/09/2026
Today we introduce TIN: a powerful and reliable full-text search extension for Postgres. TIN works with complicated WHERE clauses, replication, backups, and maintains correct transaction visibility. It's also mind-blowingly fast.
154
PlanetScale @planetscale.com · 15/09/2026
It was a packed house last week for the SF Database Meetup. Our CTO @nvw.io took the stage to break down sharding, why we built Neki, and why it's much more than just sharded Postgres. Full talk on YouTube:
youtube.com
The next evolution of cloud Postgres
Neki is available today in platform preview: https://neki.devNeki...
010
PlanetScale @planetscale.com · 14/09/2026
Join us for the @changelog.com IRL at PlanetScale HQ. We'll have three special guests joining us to discuss background agents, developer tools, and more. Happening in San Francisco this Thursday, September 17th. RSVP:
luma.com
PlanetScale presents Changelog IRL · Luma
We're happy to have Adam Stacoviak, founder and editor-in-chief of Changelog, at PlanetScale's HQ for Changelog IRL! An evening of short talks and…
000
PlanetScale @planetscale.com · 14/09/2026
S3 doesn't work the way you think it does. In this video, we uncover how S3 handles millions of requests per second on basic hard drives.
youtube.com
S3 doesn't work the way you think
Check out https://planetscale.com for more Postgres and MySQL conte...
000
PlanetScale @planetscale.com · 11/09/2026
118,538,803 queries per second. 1.22 PiB of data. 512 shards. Powered by Neki. planetscale.com/blog/118-mil...
planetscale.com
118 million queries per second on Neki — PlanetScale
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.
066
PlanetScale @planetscale.com · 10/09/2026
Neki, horizontal sharding for Postgres, is available today. Join us tonight for a first look at Neki with talks on Neki's architecture, why you should shard, the lifecycle of a query, and data movement between shards.
luma.com
THE SF DATABASE MEETUP: Neki Edition · Luma
Join us on September 10th for a first look into Neki, our sharded Postgres product. We'll have talks from our database professor Ben Dicken, CTO Nick Van…
043
PlanetScale @planetscale.com · 10/09/2026
Neki is now available.
132
PlanetScale @planetscale.com · 02/09/2026
We're pulling back the curtain on Neki, our sharded Postgres product, on Sept 10. The lineup: @nvw.io — A look at Neki's architecture @benjdd.com — Why Postgres needs sharding Harshit Gangal — The lifecycle of a query in Neki And more! Limited spots:
luma.com
THE SF DATABASE MEETUP: Neki Edition · Luma
Join us on September 10th for a first look into Neki, our sharded Postgres product. We'll have talks from our database professor Ben Dicken, CTO Nick Van…
052
PlanetScale @planetscale.com · 02/09/2026
Unblock stuck connections with live connection management in the PlanetScale CLI and dashboard. Find out more. planetscale.com/blog/debugging-live…
020
PlanetScale @planetscale.com · 01/09/2026
Every query in Neki gets two plans. The Neki plan decides which shards run the query and how their results are combined. Postgres then decides how each shard executes its work. A closer look at the Neki router:
planetscale.com
What is a Neki router? — PlanetScale
A Neki router gives applications a Postgres connection to one database while planning and coordinating queries across the shards behind it.
000
PlanetScale @planetscale.com · 31/08/2026
You've just been paged. Every database query is failing to execute. Figure out why. This exact question is how early GitHub hired its DBAs. The answer in our latest blog: planetscale.com/blog/debugging-live…
010
PlanetScale @planetscale.com · 28/08/2026
Join us on September 10th for a first look at Neki, our sharded Postgres product. We’ll have talks from our database professor @benjdd.com , CTO @nvw.io, and some members of the Neki team doing a deep dive into Neki’s architecture.
luma.com
THE SF DATABASE MEETUP: Neki Edition · Luma
Join us on September 10th for a first look into Neki, our sharded Postgres product. We'll have talks from our database professor Ben Dicken, CTO Nick Van…
000
PlanetScale @planetscale.com · 28/08/2026
You've probably never heard of sub-linear scaling. But if your Postgres database keeps taking on more traffic, you're headed there. You can scale by throwing bigger servers at it. But eventually, you need to scale beyond one machine. Neki gives you sharded Postgres from the team behind Vitess.
000
PlanetScale @planetscale.com · 28/08/2026
Postgres vs MySQL: who does indexing better? We put them head-to-head, with post-it notes and all.
youtube.com
What the hell is an index? postgres vs MySQL
Check out https://planetscale.com for more Postgres and MySQL conte...
010
PlanetScale @planetscale.com · 27/08/2026
Mixedbread moved their control plane to PlanetScale and eliminated a significant amount of operational work: Their hottest control-plane queries now execute with sub-millisecond latency. Read more: www.mixedbread.com/blog/planetscale…
050
PlanetScale @planetscale.com · 27/08/2026
PlanetScale CEO @samlambert.com holds nothing back in this new episode of Changelog. His thoughts on if Neki gets open sourced, Amazon's impact on open source, and why running the world's largest sharded databases is not something a competitor can shortcut. changelog.com/podcast/684
changelog.com
Postgres at PlanetScale with Sam Lambert, CEO of PlanetScale (Changelog Interviews #684)
Sam Lambert is back after 4 years and he does not hold back! We cover $5 PlanetScale Postgres, the Neki "do-over" of Vitess, agents shipping schema changes through deploy requests, rolling back a 500T...
020
PlanetScale @planetscale.com · 26/08/2026
Unlimited IOPS helped Sazabi cut a 5 figure bill to $500 on PlanetScale Metal. Sazabi is an AI native observability platform powering companies like Mastra, Weave, and Sandstone. Here's Sherwood Callaway telling @samlambert.com his migration story.
020
PlanetScale @planetscale.com · 25/08/2026
A large table is never just a large table. It's bloated. Slow to vacuum and repack. Holds connections. Over-indexed. It's a big pain that sharding solves.
planetscale.com
Problems with large tables in Postgres — PlanetScale
Postgres presents pretty predictable performance problems when dealing with large tables. Sharding solves this.
020
PlanetScale @planetscale.com · 24/08/2026
Scaling Postgres has been attempted by many engineering teams. Each pushed Postgres scalability forward. Each came with compromises. Neki addresses these shortcomings. Learn how we got here in this brief history of Postgres sharding:
planetscale.com
The history of Postgres sharding — PlanetScale
Why has it taken so long to get good Postgres sharding? The last 20 years are the answer.
020
PlanetScale @planetscale.com · 18/08/2026
Poisoned connection pools can bring your application to a halt. Find out how this happens and ways to prevent it in our latest blog. planetscale.com/blog/postgre...
planetscale.com
Poisoned Postgres connection pools — PlanetScale
An engineer's worst nightmare is waking up to a seemingly read-only database with no clear issue in sight. Let's dig into why this happens, and how AI can help solve it.
010
PlanetScale @planetscale.com · 07/08/2026
Reduce parallelism. Increase throughput. Sounds backwards, but past a certain point, each additional in-flight query can make all the others slower. We recently observed this in a customer's Vitess database. How it happened, and the fix: planetscale.com/blog/concurr...
planetscale.com
Concurrency vs. Throughput: why more parallelism can make databases slower — PlanetScale
Increasing throughput sometimes requires reducing parallelism. A look into why this is the case for Vitess + MySQL databases
050
PlanetScale @planetscale.com · 27/07/2026
You can't manage what you can't measure. View detailed graphs for any available query metric in Insights: CPU time, blocks read/written, cache hit ratio, and more.
121
PlanetScale @planetscale.com · 15/07/2026
Sharding is how you scale relational databases. Bottlenecks like server write limits, data size, and slow backups mean eventually, your data should live on multiple servers. Learn how we do this at PlanetScale with Neki and Vitess in our latest blog.
130
PlanetScale @planetscale.com · 07/07/2026
Join us in SF on August 31 for CRITICAL mass, a talk series held under NDA and Chatham House rules, going deep on how PlanetScale achieves extreme reliability. No recording, no record, just a moment in time.
luma.com
CRITICAL mass · Luma
Announcing CRITICAL mass, a one-of-a-kind talk series and networking event held under NDA and Chatham House rules. Every leading company is struggling to keep…
000
PlanetScale @planetscale.com · 29/06/2026
Vitalize migrated to PlanetScale and saw: - P95 latency dropped to 2ms - Heavy JSONB reads dropped from 50s -> 1.2s - Half the vCPUs with better performance - Actionable performance info with Query Insights Read all about their migration:
vitalize.care
From Supabase to PlanetScale: Zero Downtime, 400GB, 150 Million Rows - Vitalize
Our recent migration to PlanetScale ensures our platform can scale reliably in an industry where precision and speed directly affect patient care.
040
PlanetScale @planetscale.com · 23/06/2026
PlanetScale's fault tolerance is built on straightforward principles and architectures. The challenge is in the execution. Here are the principles we follow to keep our systems reliable:
planetscale.com
The principles of extreme fault tolerance — PlanetScale
The principles and processes we follow for fault tolerance.
010
PlanetScale @planetscale.com · 29/05/2026
Always bet on JavaScript.
010
PlanetScale @planetscale.com · 26/05/2026
At scale, you can only put off sharding for so long. YouTube scaled MySQL with Vitess, and now we're building the same for Postgres.
020
Reposted by PlanetScale
Matt Blewitt @matt.blwt.io · 20/05/2026
I'm hiring for my team @planetscale.com, in AMER and EMEA, fully remote. Come build the best Postgres product on the planet with super talented folks, very high autonomy, tier-zero databases. DMs open if you'd like to talk first, happy to chat. job-boards.greenhouse.io/planetscale/...
093
PlanetScale @planetscale.com · 20/05/2026
Magicare migrated to PlanetScale and achieved an 85%+ reduction in query latency, 17× faster materialized view refreshes, and a 6× smaller database footprint per instance. Read the article for all the details.
magicare.ai
How Magicare cut query latency by 85% by moving to PlanetScale - Magicare.ai
Magicare drives better patient outcomes, automates your busywork, and increases employee happiness—all from one simple dashboard purpose built for post acute healthcare.
010
PlanetScale @planetscale.com · 19/05/2026
If you’re not careful, ingress (free) can become egress (not free). Double-check your agents work, they could quietly be costing you money.
000
PlanetScale @planetscale.com · 14/05/2026
Egress costs are an annoying reality of AWS and GCP. But there are ways to minimize the pain while also getting more out of your database. New post on how to send less data, save money, and make your apps faster: planetscale.com/blog/databas...
planetscale.com
Egress problems and where to find them — PlanetScale
Reducing the size and frequency of requests to your database has the double benefit of making your applications faster and cheaper.
110
PlanetScale @planetscale.com · 13/05/2026
82,000x database performance improvement? A single index can do that, and PlanetScale Insights can tell you where.
030
PlanetScale @planetscale.com · 07/05/2026
It's easy to introduce slow queries into your workload. Tracking them down should be easy too. PlanetScale Insights shows you which queries are slow and why. Combined with our MCP server, you can automate fixing them.
310
PlanetScale @planetscale.com · 05/05/2026
Most database benchmarks are bad. The problems are often subtle. Mismatched instances, cold caches, and coordinated omission all produce misleading results. Today, we’re publishing guidance on how to do it right, and updating our acceptable use policy to allow benchmarking.
120
PlanetScale @planetscale.com · 04/05/2026
pgvectorscale augments pgvector with StreamingDiskANN, making larger-than-RAM vector indexes achievable in Postgres. It also adds statistical binary quantization for improved search recall over regular quantization. PlanetScale supports both. Try them today.
110
PlanetScale @planetscale.com · 30/04/2026
Postgres RLS sounds great in theory: embedded access control right in the database. In practice, there's complexity in policy configuration, managing your attack surface, and performance implications. Our latest article takes a deep dive into RLS.
120
PlanetScale @planetscale.com · 21/04/2026
Postgres has three ways to isolate tenants: - Logical databases - Per-tenant schemas - Tenant ID in a shared schema Counterintuitively, the last is the best way to scale. Read about why in our latest article.
110