What is a data topology?

Neki, PlanetScale’s PostgreSQL-native sharding architecture inspired by lessons from Vitess, uses a data topology to map logical database tables onto physical shards and route queries without requiring applications to track data locations. Defined as JSON, a topology combines shard indexes, which convert shard-key values through hash, modulo, or range strategies; shard groups, which assign routing-key ranges to physical shards and support colocating related tables; and database bindings that apply shard-group defaults across PostgreSQL databases, schemas, and tables. Physical shards, each comprising a PostgreSQL primary and replicas, are provisioned separately and referenced through stable IDs, while an authoritative single-shard group stores database-wide metadata such as schemas and sequences. In an example store database, customer IDs are transformed into routing keys and directed to one of two shards according to configured ranges. The topology acts as a live routing configuration that can be updated during resharding, table moves, and imports while applications continue operating.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.