# Move Fast and Don't Break Things: Scaling Databases for the AI Era — PlanetScale

## Executive summary

This talk outlines how modern infrastructure must scale to support the massive, unpredictable traffic generated by AI agents. The speaker argues that achieving high availability (three to five nines) requires adopting advanced architectural principles—including isolation, redundancy, sharding, back pressure, and decoupling. Crucially, the talk details how these complex systems can be safely managed and modified by AI agents through developer-friendly primitives like VSchema JSON files, Traffic Control budgets, and Git-like database branching.

## Key takeaways

- Scaling for AI-Driven Traffic: The current era, powered by AI agents, demands infrastructure that can handle massive, unpredictable spikes in traffic, requiring a shift from traditional scaling methods.
- The Importance of Developer Experience (DX): Focusing on a robust developer experience (DX) for infrastructure—providing safe, controlled primitives—is the key to enabling AI agents to interact with and manage complex systems reliably.

## Technical details

- Isolation and Redundancy: System components must be highly isolated (e.g., separating the data plane from the control plane) so that a failure in one area does not take down the entire system. Redundancy is critical for stateful workloads like databases, requiring primary and replica nodes across different availability zones.
- Sharding: To scale beyond single-node limits (e.g., 10TB+), data and queries must be spread across multiple servers (shards). Tools like Vitess (for MySQL) and Neki (for Postgres) manage this distribution using intelligent proxies.
- Back Pressure: This principle involves designing the system to gracefully degrade when overloaded. Instead of crashing, the system should detect resource thresholds (CPU, RAM) and proactively deny or fail non-critical requests, maintaining service for core users.
- Decoupling: Services (e.g., OLTP, analytics, queuing) should be independently scaled and separated to prevent resource contention and ensure that a failure in one service does not impact others.
- Agent-Controlled Infrastructure: AI agents can safely manage complex infrastructure tasks using simple interfaces: VSchema JSON files allow agents to design sharding plans for Vitess; Traffic Control sets resource budgets for graceful degradation; and database branching/deploy requests allow schema changes with one-click, non-data-losing reverts.

## Practical implications

- When designing scalable systems, prioritize architectural principles (isolation, decoupling) over convenience to prevent single points of failure.
- Implement robust resource management (back pressure) to ensure graceful degradation during traffic spikes, especially those caused by AI agents.
- Adopt Git-like workflows for database schema changes (branching, deploy requests, reverts) to make infrastructure changes as safe and auditable as code changes.
- Utilize simple configuration interfaces (like JSON VSchema) to expose complex infrastructure capabilities to AI agents, making the system manageable by automated processes.

## Topics

Database Scaling, Reliable Infrastructure, AI Agent Integration, Distributed Systems, PlanetScale, Vitess, Neki, Traffic Control

Source: https://www.youtube.com/watch?v=uKUA1a0Kdfc