Embracing NewSQL: Why We Chose TiDB Over MongoDB and MySQL

4 years ago dzone.com

Summary: This is a summary of an article originally published by the source. Read the full original article here →

As of October 2020, PalFish has over 40 million users, of which more than 2 million are paid users.

Three months went by, and TiDB worked almost flawlessly, so we read and wrote to TiDB synchronously, while we wrote to MongoDB asynchronously.

Here, I'd like to share two typical scenarios of TiDB in PalFish: the online class data storage and the trading system.

As we deepened our knowledge of TiDB, and with the support of the PingCAP team, we got better at managing TiDB and successfully resolved the data replication problem.

DevOps Articles