NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp store topology data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent IS_USED_LOCK() • RELEASE_ALL_LOCKS() • RELEASE_LOCK() Restrictions Vitess will initially only support locking functions with these limitations: * Can only be used in SELECT queries * The queries can

NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp store topology data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent as MASTER reads. However, you get REPEATABLE_READ consistency and ACID writes for a single shard. Support is underway for cross-shard Atomic transactions. As for atomicity, the following levels are supported:

NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp store topology data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent IS_USED_LOCK() • RELEASE_ALL_LOCKS() • RELEASE_LOCK() Restrictions Vitess will initially only support locking functions with these limitations: • Can only be used in SELECT queries • The queries can

NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp store topology data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent IS_USED_LOCK() • RELEASE_ALL_LOCKS() • RELEASE_LOCK() Restrictions Vitess will initially only support locking functions with these limitations: • Can only be used in SELECT queries • The queries can

store topology data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent working on fixing this in issue #5411, but also depend on etcd-operator which will require changes to support these newer versions. {{< /warning >}} Prerequisites Before we get started, let’s get a few things for them? • Cardinality of the column; it must be high. • Do we want some rows to live together to support in-shard joins? • Do we want certain rows that will be in the same transaction to live together?

store topology data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent as MASTER reads. However, you get REPEATABLE_READ consistency and ACID writes for a single shard. Support is underway for cross-shard Atomic transactions. As for atomicity, the following levels are supported: effort commit. • TWOPC: multi-db transactions with 2PC commit. 37 No multi-master Vitess doesn’t support multi-master setup. It has alternate ways of addressing most of the use cases that are typically

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Character set support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NoOp default_storage_engine NoOp default_tmp_storage_engine NoOp innodb_strict_mode NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp store topology data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent

store topology data and provide a distributed locking service. Vitess uses a plug-in system to support various backends for storing topology data, which are assumed to provide a distributed, consistent as MASTER reads. However, you get REPEATABLE_READ consistency and ACID writes for a single shard. Support is underway for cross-shard Atomic transactions. As for atomicity, the following levels are supported: best effort commit. • TWOPC: multi-db transactions with 2PC commit. No multi-master Vitess doesn’t support multi-master setup. It has alternate ways of addressing most of the use cases that are typically

sum(price) as amount from order select * from merchant where in_keyrange( mname, ‘unicode_loose_md5’, ‘-80’) Questions? ● Sign into slack channel at vitess.io ● Try bringing up a cluster

pid, sum(price) as amount from orders select * from orders where in_keyrange( mname, ‘unicode_loose_md5’, ‘-80’) 46 VITESS.IO Materializ ed Views Use Cases Real- Time Rollups Reshardi