PlanetScale (@PlanetScale) header
PlanetScale (@PlanetScale) profile picture

The fastest and most reliable database for Postgres & Vitess Discord: https://xitter.twitterapi.xyz/t.co/vGOpjxZx8H https://xitter.twitterapi.xyz/t.co/wQJpk2fXwb

Joined February 2018
Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)Photo by PlanetScale (@PlanetScale)
Neki is now available.
64
135
66
1,820
806,651
PlanetScale retweeted
A well designed schema with optimized indexes is the foundation of good database performance. Combined with great hardware (local NVMe) you get an insane system. PlanetScale gives you the tools to automate figuring out the former. And the latter, well, we have it on lock.
classic, forgot an index
3
6
205
7,941
PlanetScale is at KubeCon in SLC. Stop by to get a demo, grab some merch, and meet the team.
1
4
2
63
4,862
What would Postgres look like if you designed it from scratch today? And can LLMs build bbtree, the fastest B-tree around, without giving up correctness? Manish Rai Jain (Egres) and Xiangpeng Hao (SpiralDB) answer both tonight at the SF Database Meetup at PlanetScale HQ. luma.com/planet-vxwl
1
5
2
35
3,806
PlanetScale retweeted
How do you ship fast while not breaking the database? Most of the principles are decades-old ideas in reliable infrastructure. The key with agents is exposing them as primitives in just the right ways. My talk from AIE this summer (YouTube link below)
20
19
3
338
20,372
Full house tonight at the @depotdev x PlanetScale ramen pop-up.
4
5
1
36
2,743
Failover cannot be an afterthought. It is, fundamentally, how you create reliable databases in the face of inevitable server and network failures. How we designed them in Neki ↓ planetscale.com/blog/designi…
4
2
3
95
4,455
PlanetScale retweeted
Was fun hearing Bruce Momjian, co-founder of open source PostgreSQL, trace the roots of Postgres and the evolution of its ecosystem over the past 30+ years. Fittingly hosted by @PlanetScale, where the next chapter of Postgres is being concocted. (See Neki.dev 🐈‍⬛)
1
3
471
PlanetScale retweeted
30 years of @PostgreSQL, and the secret was never one company. It's the loop: developers propose, users discuss, everyone tests, bugs get fixed in the open. Proprietary software builds in isolation and hears back after the sale. Great to hear Bruce Momjian of @EDBPostgres make that case tonight at @PlanetScale's Postgres Day SF. Everything we build at Constructive stands on that loop. 🐘 #PostgreSQL
3
3
48
2,139
PlanetScale retweeted
This is from our October internal availability report. We're far from perfect, but we're doing well. The biggest contributor to this is our MySQL databases being hosted on PlanetScale. Also, no sign of our AI acceleration causing serious problems.
2
9
4
76
12,799
If you can't make it over for coffee, we'd love to see you at tonight's PGDay meetup. ​We’ll be joined by Bruce Momjian, co-founder of open source Postgres, along with PlanetScale’s Postgres Core team, to dive into how Postgres got to where it is today and where it’s headed. luma.com/haxfnzo1
1
6
1,360
"Moving our control plane to PlanetScale delivered predictable performance, removed a significant amount of operational work, and gave us better tools for understanding how the database behaves in production." Read the full case study from Mixedbread: mixedbread.com/blog/planetsc…
4
38
2,819
Performance 101: Step 1: Move your app closer to your database Step 2: Move your database storage closer to your database compute planetscale.com/blog/the-hid…
20
32
12
580
164,327
AWS regions and availability zones are how applications stay online when hardware fails, power goes out, or a whole data center goes MIA.  Here's how they work.
5
8
4
135
27,113
DROP TABLE is the most scalable Postgres data-deletion strategy. The reason? A complex interplay between Postgres MVCC, replication, and how indexes work.
5
5
2
75
9,209