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 Go. We love it for its simplicity (e.g. compared to C++ or Java) and performance (e.g. compared to Python). Contributing to our server code will require you to learn Go. We recommend that you follow the which requires additional dependencies. • Vitess currently has some additional tests written in Python, but we will be skipping this step for simplicity. Disable SELinux SELinux will not allow Vitess

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 Go. We love it for its simplicity (e.g. compared to C++ or Java) and performance (e.g. compared to Python). Contributing to our server code will require you to learn Go. We recommend that you follow the which requires additional dependencies. • Vitess currently has some additional tests written in Python, but we will be skipping this step for simplicity. Disable SELinux SELinux will not allow Vitess

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 Go. We love it for its simplicity (e.g. compared to C++ or Java) and performance (e.g. compared to Python). Contributing to our server code will require you to learn Go. We recommend that you follow the which requires additional dependencies. • Vitess currently has some additional tests written in Python, but we will be skipping this step for simplicity. 18 Disable SELinux SELinux will not allow Vitess

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 Go. We love it for its simplicity (e.g. compared to C++ or Java) and performance (e.g. compared to Python). Contributing to our server code will require you to learn Go. We recommend that you follow the

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 Go. We love it for its simplicity (e.g. compared to C++ or Java) and performance (e.g. compared to Python). Contributing to our server code will require you to learn Go. We recommend that you follow the

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 Go. We love it for its simplicity (e.g. compared to C++ or Java) and performance (e.g. compared to Python). Contributing to our server code will require you to learn Go. We recommend that you follow the

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 Go. We love it for its simplicity (e.g. compared to C++ or Java) and performance (e.g. compared to Python). Contributing to our server code will require you to learn Go. We recommend that you follow the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

databases for large scale web services. • about 8w line(test code exclude) • client(bson SSL) java/python/go Golang ? • minimalist • goroutines • channels & selects • closures • defers • generics vtprimecache Vitess concepts • keyspaceId • unique Index • Non-unique Index • second index support Select only • How to find shards by keyspaceId ? vindex hash lookup numeric Configure Server

team as well as Chris Aniszczyk of The Linux Foundation, for their excellent project coordination, support and assistance, both before and during this assignment. Special gratitude also needs to be extended