What do you like best about the product?

There are a lot of useful features. I will bring up the 4 top most useful features for us:
1. MySQL compatibility
2. Built-in high availability
3. Horizontal scaling
4. Built-in CDC (Change Data Capture)

What do you dislike about the product?

At the time this review written, TiDB lack of Postgres compatibility and not support any kind of stored procedure

What problems is the product solving and how is that benefiting you?

Our initial use case for TiDB was to handle traffic spikes in our courier system during double-date sales events.

Whenever traffic spiked, our database would struggle. We had already implemented tuning, indexing, housekeeping, and other optimizations, but they still weren’t enough. Eventually, we attempted to distribute traffic based on different regions, which worked and remained stable for several months. However, this solution became costly since we had to multiply our database instances significantly.

The main challenge for us was simulating double-date conditions with a load twice as high as our peak traffic, which caused database issues—hitting **30K QPS**.