PlanetScale

$5 PlanetScale Postgres is live. planetscale.com/blog/5-dollar-…

We can't believe it's already been a week since @PlanetScale opened up React Miami with some scalding hot takes.

Read more planetscale.com/blog/rls-sound…

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.

PlanetScale is a Speakeasy customer 🤝 They don't just build a great database, they put in the work to build a great platform! Whether a developer is prompting an AI agent or writing infrastructure-as-code, PlanetScale just works. We've loved collaborating with them to launch the initial versions of their Terraform provider and MCP server and look forward to many more years of partnership!

Still manually optimizing database queries? There's a better way. The PlanetScale MCP server lets your AI agent read Query Insights data, analyze performance, and generate improvement suggestions specific to your codebase.

Network latency matters much more for databases than for LLM inference. Balancing network latency, capacity, and inference speed means it's sometimes better to send requests to far-away data centers. @bernhardsson discusses on the p99 podcast.

If you’re at @ReactMiamiConf and you want a LIMITED EDITION CAMO IOPS hat you’ve got to act fast

One bad query shouldn't be able to take down your whole database. PlanetScale Traffic Control lets you set and enforce resource budgets on all your query traffic. Keep your database healthy, even when clients send unexpected load.

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.

so cool watching planetscale do its thing

We've been doing an insane amount of infra work recently (real ones know 🫠) but working with the guys @PlanetScale is such a pleasure if anyone's thinking of making the switch, here's some thoughts about our experience 👇

Autumn migrated to PlanetScale and got: - Query latency reduction from ~100ms to < 10ms - Support and tooling to identify + fix slow queries - Significant decrease in CPU usage - Connection scalability Read about their migration: pscale.link/autumn-to-ps

p99 podcast x.com/i/broadcasts/1…

The PlanetScale developer education team is growing. We're looking for p99 individuals that love explaining deeply technical concepts, supporting + building our engineering community, and don't mind nerding out over databases with me all day long. I joined PlanetScale a little over 2 years ago with 0 background in the "developer experience" space. Before that I was a CS faculty member and before that a research software engineer. The past two years has been the best of my career. I get to work with some of the most talented educators, engineers, and marketers in the whole tech space. 10/10 would recommend. Come join the ride. Shoot me a DM.

Learn how to deploy PlanetScale Postgres and MySQL databases via Cloudflare and connect Cloudflare Workers. cfl.re/4cedFPp

Sharding is the best way to scale a database. But how does it work? And what's the best way to ensure data and queries are evenly distributed? Our interactive article on database sharding teaches you how.

Check out our new migration guide: planetscale.com/docs/postgres/…

pgcopydb is the best way to migrate to PlanetScale Postgres. We've used it to move multi-TB databases at speeds over 2 TB/hr. PlanetScale's custom fork adds PG 17/18 support, better CDC, and resilient retry.