. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . shard resides. Keyspace Graph The keyspace graph allows Vitess to decide which set of shards to use for a given keyspace, cell, and tablet type. Partitions During horizontal resharding (splitting or databases; if you’re not using sharding, a keyspace maps directly to a MySQL database name. In either case, a keyspace appears as a single database from the standpoint of the application. Reading data from

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . as much work as possible to the underlying MySQL instances. When this is not possible, Vitess will use a plan that collects input from multiple sources and merges the results to produce the correct query Documentation • VTGate Keyspace Graph The keyspace graph allows Vitess to decide which set of shards to use for a given keyspace, cell, and tablet type. 11 Partitions During horizontal resharding (splitting

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . shard resides. Keyspace Graph The keyspace graph allows Vitess to decide which set of shards to use for a given keyspace, cell, and tablet type. Partitions During horizontal resharding (splitting or databases; if you’re not using sharding, a keyspace maps directly to a MySQL database name. In either case, a keyspace appears as a single database from the standpoint of the application. Reading data from

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Planning to use Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . table we want to shard using country. The lookup table will help us do that. Region Vindex We will use a region_json vindex to compute the keyspace_id for a customer row using the (id, country) fields.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346 Planning to use Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Planning to use Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365 Planning to use Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4 The use of unique keys 68 Which keys are eligible? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 When not to Use Auto-Increment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

able to access VTAdmin-web. In this case, the trust boundary is the local file system. 10 Vitess Security Audit, 2023 . Compromising existing app Another use case of VTAdmin-web is to integrate it into As such, users first have to authenticate by way of the existing app to access VTAdmin-web. In this case, a trust boundary exists between the internet and the existing web app: 11 Vitess Security Audit of vulnerabilities in public registries and assess whether projects use the vulnerable version. In either case, a threat actor can use a vulnerability in a 3rd-party dependency to escalate privileges and

minimal reference client https://github.com/vitessio/messages was used as additional illustration of use-cases. ▪ branch master commit 7d2ac2189573a7d26cf0f42e17df749673e3d16f ◦ The testers received unencumbered sha1(client_response ^ sha1(salt + sha1(sha1(pw))) Server compares: generated_hash == stored_hash In case the password is stored as plain-text, Vitess spares itself the final SHA1 operation on the server-side the authentication schemes mentioned above, Vitess also implements MysqlDialog, which makes use of plain-text password comparison from both the server’s and the client’s perspectives. The problem