mysql Beyond these features, componentizing TabletServer will make the vitess architecture more flexible. There are many places in the code where we instantiate a QueryService. All those places can now good opportunity for us to come up with better names. Since the config option is more powerful and flexible, specifying that file in the command line will supersede all legacy flags. Other options considered docker_vttestserver This creates 2 docker images named vitess/vttestserver:mysql57 and vitess/vttestserver:mysql80 2. Pulling from docker hub Alternately, you can get the latest docker images from the docker hub. In your

mysql Beyond these features, componentizing TabletServer will make the vitess architecture more flexible. There are many places in the code where we instantiate a QueryService. All those places can now good opportunity for us to come up with better names. Since the config option is more powerful and flexible, specifying that file in the command line will supersede all legacy flags. Other options considered docker_vttestserver This creates 2 docker images named vitess/vttestserver:mysql57 and vitess/vttestserver:mysql80 2. Pulling from docker hub Alternately, you can get the latest docker images from the docker hub. In your

mysql Beyond these features, componentizing TabletServer will make the vitess architecture more flexible. There are many places in the code where we instantiate a QueryService. All those places can now good opportunity for us to come up with better names. Since the config option is more powerful and flexible, specifying that file in the command line will supersede all legacy flags. Other options considered Creating a message table The current implementation requires a fixed schema. This will be made more flexible in the future. There will also be a custom DDL syntax. For now, a message table must be created

mysql Beyond these features, componentizing TabletServer will make the vitess architecture more flexible. There are many places in the code where we instantiate a QueryService. All those places can now good opportunity for us to come up with better names. Since the config option is more powerful and flexible, specifying that file in the command line will supersede all legacy flags. Other options considered Creating a message table The current implementation requires a fixed schema. This will be made more flexible in the future. There will also be a custom DDL syntax. For now, a message table must be created

Creating a message table The current implementation requires a fixed schema. This will be made more flexible in the future. There will also be a custom DDL syntax. For now, a message table must be created previously known limitations, but have since been supported and are awaiting further documentation. • Flexible columns: Allow any number of application defined columns to be in the message table. • No ACL check embarking on a major migration of the MySQL infrastructure at the core of our service to use Vitess’ flexible sharding and management instead of our simple application-based shard routing and manual administration

Creating a message table The current implementation requires a fixed schema. This will be made more flexible in the future. There will also be a custom DDL syntax. For now, a message table must be created previously known limitations, but have since been supported and are awaiting further documentation. • Flexible columns: Allow any number of application defined columns to be in the message table. • No ACL check embarking on a major migration of the MySQL infrastructure at the core of our service to use Vitess’ flexible sharding and management instead of our simple application-based shard routing and manual administration

Creating a message table The current implementation requires a fixed schema. This will be made more flexible in the future. There will also be a custom DDL syntax. For now, a message table must be created previously known limitations, but have since been supported and are awaiting further documentation. • Flexible columns: Allow any number of application defined columns to be in the message table. • No ACL check embarking on a major migration of the MySQL infrastructure at the core of our service to use Vitess’ flexible sharding and management instead of our simple application-based shard routing and manual administration

Creating a message table The current implementation requires a fixed schema. This will be made more flexible in the future. There will also be a custom DDL syntax. For now, a message table must be created previously known limitations, but have since been supported and are awaiting further documentation. • Flexible columns: Allow any number of application defined columns to be in the message table. • No ACL check embarking on a major migration of the MySQL infrastructure at the core of our service to use Vitess’ flexible sharding and management instead of our simple application-based shard routing and manual administration

design. We understand from internal discussions during the audit that Vitess wishes to allow as flexible a usage of the web ui as possible which authentication-by-default is counter-productive to. However

and deployed; one type concerned simple 3-tablet versions that were crafted via the provided docker images, another type was built along the lines of the minikube-instructions. This was done to gain better