TiDB Cloud
PingCAPReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
76 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Scalable and Reliable, but with a Learning Curve
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
TiDB has solved several critical problems:
Scalability bottlenecks from traditional single-node databases
Operational complexity of managing multiple systems for OLTP and OLAP
Downtime risks during scaling or failover
The main benefit is that it simplifies infrastructure while providing stable, high-performance services even under heavy loads. This helps reduce maintenance costs, improves development agility, and ensures better service continuity for end users.
Scalability bottlenecks from traditional single-node databases
Operational complexity of managing multiple systems for OLTP and OLAP
Downtime risks during scaling or failover
The main benefit is that it simplifies infrastructure while providing stable, high-performance services even under heavy loads. This helps reduce maintenance costs, improves development agility, and ensures better service continuity for end users.
A powerful, scalable, and MySQL-compatible distributed database
What do you like best about the product?
TiDB seamlessly combines the best of both OLTP and OLAP, allowing real-time analytics on live transactional data without ETL. Its MySQL compatibility makes migration extremely smooth, and the horizontal scalability ensures performance under high workloads. The HTAP architecture is a game-changer for businesses requiring both operational and analytical capabilities in one system. The community is active, the documentation is well-written, and tools like TiUP simplify deployment and upgrades.
What do you dislike about the product?
While TiDB is powerful, the learning curve can be a bit steep for teams unfamiliar with distributed systems. Proper configuration and tuning are essential to achieve optimal performance, especially for complex workloads. Also, while the ecosystem is growing, some third-party tool integrations still lag behind those of more established databases. However, the team is actively improving these aspects.
What problems is the product solving and how is that benefiting you?
We use TiDB to replace traditional MySQL clusters that struggled with scaling and analytical performance. TiDB’s HTAP architecture allows us to run complex analytical queries on fresh transactional data without impacting our online services. This helps us consolidate our data infrastructure and reduces latency in business decision-making.
TiDB for large scale databases
What do you like best about the product?
TiDB really helps me as a DBA when running large databases, both in size and QPS. Since it's distributed it's easy to scale out horizontally when growth presents itself. It also has many operations-friendly features like Online DDL, TTL, automatic sharding, etc. that removes many of the pain point of running traditional MySQL in large setups. Documentation is really good and it's fairly easy to get started and migrate workloads from traditional MySQL.
What do you dislike about the product?
The downsides are it's a more complex piece of software so harder to learn, perf tune and become a real expert on it. Since it's also much newer, it still has some bugs/missing features that need to be fixed/implemented.
What problems is the product solving and how is that benefiting you?
DBA operations at large scale
My Experiences with TiDB
What do you like best about the product?
TiDB shines when you want MySQL-like simplicity with cloud-scale architecture. It’s ideal for scalable, real-time workloads that combine OLTP and OLAP. Further, i would like to add that TiDB MySQL-compatible interface makes onboarding and usage piece of cake. Most SQL tools and skills translate directly. TiDB’s deployment with tools like tiup straightforward since it easy to implement as it is well documented. PingCAP provides strong support, and their GitHub community and slack forums are active providing support for most of the common issues. TiDB is best fit for high availability and horizontal scalability. Features like horizontal scaling, HTAP (Hybrid Transactional and Analytical Processing), and automatic sharding are extremely powerful. TiDB integrates with tools like Debezium, Kafka, and Grafana. TiCDC (change data capture) is also a strong asset. In the end i would like to add TiDB offers MySQL-compatible, scalable, HTAP capabilities, great integration, and cloud-native design
What do you dislike about the product?
While using the TiDB for the first time i felt that it comes with a steep learning curve for managing its distributed architecture and some feature caveats in MySQL compatibility. While SQL usage is simple, understanding the internal architecture (TiKV, PD, TiFlash, etc.) can be complex and has a learning curve.
For advanced setups (multi-region, disaster recovery), the complexity increases rapidly and requires significant ops expertise. Community support is solid, but free-tier users may find delayed responses. Deep debugging sometimes requires premium enterprise help. Not as helpful in small to mid-size projects—often overkill unless you really need distributed SQL and horizontal scaling. While TiDB is a feature-rich offering, not all MySQL features are 100% compatible (e.g., stored procedures, full-text search limitations). Some MySQL-based ORMs and drivers may hit compatibility quirks. Also, integrating TiFlash (columnar storage) requires deeper understanding and tuning on developer end.
For advanced setups (multi-region, disaster recovery), the complexity increases rapidly and requires significant ops expertise. Community support is solid, but free-tier users may find delayed responses. Deep debugging sometimes requires premium enterprise help. Not as helpful in small to mid-size projects—often overkill unless you really need distributed SQL and horizontal scaling. While TiDB is a feature-rich offering, not all MySQL features are 100% compatible (e.g., stored procedures, full-text search limitations). Some MySQL-based ORMs and drivers may hit compatibility quirks. Also, integrating TiFlash (columnar storage) requires deeper understanding and tuning on developer end.
What problems is the product solving and how is that benefiting you?
As a software developer, I use TiDB for applications that require:
Horizontal Scalability for OLTP workloads as TiDB’s distributed architecture lets me scale out write-heavy applications without the traditional MySQL bottlenecks. TiDB is an ideal offering for multi-tenant SaaS platforms, e-commerce systems, or services where dataset size and concurrent users grow quickly.
With TiFlash, I am able to run real-time analytical queries (OLAP) on live transactional data (OLTP) without needing a separate ETL pipeline or data warehouse. This is especially helpful in dashboards, fraud detection systems, and internal BI platforms.
TiDB automatically handles failover with Raft consensus, which simplifies infrastructure resilience. No need to manually set up master-slave or manage replication lag. Thus offering high availability and fault tolerance.
It enables legacy apps or teams with MySQL knowledge to transition to a distributed backend without learning a new query language. Useful during modernization of monolithic systems.
Horizontal Scalability for OLTP workloads as TiDB’s distributed architecture lets me scale out write-heavy applications without the traditional MySQL bottlenecks. TiDB is an ideal offering for multi-tenant SaaS platforms, e-commerce systems, or services where dataset size and concurrent users grow quickly.
With TiFlash, I am able to run real-time analytical queries (OLAP) on live transactional data (OLTP) without needing a separate ETL pipeline or data warehouse. This is especially helpful in dashboards, fraud detection systems, and internal BI platforms.
TiDB automatically handles failover with Raft consensus, which simplifies infrastructure resilience. No need to manually set up master-slave or manage replication lag. Thus offering high availability and fault tolerance.
It enables legacy apps or teams with MySQL knowledge to transition to a distributed backend without learning a new query language. Useful during modernization of monolithic systems.
Could've been great if it had extended abilities in TiCDC
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
We initially explored TiDB as a way to consolidate our transactional and analytical workloads, which are currently split between MongoDB and Snowflake. Syncing data between the two has been a pain point, and TiDB’s HTAP capabilities looked like a promising solution. The idea of using a single system for both workloads, with strong consistency and horizontal scalability, was really appealing. Unfortunately, the lack of support for private hosting became a blocker for us, which was disappointing given how aligned the architecture was with our needs.
Best distributed SQL database offering
What do you like best about the product?
TiDB is an excellent distributed database offering by Pingcap which provides all features along with great stability like scalability, availability, durability etc while also giving excellent performance both in terms of throughput and latency. We have managed to scale TiDB to scale to over 1 million QPS with less than 50ms latency at Flipkart which is sufficient for most requirements for SQL.
What do you dislike about the product?
The architecture is fairly complex due to which debugging latency or issues in SQL is a hastle and requires deep expertise.
What problems is the product solving and how is that benefiting you?
TIDB is solving mostly scalabiilty and availability problems at Flipkart while supporting standard SQL. It is performing better than expectations in terms of performance and also has a very active community which help drive improvements and feature additions quickly.
Truly distributed MySQL supported database
What do you like best about the product?
It's the comprehensive MySQL distributed database, there are many similar database in market but they have lot of restrictions like Amazon DSQL, Google Alloy, Amazon Aurora etc. none of them are true distributed solution as they assume many things and solve for specific usecases. Also none of them are HTAP databases which is an advantage for TiDB.
What do you dislike about the product?
Few things majorly CDC not being transactional consistent, very complex monitoring systems, hard to debug issues on your own. These are not major things but they definitely impact adoption.
What problems is the product solving and how is that benefiting you?
The 2 major features for us were horizontal scaling and high availability using raft. These two helped us not worry about fitting our data into instance size / headache of manual sharding. Also HA was a major requirement for us as Master slave architecture always results in data loss and downtime for even single node failure
A scalable distributed DBMS with native HA
What do you like best about the product?
Obviously as a distributed database, its scaling capability and native high availability are best valuable.
What do you dislike about the product?
The execution plan of optimizer was unstable in some scenarios.
We wanna move some system to Alicloud unfortunately no dbaas offerings on Alicloud yet.
We wanna move some system to Alicloud unfortunately no dbaas offerings on Alicloud yet.
What problems is the product solving and how is that benefiting you?
It provides horizontal scaling to addressed challenge of large data processing. And the native HA ensured the system reliability.
Adoption of TiDB: Significant Reduction in Infrastructure Costs
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)
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**.
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**.
The agile data platfoem powered by TiDB
What do you like best about the product?
Overall we are satisfied with TiDB adoption. TiDB has many good features I love, here I highlight some top useful features for our company: 1. Finalcial-grade HA; 2. Online elastic expansion and contraction; 3. Support high concurrency and analytics workload; 4. Rich ecosystem of useful tools.
What do you dislike about the product?
1. Lack of data compression capability; 2. TiFlash testing performance is not good enough, and it requies much higher hardware resource.
What problems is the product solving and how is that benefiting you?
Due to MySQL single instance has bottleneck of storage and it needs sharding tasks, it can not support the rapid growing data. TiDB can support horiztontal scalability and high concurrency scenarios.
showing 51 - 60