3 ms·
“Infinite horizontal scalability”. Yeah, no. There’s coordination overhead for adding more nodes. It needs to have an upper bound. It may be a high upper bo
by thanatos_dem 8y ago
“Infinite horizontal scalability”. Yeah, no. There’s coordination overhead for adding more nodes. It needs to have an upper bound. It may be a high upper bound, but infinite is straight up impossible.
It may seem trivial, but claims like that are why I prefer CockroachDB when it comes to NewSQL systems. They’re at least very upfront with its compromises and areas needing improvement.
I’ve never see anything from Pingcap explaining the compromises that the DB makes. A “when should you not use this” type overview, and to me those are the most important things when deciding on a technology.
It may be good technology, but it’s marketed like modern day snake oil.
- morgo 8y agoUpdate: The documentation has now been updated https://github.com/pingcap/tidb/pull/9144 https://github.com/pingcap/tidb/pull/9144
- morgo 8y agoMorgan from the TiDB team here. Thank you for the feedback, and I agree with you. We actually took this line out from the same copy in the docs: https://pingcap.com/docs/ https://pingcap.com/docs/ (We must have missed a spot, and I will follow up and make sure it is addressed). We try to be transparent about the differences from MySQL. On the compatibility page, there are a few cases described such as large transactions, small transactions and single threaded workloads: https://www.pingcap.com/docs/sql/mysql-compatibility/ https://www.pingcap.com/docs/sql/mysql-compatibility/