auto-failover • row-cache • limit inefficiency SQL • more client connection • replication lag optimization • multi data center Vitess Topo Vitess concepts • keyspace/keyspaceId • vtctl • vttablet

high QPS queries to be sent to all shards. • Lookup Unique Unowned: This category is used as an optimization as described in the Shared Vindexes section. • Lookup NonUnique Owned: This gets used for high are returned in Field message responses from MySQL, i.e. field name, table name, etc. This is an optimization for high-QPS queries where the client knows what it’s getting Enums ExecuteOptions.IncludedFields

are returned in Field message responses from MySQL, i.e. field name, table name, etc. This is an optimization for high-QPS queries where the client knows what it’s getting Enums ExecuteOptions.IncludedFields high QPS queries to be sent to all shards. • Lookup Unique Unowned: This category is used as an optimization as described in the Shared Vindexes section. • Lookup NonUnique Owned: This gets used for high

lookup table is amortized as the number of shards grow. • Lookup Unique Unowned: Can be used as an optimization as described in the Shared Vindexes section. • Lookup NonUnique Owned: Used for high QPS queries possible inconsistency, potentially with a retry, or some more elaborate mechanism. Notes • As an optimization Phase 1+2 are performed at the same time, see below. • Because parts of this proceeds serially specify the list of columns along with their types for every table. This allows Vitess to make optimization decisions where necessary. For example, specifying that a column contains numeric data allows

lookup table is amortized as the number of shards grow. • Lookup Unique Unowned: Can be used as an optimization as described in the Shared Vindexes section. • Lookup NonUnique Owned: Used for high QPS queries specify the list of columns along with their types for every table. This allows Vitess to make optimization decisions where necessary. 396 For example, specifying that a column contains text allows VTGate

lookup table is amortized as the number of shards grow. • Lookup Unique Unowned: Can be used as an optimization as described in the Shared Vindexes section. • Lookup NonUnique Owned: Used for high QPS queries specify the list of columns along with their types for every table. This allows Vitess to make optimization decisions where necessary. For example, specifying that a column contains numeric data allows

lookup table is amortized as the number of shards grow. • Lookup Unique Unowned: Can be used as an optimization as described in the Shared Vindexes section. • Lookup NonUnique Owned: Used for high QPS queries specify the list of columns along with their types for every table. This allows Vitess to make optimization decisions where necessary. 433 For example, specifying that a column contains numeric data allows

high QPS queries to be sent to all shards. • Lookup Unique Unowned: This category is used as an optimization as described in the Shared Vindexes section. • Lookup NonUnique Owned: This gets used for high

lookup table is amortized as the number of shards grow. • Lookup Unique Unowned: Can be used as an optimization as described in the Shared Vindexes section. • Lookup NonUnique Owned: Used for high QPS queries