G2

yugesh K.

Developer

Small-Business (50 or fewer emp.)

2/11/2026

"TiDB Delivers NoSQL-Scale with SQL Simplicity and MySQL Compatibility"

5/5

What do you like best about TiDB?

What I like best about TiDB is its ability to combine the scalability of NoSQL systems with the reliability and familiarity of traditional SQL databases. It allows me to scale horizontally without changing my application logic, which is very helpful while building growing projects. The MySQL compatibility makes integration smooth, and the distributed architecture ensures high availability and strong consistency. I also appreciate how it handles large datasets efficiently while maintaining good performance. Overall, it gives me the flexibility of a modern distributed system without sacrificing the simplicity of SQL. Review collected by and hosted on G2.com.

What do you dislike about TiDB?

One thing I dislike about TiDB is that the initial setup and configuration can feel complex, especially for beginners who are new to distributed databases. Understanding how different components like PD, TiKV, and TiDB servers work together takes time. In some cases, performance tuning and optimization also require deeper knowledge compared to traditional single-node databases. Additionally, documentation can feel overwhelming because there are many deployment and scaling options to choose from. Review collected by and hosted on G2.com.

What problems is TiDB solving and how is that benefiting you?

TiDB addresses the challenge of scaling databases without giving up SQL compatibility or consistency. In many growing projects, traditional databases can become a bottleneck as traffic rises and data volumes expand. With its distributed architecture, TiDB enables horizontal scaling while continuing to support standard SQL, so I don’t have to redesign the database layer just to keep up with growth.

In projects like Cartify, where I’m building an AI-powered ecommerce assistant with real-time product suggestions, smart cart updates, and analytics, TiDB helps me run transactional workloads and analytical queries side by side. Rather than splitting OLTP and OLAP into separate systems, I can handle both within a single, unified database, which keeps the overall architecture simpler and reduces unnecessary complexity. Review collected by and hosted on G2.com.