Re:We Chose a Distributed SQL Database to Complement MySQL
by qaq on Saturday August 29, 2020 @04:26PM
(#24319184)
Thanx for the detailed resp. Just to clarify TiDB uses 2pc too for cross region transactions from what I remember?
Re:We Chose a Distributed SQL Database to Complement MySQL
by gregwebs on Saturday August 29, 2020 @04:45PM
(#24319300)
Yes, it is a form of 2PC that happens transparently during normal transactions. It is designed to perform well for production workloads whereas Vitess now has 2PC but warns against using it and requires configuration changes to enable it.
Re:We Chose a Distributed SQL Database to Complement MySQL
by mmerlin on Saturday August 29, 2020 @06:06PM
(#24319753)
2PC =
two-phase commit
https://en.m.wikipedia.org/wiki/Two-phase_commit_protocol
For anyone like me whose neural net had a cache miss due to lack of caffeine activation function ;)
Vitess is a MySQL sharding system. In this article they stated that it was too difficult to query across shards in their existing setup. Switching to Vitess from their existing sharding system (assuming they were using something else) might have helped them for some of their queries. However, Vitess doesn't support cross shard transactions for production workloads. TiDB doesn't have these sharding limitations.