3 ms·
Scaling horizontally or vertically, on-premise or with cloud service provider is always debatable. IMHO for the scalability topic especially in the internet i
by littlecatbird 4y ago
Scaling horizontally or vertically, on-premise or with cloud service provider is always debatable.
IMHO for the scalability topic especially in the internet industry, China or Indian companies may have more say about it thanks to the largest population.
Searching through the mentioned TiDB, it's quite interesting to find through its affiliated site https://ossinsight.io/analyze/pingcap/tidb https://ossinsight.io/analyze/pingcap/tidb, that the popularity (stargazer) seems pretty high in China.
The US stars is not bad, comparable to Mongo's.
Honestly I've not heard about it much. How much of the load these databases can support up to, with a single cluster ?
- azurezyq 4y agoaccording to https://en.pingcap.com/case-study/lesson-learned-from-queries-over-1-3-trillion-rows-of-data-within-milliseconds-of-response-time-at-zhihu/ https://en.pingcap.com/case-study/lesson-learned-from-querie..., it can store 1.3 trillion rows in a single DB. And in one use case: "in this application, data increases by 8 billion records and 1.5 TB every day."
- zzzhangjinpeng 4y ago
- jerryjerryjerry 4y agoExactly, the scalability usually comes with "population", no matter it's population of China/India, or the volume of data. Actually I did a quick research on your last question and it seems that a single cluster with NewSQL architecture has no theoretical upper bound on it (and since you mentioned TiDB, I checked its document which says "unlimited"), however, in reality I believe there is such a bound due to implementation-based limitation and/or performance concern.