back to the client. It speaks both the MySQL Protocol and the Vitess gRPC protocol. Thus, your applications can connect to VTGate as if it is a MySQL Server. When routing queries to the appropriate VTTablet failover to a new master within seconds of failure detection. This is usually sufficient for most applications. • Low-latency geographically distributed writes: This is one case that is not addressed by Vitess Vitess supports transactions. NoSQL solutions have custom APIs, leading to custom architectures, applications, and tools. Vitess adds very little variance to MySQL, a database that most people are already

back to the client. It speaks both the MySQL Protocol and the Vitess gRPC protocol. Thus, your applications can connect to VTGate as if it is a MySQL Server. When routing queries to the appropriate VTTablet failover to a new master within seconds of failure detection. This is usually sufficient for most applications. • Low-latency geographically distributed writes: This is one case that is not addressed by Vitess Vitess supports transactions. NoSQL solutions have custom APIs, leading to custom architectures, applications, and tools. Vitess adds very little variance to MySQL, a database that most people are already

Vitess, and reserved connections can’t be pooled, so this should not be the normal way to run applications on Vitess. Just make sure that the global variable is set to the same value the application will back to the client. It speaks both the MySQL Protocol and the Vitess gRPC protocol. Thus, your applications can connect to VTGate as if it is a MySQL Server. When routing queries to the appropriate VTTablet failover to a new master within seconds of failure detection. This is usually sufficient for most applications. • Low-latency geographically distributed writes: This is one case that is not addressed by Vitess

Vitess, and reserved connections can’t be pooled, so this should not be the normal way to run applications on Vitess. Just make sure that the global variable is set to the same value the application will back to the client. It speaks both the MySQL Protocol and the Vitess gRPC protocol. Thus, your applications can connect to VTGate as if it is a MySQL Server. When routing queries to the appropriate VTTablet Supporting the advisory locking functions in MySQL is important, given that they are used by common applications and frameworks. Functions covered • GET_LOCK() • IS_FREE_LOCK() • IS_USED_LOCK() • RELEASE_ALL_LOCKS()

Vitess, and reserved connections can’t be pooled, so this should not be the normal way to run applications on Vitess. Just make sure that the global variable is set to the same value the application will back to the client. It speaks both the MySQL Protocol and the Vitess gRPC protocol. Thus, your applications can connect to VTGate as if it is a MySQL Server. When routing queries to the appropriate VTTablet Supporting the advisory locking functions in MySQL is important, given that they are used by common applications and frameworks. 46 Functions covered • GET_LOCK() • IS_FREE_LOCK() • IS_USED_LOCK() • RELEASE_ALL_LOCKS()

Vitess, and reserved connections can’t be pooled, so this should not be the normal way to run applications on Vitess. Just make sure that the global variable is set to the same value the application will back to the client. It speaks both the MySQL Protocol and the Vitess gRPC protocol. Thus, your applications can connect to VTGate as if it is a MySQL Server. When routing queries to the appropriate VTTablet Supporting the advisory locking functions in MySQL is important, given that they are used by common applications and frameworks. Functions covered • GET_LOCK() • IS_FREE_LOCK() • IS_USED_LOCK() • RELEASE_ALL_LOCKS()

Vitess, and reserved connections can’t be pooled, so this should not be the normal way to run applications on Vitess. Just make sure that the global variable is set to the same value the application will back to the client. It speaks both the MySQL Protocol and the Vitess gRPC protocol. Thus, your applications can connect to VTGate as if it is a MySQL Server. When routing queries to the appropriate VTTablet Supporting the advisory locking functions in MySQL is important, given that they are used by common applications and frameworks. Functions covered • GET_LOCK() • IS_FREE_LOCK() • IS_USED_LOCK() • RELEASE_ALL_LOCKS()

mechanisms · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 139 4.1.3 The way applications interact with TiDB· · · · · · · · · · · · · · · · · · · · · · · · · · 140 4.1.4 Read More· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 143 4.3 Example Applications · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1394 12.5.2 Best Practices for Developing Java Applications with TiDB · · · · · · · · · · 1401 12.5.3 Best Practices for Using HAProxy in TiDB· · · · · ·

mechanisms · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 132 4.1.3 The way applications interact with TiDB· · · · · · · · · · · · · · · · · · · · · · · · · · 133 4.1.4 Read more· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 136 3 4.3 Example Applications · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1676 12.5.2 Best Practices for Developing Java Applications with TiDB · · · · · · · · · · 1683 12.5.3 Best Practices for Using HAProxy in TiDB· · · · · ·

mechanisms · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 126 4.1.3 The way applications interact with TiDB· · · · · · · · · · · · · · · · · · · · · · · · · · 126 4.1.4 Read more· · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 130 3 4.3 Example Applications · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · · 1786 12.5.2 Best Practices for Developing Java Applications with TiDB · · · · · · · · · · 1793 12.5.3 Best Practices for Using HAProxy in TiDB· · · · · ·