In this post, PalFish explains why they chose TiDB over MongoDB and MySQL. The key factors were their application requirements and their perspective on NewSQL databases.
In this article, an engineer at U-Next talks about why they chose TiDB and why they run it on the ARM architecture. He also provides detailed benchmarking results showing that TiDB runs equally well on ARM and x86.
As its business quickly grew, ZTO Express found Exadata, Kudu, and HBase couldn't meet their database requirements. They migrated from Exadata to TiDB to scale out their database and perform multi-dimensional analytics in near real time.
Xiaohongshu receives more than 100 million rows of data every day. They adopted TiDB because it supports both transactional and analytical queries, real-time data analytics, and horizontal scalability.
Zhuan Zhuan embraced TiDB 4.0's new features with great results. It's a truly HTAP database with one-minute deployment, visual troubleshooting, and reduced maintenance costs.
After trying out different database solutions, BIGO chose TiDB. In this post, a BIGO DBA talks about TiDB 4.0's new features, how they benefit BIGO's business, and BIGO's plan to use TiDB 4.0 even more in the future.