Transport When using gRPC transport, Vitess can use the usual TLS security features (familiarity with SSL / TLS is necessary here): • Any Vitess server can be configured to use TLS with the following command clients should have different access to Vitess tables. Caller ID Override In a private network, where SSL security is not required, it might still be desirable to use table ACLs as a safety mechanism to prevent connect with SSL. It also exercises the grpc_use_effective_callerid flag, by connecting without SSL. MySQL Transport To get vtgate to support SSL/TLS use -mysql_server_ssl_cert and -mysql_server_ssl_key. To

VTGate to support TLS use the -mysql_server_ssl_cert and -mysql_server_ssl_key VTGate options. To require client certificates, you can set -mysql_server_ssl_ca, containing the CA certificate you expect configure VTGate to support TLS set -mysql_server_ssl_cert and -mysql_server_ssl_key. Client certificates can also be mandated by setting -mysql_server_ssl_ca. If there is no CA specified then TLS is optional no timeout) db_dba_password string db dba password db_dba_use_ssl boolean Set this flag to false to make the dba connection to not use ssl (default true) db_dba_user string db dba user userKey (default

db_charset flags: 0 # db_flags flavor: # db_flavor sslCa: # db_ssl_ca sslCaPath: # db_ssl_ca_path sslCert: # db_ssl_cert sslKey: # db_ssl_key serverName: # db_server_name connectTimeoutMilliseconds: db_app_password useSsl: true # db_app_use_ssl preferSocket: true dba: user: vt_dba # db_dba_user password: # db_dba_password useSsl: true # db_dba_use_ssl preferSocket: true filtered: user: vt_filtered db_filtered_password useSsl: true # db_filtered_use_ssl preferSocket: true repl: user: vt_repl # db_repl_user password: # db_repl_password useSsl: true # db_repl_use_ssl preferSocket: true appdebug: user: vt_appdebug

db_charset flags: 0 # db_flags flavor: # db_flavor sslCa: # db_ssl_ca sslCaPath: # db_ssl_ca_path sslCert: # db_ssl_cert sslKey: # db_ssl_key serverName: # db_server_name connectTimeoutMilliseconds: db_app_password useSsl: true # db_app_use_ssl preferSocket: true dba: user: vt_dba # db_dba_user password: # db_dba_password useSsl: true # db_dba_use_ssl preferSocket: true filtered: user: vt_filtered db_filtered_password useSsl: true # db_filtered_use_ssl preferSocket: true repl: user: vt_repl # db_repl_user password: # db_repl_password useSsl: true # db_repl_use_ssl preferSocket: true appdebug: user: vt_appdebug

db_charset flags: 0 # db_flags flavor: # db_flavor sslCa: # db_ssl_ca sslCaPath: # db_ssl_ca_path sslCert: # db_ssl_cert sslKey: # db_ssl_key serverName: # db_server_name connectTimeoutMilliseconds: db_app_password useSsl: true # db_app_use_ssl preferSocket: true dba: user: vt_dba # db_dba_user password: # db_dba_password useSsl: true # db_dba_use_ssl preferSocket: true filtered: user: vt_filtered db_filtered_password useSsl: true # db_filtered_use_ssl preferSocket: true repl: user: vt_repl # db_repl_user password: # db_repl_password useSsl: true # db_repl_use_ssl preferSocket: true appdebug: user: vt_appdebug

db_charset flags: 0 # db_flags flavor: # db_flavor sslCa: # db_ssl_ca sslCaPath: # db_ssl_ca_path sslCert: # db_ssl_cert sslKey: # db_ssl_key serverName: # db_server_name connectTimeoutMilliseconds: db_app_password useSsl: true # db_app_use_ssl preferSocket: true dba: user: vt_dba # db_dba_user password: # db_dba_password useSsl: true # db_dba_use_ssl preferSocket: true filtered: user: vt_filtered db_filtered_password useSsl: true # db_filtered_use_ssl preferSocket: true repl: user: vt_repl # db_repl_user password: # db_repl_password useSsl: true # db_repl_use_ssl preferSocket: true appdebug: user: vt_appdebug

configure VTGate to support TLS set -mysql_server_ssl_cert and -mysql_server_ssl_key. Client certificates can also be mandated by setting -mysql_server_ssl_ca. If there is no CA specified then TLS is optional Transport When using gRPC transport, Vitess can use the usual TLS security features (familiarity with SSL / TLS is necessary here): • Any Vitess server can be configured to use TLS with the following command clients should have different access to Vitess tables. Caller ID Override In a private network, where SSL security is not required, it might still be desirable to use table ACLs as a safety mechanism to prevent

configure VTGate to support TLS set -mysql_server_ssl_cert and -mysql_server_ssl_key. Client certificates can also be mandated by setting -mysql_server_ssl_ca. If there is no CA specified then TLS is optional Transport When using gRPC transport, Vitess can use the usual TLS security features (familiarity with SSL / TLS is necessary here): • Any Vitess server can be configured to use TLS with the following command clients should have different access to Vitess tables. Caller ID Override In a private network, where SSL security is not required, it might still be desirable to use table ACLs as a safety mechanism to prevent

MySQL 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