The most upside of TiDB in my point of view is it's compatibility with MySQL , most of the MySQL syntax supported in it. So it is easy to integrate it with the existing applications and tools and easy to handle by the DBAs.

It is easy to migrate the MySQL data to the TiDB database through the migration tool TiDB DM. This makes it very feasible to implement TiDB alongside existing MySQL infrastructure with minimal disruption.

TiDB's DM feature and TiCDC are widely used features and it is frequently used where real-time analytics is needed on live transactional data.

As we know TiDB providing customer support through the active community on github and slack also provides the great documentation to understand the concepts and usage of tools to make it easy for the users. Review collected by and hosted on G2.com.

The main cons in TiDB is it's cost. In many cases, customers are cost-sensitive, and TiDB's distributed architecture while powerful may appear less appealing compared to more lightweight, single-node database solutions.

Connecting with the existing system is easy with TiDB but still the TiKV needs optimization in some situations. Review collected by and hosted on G2.com.

* TiDB gives us horizontal scale and strong consistency with familiar MySQL syntax.

* Great observability

* Core components (TiDB SQL, TiKV, PD) are extremely stable

* Easy to implement schemas as we can directly translate them from MySQL for the most part

* Nice features, such as readonly nodes, placement rules, stale reads, TTL

* Good restore features, and self healing Review collected by and hosted on G2.com.

Ecosystem is not as mature. There are not a lot of extensions, and some non-core components do not get as much attention or are not as reliable. Despite this, PingCap (the parent company) makes sure to address issues as we encounter them. Review collected by and hosted on G2.com.

TiDB perfectly meets our scalability and high availability expectations. Once properly tuned, TiDB has met our high-throughput demands without missing a beat. We’ve been able to add new TiKV nodes to absorb surges in write traffic and watched data rebalance itself. When it comes to High availability, TiDB’s multi-replica Raft setup worked great for us.

Ease of use & integration is great.

If we talk about the Frequency, we needed a database which can support 10K QPS, which was perfectly meet by TIDB Review collected by and hosted on G2.com.

Running TiDB isn’t cheap. To get real redundancy we’ve got at least five large instances, each with plenty of CPU, memory, and disk I/O. Plus you need extra storage for replicas and engineers to manage everything. All together, our cloud bill and staffing costs can add up quickly.

Ease of implementation is quite difficult as Deployment using helm is an overhead as our team isn't very strong with Kubernetes. So we had to spend some time to get things running using the binaries and docker. We created a docker-compose of our know cause the provided compose want working in my case.

Another thing to note is that the TiDB community is still quite small. When we ran into problems, there weren’t many active users or resources online to help. It made troubleshooting slower and sometimes left us waiting for answers from the customer support or the dev team. Review collected by and hosted on G2.com.

What I appreciate most about TiDB is how seamlessly it combines horizontal scalability with the simplicity of SQL. Its compatibility with MySQL made the transition effortless, and the HTAP architecture is a major advantage for managing both transactional and analytical workloads in a unified system. Additionally, the support has been outstanding—responsive, knowledgeable, and truly helpful when it counts. Review collected by and hosted on G2.com.

Although I genuinely like TiDB overall, my experience with TiCDC in production has been quite tough. Achieving stability and reliably managing edge cases has required more effort than I anticipated. The surrounding tooling for data replication and observability still feels immature and underdeveloped. That said, the progress and direction of TiCDC give me confidence that things will get better over time. However, as it stands today, TiCDC is far from developer- and deployment-friendly. Review collected by and hosted on G2.com.

I like that it’s a low effort setup, high availability and distributed database. Review collected by and hosted on G2.com.

It has quite a few of parameters that make it complicated, at least for the self hosted version. Review collected by and hosted on G2.com.

* Horizontally scalable SQL database: TiDB's architecture eliminates concerns about supporting ever-growing traffic. Scaling a TiDB cluster up and down is straightforward, to meet workload demands and improve efficiency.

* Online data schema migration: Schema migration is painless. When combining with the resource control, it eliminates the major pain points of downtime and disruption to production traffic.

* Comprehensive suite of tools: TiDB provides a suite of invaluable tools that make troubleshooting and mitigating production issues easy, ensuring that the system runs smoothly.

* Compatibility with MySQL: This feature makes migration from MySQL possible.

* Top-notch supports: PingCap business support adds a crucial layer of assurance, making TiDB a reliable and trustworthy system for mission critical workload. Review collected by and hosted on G2.com.

* Niche features are less reliable: Generated column is less reliable than its MySQL equivalent, leading to several production incidents. Review collected by and hosted on G2.com.

What I like best about TiDB is how it brings together horizontal scalability and the ease of SQL with minimal friction. The MySQL compatibility made adoption smooth, and the HTAP architecture is a big plus for handling both transactional and analytical workloads without splitting systems. On top of that, the support has been great, responsive, knowledgeable, and genuinely helpful when it matters. Review collected by and hosted on G2.com.

While I really like TiDB overall, I’ve had a rough time with TiCDC in production. Getting it stable and handling edge cases reliably has taken more effort than expected. Some of the tooling around data replication and observability still feels like it needs more maturity. That said, the direction it's heading in gives me confidence things will improve. But now it is not at all dev-friendly and deployment friendly atleast the TiCDC part of it. Review collected by and hosted on G2.com.

What I like most about TiDB is its horizontal scalability and MySQL compatibility. It allows seamless scaling without requiring major changes to application code, which is extremely valuable as data grows. The support for distributed transactions and high availability makes it well-suited for online transactional workloads. I also appreciate the HTAP (Hybrid Transactional/Analytical Processing) capability, which enables us to handle both OLTP and OLAP scenarios in a single platform. Review collected by and hosted on G2.com.

TiDB tends to consume more system resources, and its performance might not be optimal for smaller deployments. Although it's MySQL-compatible, there are still some inconsistencies in SQL support or function behavior, which requires extra testing and adjustments. Additionally, while the documentation is extensive, it can be a bit fragmented for advanced topics like performance tuning and cluster monitoring, making the learning curve steeper for new users. Review collected by and hosted on G2.com.

they boast a lot about latency, scale and clients like global giants such as flipkart. tbh, we never reached such scale hence it was overkill and supabase even thought costly gave clarity there Review collected by and hosted on G2.com.

not merged with vibe code stack natively and not so LLM friendly.

plus point for easy migration just via following chatgpt, me & wandering in internet but still an overkill if you don't bother much about latency etc Review collected by and hosted on G2.com.

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) Review collected by and hosted on G2.com.

At the time this review written, TiDB lack of Postgres compatibility and not support any kind of stored procedure Review collected by and hosted on G2.com.