against externally managed databases like RDS and CloudSQL. Such users are reluctant to pay the latency cost of the extra hop. VTDirect is the ability of VTGate to directly send queries to the mysql instances transactions that give you distributed atomic guarantees. However, choosing this option increases the write cost by approximately 50%. Single shard transactions continue to remain ACID, just like MySQL supports is one case that is not addressed by Vitess. The current recommen- dation is to absorb the latency cost of long-distance round-trips for writes. If the data distribution allows, you still have the option

against externally managed databases like RDS and CloudSQL. Such users are reluctant to pay the latency cost of the extra hop. VTDirect is the ability of VTGate to directly send queries to the mysql instances transactions that give you distributed atomic guarantees. However, choosing this option increases the write cost by approximately 50%. 95 Single shard transactions continue to remain ACID, just like MySQL supports is one case that is not addressed by Vitess. The current recommen- dation is to absorb the latency cost of long-distance round-trips for writes. If the data distribution allows, you still have the option

against externally managed databases like RDS and CloudSQL. Such users are reluctant to pay the latency cost of the extra hop. VTDirect is the ability of VTGate to directly send queries to the mysql instances transactions that give you distributed atomic guarantees. However, choosing this option increases the write cost by approximately 50%. Single shard transactions continue to remain ACID, just like MySQL supports is one case that is not addressed by Vitess. The current recommen- dation is to absorb the latency cost of long-distance round-trips for writes. If the data distribution allows, you still have the option

transactions that give you distributed atomic guarantees. However, choosing this option increases the write cost by approximately 50%. Single shard transactions continue to remain ACID, just like MySQL supports is one case that is not addressed by Vitess. The current recommen- dation is to absorb the latency cost of long-distance round-trips for writes. If the data distribution allows, you still have the option master in another cell. vtgate will just route the traffic to the right place, incurring extra latency cost only on the remote access. For instance, creating U.S. user records in a database with masters in

against externally managed databases like RDS and CloudSQL. Such users are reluctant to pay the latency cost of the extra hop. VTDirect is the ability of VTGate to directly send queries to the mysql instances transactions that give you distributed atomic guarantees. However, choosing this option increases the write cost by approximately 50%. Single shard transactions continue to remain ACID, just like MySQL supports is one case that is not addressed by Vitess. The current recommen- dation is to absorb the latency cost of long-distance round-trips for writes. If the data distribution allows, you still have the option

transactions that give you distributed atomic guarantees. However, choosing this option increases the write cost by approximately 50%. Single shard transactions continue to remain ACID, just like MySQL supports is one case that is not addressed by Vitess. The current recommen- dation is to absorb the latency cost of long-distance round-trips for writes. If the data distribution allows, you still have the option master in another cell. vtgate will just route the traffic to the right place, incurring extra latency cost only on the remote access. For instance, creating U.S. user records in a database with masters in

transactions that give you distributed atomic guarantees. However, choosing this option increases the write cost by approximately 50%. Single shard transactions continue to remain ACID, just like MySQL supports is one case that is not addressed by Vitess. The current recommen- dation is to absorb the latency cost of long-distance round-trips for writes. If the data distribution allows, you still have the option master in another cell. vtgate will just route the traffic to the right place, incurring extra latency cost only on the remote access. For instance, creating U.S. user records in a database with masters in

transactions that give you distributed atomic guarantees. However, choosing this option increases the write cost by approximately 50%. Single shard transactions continue to remain ACID, just like MySQL supports is one case that is not addressed by Vitess. The current recommen- dation is to absorb the latency cost of long-distance round-trips for writes. If the data distribution allows, you still have the option master in another cell. vtgate will just route the traffic to the right place, incurring extra latency cost only on the remote access. For instance, creating U.S. user records in a database with masters in