services. • about 8w line(test code exclude) • client(bson SSL) java/python/go Golang ? • minimalist • goroutines • channels & selects • closures • defers • generics • GC • map, slices • performace

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Design Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Design Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Design Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Design Docs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

shard. The global topology is used for some operations, including reparenting and resharding. By design, the global topology service is not used a lot. In order to survive any single cell going down, authors and reviewers need to answer these general questions: • Does this change match an existing design / bug? • Is there proper unit test coverage for this change? All changes should increase coverage shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended to design the VSchema in such a way that cross- shard modifications are not required. OLAP Workload By default

shard. The global topology is used for some operations, including reparenting and resharding. By design, the global topology service is not used a lot. In order to survive any single cell going down, authors and reviewers need to answer these general questions: • Does this change match an existing design / bug? • Is there proper unit test coverage for this change? All changes should increase coverage shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended to design the VSchema in such a way that cross- shard modifications are not required. OLAP Workload By default

shard. The global topology is used for some operations, including reparenting and resharding. By design, the global topology service is not used a lot. In order to survive any single cell going down, base can be prevented. Some additional points to keep in mind: * Does this change match an existing design / bug? * Is this change going to log too much? (Error logs should only happen when the component warning >}} Transaction commit is much slower when using 2PC. The authors of Vitess recommend that you design your VSchema so that cross-shard updates (and 2PC) are not required. {{< /warning >}} Vitess 2PC

shard. The global topology is used for some operations, including reparenting and resharding. By design, the global topology service is not used a lot. In order to survive any single cell going down, authors and reviewers need to answer these general questions: • Does this change match an existing design / bug? • Is there proper unit test coverage for this change? All changes should increase coverage warning >}} Transaction commit is much slower when using 2PC. The authors of Vitess recommend that you design your VSchema so that cross-shard updates (and 2PC) are not required. {{< /warning >}} Vitess 2PC

related to VTAdmins default settings. Missing authentication is a security issue related to VTAdmins design. We understand from internal discussions during the audit that Vitess wishes to allow as flexible counter-productive to. However, from the perspective of security, we recommend an authentication-by-default design that can be removed from deployments. 28 Vitess Security Audit, 2023 ADA-VIT-SA23-7: Critical compliance review. Our overall assessment of VTAdmin is highly positive. VTAdmin follows secure design and code practices, and VTAdmin-web is written with React which is hardened to defend against many