📹 The future of AI infrastructure: optimize and shard your database with agents.Watch the talk
Navigation

Blog

Get the RSS feed

Mike Coutermarsh |

Connect Claude, Cursor, and other AI tools directly to your PlanetScale database to optimize schemas, debug queries, and monitor app performance.


Ben Dicken [@BenjDicken] |

What are database transactions and how do SQL databases isolate one transaction from another?


Mike Coutermarsh |

How PlanetScale uses Cursor commands to automate our changelog entries


Chris Sinjakli |

Postgres 18 is now available on PlanetScale


Ben Dicken [@BenjDicken] |

Using MotherDuck with PlanetScale


Richard Crowley |

We've lowered the entry price for using PlanetScale Metal to $50 and added more flexibility in storage-to-compute ratios.


Rafer Hazen |

Introducing AI-powered index suggestions for PostgreSQL


Sam Lambert [@samlambert] |

You can now create single node Postgres databases on PlanetScale starting at just $5.


Vitess Engineering Team |

Vitess 23 is now generally available


Sam Lambert [@samlambert] |

Introducing $50 PlanetScale Metal


Richard Crowley |

On 2025-10-20, there was an incident that affected PlanetScale, initially caused by DNS misconfiguration in one of PlanetScale’s service providers, followed by several hours of capacity constraints and network instability.


Sam Lambert [@samlambert] |

Introducing the $5 PlanetScale plan.


Ben Dicken [@BenjDicken] |

Postgres 18 brings a significant improvement to read performance via async I/O and I/O worker threads. Here we compare its performance to Postgres 17.


Vicent Martí |

A new hybrid design for scalable vector indexes and a reference implementation in MySQL


Mike Coutermarsh |

You can now easily set up PlanetScale databases with Cloudflare Workers using this native integration.


Ben Dicken [@BenjDicken] |

Processes and threads are fundamental abstrations for operating systems. Learn how they work and how they impact database performance in this interactive article.


Sam Lambert [@samlambert] |

Why a lagging client can stall or break failover, and how MySQL’s GTID model avoids it.


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


Ben Dicken [@BenjDicken] |

Every time you use a computer, the cache is working to ensure your experience is fast.


Max Englander |

The principles and processes we follow for fault tolerance.


Sam Lambert [@samlambert] |

PlanetScale now supports Postgres


Ben Dicken [@BenjDicken] |

Benchmarking Postgres in a transparent, standardized and fair way is challenging. Here, we look at the process of how we did it in-depth


Vitess Engineering Team |

Vitess 22 is now generally available


Patrick Reynolds |

You can now use vector search and storage in your PlanetScale MySQL database.


Vicent Martí |

A novel technique for implementing dynamic language interpreters in Go, applied to the Vitess SQL evaluation engine