CtrlK
BlogDocsLog inGet started
Tessl Logo

vitess

Vitess best practices, query optimization, and connection troubleshooting for PlanetScale Vitess databases. Load when working with Vitess databases, sharding, VSchema configuration, keyspace management, or MySQL scaling issues.

Install with Tessl CLI

npx tessl i github:planetscale/database-skills --skill vitess
What are skills?

Overall
score

84%

Does it follow best practices?

Evaluation96%

1.10x

Agent success when using this skill

Validation for skill structure

SKILL.md
Review
Evals

Vitess

Vitess is a MySQL-compatible, cloud-native database system originally built at YouTube to scale MySQL. PlanetScale runs Vitess as a managed service. Core capabilities:

  • Horizontal sharding: Built-in sharding transparent to the application — no sharding logic in app code.
  • Connection pooling: VTGate multiplexes client connections, scaling concurrent connections far beyond native MySQL limits.
  • High availability: Automatic primary failure detection and repair. Resharding and data migrations with near-zero downtime.
  • Query rewriting and caching: VTGate rewrites and optimizes queries before routing to shards.
  • Schema management: Apply schema changes across all shards consistently, in the background, without disrupting workloads.
  • Materialized views and messaging: Cross-shard materialized views and publish/subscribe messaging via VStream.

Key concepts

ConceptWhat it is
KeyspaceLogical database mapping to one or more shards. Analogous to a MySQL schema.
ShardA horizontal partition of a keyspace, each backed by a separate MySQL instance.
VSchemaConfiguration defining how tables map to shards, vindex (sharding) keys, and routing rules.
VindexSharding function mapping column values to shards (hash, unicode_loose_xxhash, lookup).
VTGateStateless proxy that plans and routes queries to the correct shard(s).
Online DDLNon-blocking schema migrations. On PlanetScale, use deploy requests for production changes.

PlanetScale specifics

  • Branching: Git-like database branches for development; deploy requests for production schema changes.
  • Connections: MySQL protocol, port 3306 (direct) or 443 (serverless). SSL always required.

SQL compatibility

Vitess supports nearly all MySQL syntax — most applications work without query changes. Standard DML, DDL, joins, subqueries, CTEs (including recursive CTEs as of v21+), window functions, and common built-in functions all work as expected.

Known limitations:

  • Stored procedures / triggers / events: Not supported through VTGate.
  • LOCK TABLES / GET_LOCK: Not supported through VTGate.
  • SELECT ... FOR UPDATE: Works within a single shard; cross-shard locking is not atomic.
  • Cross-shard joins: Supported but expensive (scatter-gather). Filter by vindex column for single-shard routing.
  • Correlated subqueries: May fail or perform poorly cross-shard. Rewrite as joins when possible.
  • AUTO_INCREMENT: Sequences are per-shard. Use vindexes or app-generated IDs (UUIDs, snowflake) to avoid collisions on sharded tables.
  • Aggregations on sharded tables: GROUP BY/ORDER BY/LIMIT merge in VTGate memory. Large result sets can be slow.
  • Foreign keys: Limited support. Prefer application-level referential integrity on sharded keyspaces.

References

TopicReferenceUse for
VSchemareferences/vschema.mdVSchema design, vindexes, sequences, sharding strategies
Schema Changesreferences/schema-changes.mdOnline DDL, managed migrations, ddl strategies, migration lifecycle
VReplicationreferences/vreplication.mdMoveTables, Reshard, Materialize, VDiff, VStream
Architecturereferences/architecture.mdVTGate, VTTablet, Topology Service, VTOrc, component interactions
Query Servingreferences/query-serving.mdQuery routing, MySQL compatibility, cross-shard performance, EXPLAIN
Repository
github.com/planetscale/database-skills
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.