TechPlanetScaleabout 2 years ago
Achieving data consistency with the consistent lookup Vindex
8 min read
Vitess uses Vindexes to associate rows with a Keyspace ID for shard routing. The consistent lookup Vindex as a Secondary Vindex directs Select/Update/Delete queries to the correct shard without scatter-gather operations. A global index table maintains the mapping for efficient query routing.
Level
Hype check
Tap to vote and see what everyone thinks.