# vitess Open-source database clustering system for horizontally scaling MySQL. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The history of Postgres sharding DevFeed: [The history of Postgres sharding]() Original publisher: [Read original article]() Author: Josh Brown Published: 2026-08-24T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [Database](), [vitess](), [Tooling](), [LAMP]() Tags: [complexity](), [database](), [databases](), [engineering](), [history](), [mysql](), [neki](), [postgres](), [scale](), [servers](), [vitess]() ### AI overview The article traces the history of database sharding, focusing on why Postgres took longer than MySQL to develop mature sharding solutions. It discusses the origins of the term "shard," the role of MySQL's ecosystem and tools such as Vitess, and how companies including Facebook and YouTube addressed growth and increasing database workloads. ### Source excerpt Why has it taken so long to get good Postgres sharding? The last 20 years are the answer. ## Concurrency vs. Throughput: why more parallelism can make databases slower DevFeed: [Concurrency vs. Throughput: why more parallelism can make databases slower]() Original publisher: [Read original article]() Author: Liz van Dijk Published: 2026-08-07T00:00:00Z Content type: article Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [MySQL](), [vitess](), [Concurrency](), [bug](), [Cloud]() Tags: [bug](), [cloud](), [concurrency](), [databases](), [engineering](), [mysql](), [vitess]() ### AI overview Increasing database parallelism can reduce throughput and destabilize a production system. The article examines how a long-running MySQL transaction, growing version history, retries, and an uncapped request surge caused widespread failures, and explains how Vitess transaction timeouts and connection-pool limits can contain the impact. ### Source excerpt Increasing throughput sometimes requires reducing parallelism. A look into why this is the case for Vitess + MySQL databases ## See what your database is doing right now with Connections DevFeed: [See what your database is doing right now with Connections]() Original publisher: [Read original article]() Author: Brett Warminski Published: 2026-06-15T00:00:00Z Content type: release Language: en Sources: [Blog -- PlanetScale]() Topics: [Databases](), [debugging](), [vitess](), [Command-line interface](), [Processes]() Tags: [cli](), [database](), [databases](), [debugging](), [incident](), [logs](), [monitor](), [process](), [product](), [resources](), [tools](), [vitess]() ### AI overview Connections is a new PlanetScale CLI feature for Postgres and Vitess databases. It provides a live, refreshable view of active sessions, highlights blocked queries and waiting states, shows blocker trees, maintains recent history, and lets developers capture the observed session data for later handoff. ### Source excerpt Connections lets you monitor and manage all active connections to Postgres and Vitess databases. See active sessions, identify locking patterns, and keep debugging even when normal application connections are exhausted. ## Announcing Multigres: Vitess for Postgres DevFeed: [Announcing Multigres: Vitess for Postgres]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2025-06-10T07:00:00Z Content type: release Language: en Sources: [Supabase Blog]() Topics: [vitess]() Tags: [availability](), [database](), [mysql](), [postgres](), [vitess]() ### AI overview Supabase announces Multigres, a Postgres-focused proxy inspired by Vitess. The project aims to provide a gradual path from connection pooling and high availability to sharding for large-scale Postgres workloads. ### Source excerpt Today we are welcoming Sugu, the co-creator of Vitess, to the Supabase team. He is joining Supabase to build Multigres: Vitess for Postgres. ## Cash App on PlanetScale Metal DevFeed: [Cash App on PlanetScale Metal]() Original publisher: [Read original article]() Author: Aaron Young Published: 2025-03-11T00:00:00Z Content type: article Language: en Sources: [Cash App Code Blog]() Topics: [migration](), [vitess](), [MySQL](), [Kubernetes](), [Availability](), [Cloud]() Tags: [availability](), [cloud](), [kubernetes](), [migration](), [mount](), [mysql](), [storage](), [vitess]() ### AI overview Cash App describes its migration from self-managed Vitess and MySQL infrastructure in its datacenters to PlanetScale's cloud-managed product, and its subsequent work with PlanetScale to migrate its fleet to PlanetScale Metal. The article explains the original architecture and reports storage-volume degradation, manual shard failovers, and periods when shards could not accept writes. ### Source excerpt Cash App moves to PlanetScale to drive efficiencies ## Horizontally scaling the Rails backend of Shop app with Vitess DevFeed: [Horizontally scaling the Rails backend of Shop app with Vitess]() Original publisher: [Read original article]() Author: Hammad Khalid Published: 2024-01-17T20:34:53Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [vitess]() Tags: [architecture](), [backend](), [mysql](), [ruby](), [vitess]() ### AI overview The article describes scaling the Shop app's Ruby on Rails backend as growth pushed its MySQL datastore toward its limits, culminating in an approach centered on Vitess. ### Source excerpt Shop app horizontally scaled a Ruby on Rails app with Vitess. This blog describes Vitess and our detailed approach for introducing Vitess to a Rails app. ## Shard Splits with Consistent Snapshots DevFeed: [Shard Splits with Consistent Snapshots]() Original publisher: [Read original article]() Author: Andrés Taylor Published: 2018-12-04T17:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [vitess](), [MySQL](), [Databases](), [data](), [Algorithm]() Tags: [algorithm](), [customers](), [database](), [databases](), [engineering](), [locks](), [mysql](), [vitess]() ### AI overview This tutorial explains how Square performs gradual MySQL shard splits using Vitess while data continues changing. It covers online cloning, inconsistent destination copies, and consistent snapshots to reduce application impact during the process. ### Source excerpt How to take a copy of something too large to fit in a single shot