Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
41 reviews
from
and
External reviews are not included in the AWS star rating for the product.
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.
TiDB supports data consolidation use case perfectly
What do you like best about the product?
Easy to use because it is highly compatible with MySQL protocol, reduces the costs of operations and migration.
It can consolidate all upstream MySQL instance data in one TiDB cluster, we do not need to care about underlying data sharding.
One-stack HTAP simplifies the data stack.
And good technical support.
It can consolidate all upstream MySQL instance data in one TiDB cluster, we do not need to care about underlying data sharding.
One-stack HTAP simplifies the data stack.
And good technical support.
What do you dislike about the product?
For some complex analysis queries, the pressure of TiKV storage resource is still relatively large.
Lack of robust resource control capabilities in current v6 version.
Lack of robust resource control capabilities in current v6 version.
What problems is the product solving and how is that benefiting you?
The challenges include: The data volume of a single table exceeds 100M, so the performance of standalone MySQL cannot meet the requirements, and doing sharding has increased the complexity. By adopting TiDB, we just simply add new nodes that can achieve horizontal expansion of cluster, to address high concurrency and massive data scenarios more easily.
TiDB is a good fit for enterprise big data platform
What do you like best about the product?
As a DBA with a foundation in MySQL, moving to TiDB requires almost no learning cost and is very user-friendly.
Each component in the TiDB cluster has achieved high availability design.
The Resource Control feature was good for the multi-tenant needs of different businesses.
Each component in the TiDB cluster has achieved high availability design.
The Resource Control feature was good for the multi-tenant needs of different businesses.
What do you dislike about the product?
Upgrading across major versions may encounter some unknown issues.
What problems is the product solving and how is that benefiting you?
The performance of single node MySQL will be limited in scenarios such as high concurrency writes and complex SQL queries, and it can not support direct delivery of data to Flink. By moving to TiDB, we built a real-time data warehouse framework with Flink which applied for the enterprise data hub.
A shardless database
What do you like best about the product?
mysql compatible, minimizing migration costs and leveraging mysql ecosystem.
scales horizontally to accommodate growth.
high available for 24/7 logistics needs.
scales horizontally to accommodate growth.
high available for 24/7 logistics needs.
What do you dislike about the product?
lacks ui managemet tool, requiring periodic command review for command-line usage.
tiflash is somewhat limited and needs improvement
tiflash is somewhat limited and needs improvement
What problems is the product solving and how is that benefiting you?
logistics data requires multi-dimensional queries, making traditional sharded databases solutions inadequate
The agile data platform powered by TiDB
What do you like best about the product?
1. The distributed architecture provides seamless scalability, making the data platform more agile.
2. One stack real-time HTAP capability
3. It is compatible with MySQL protocol, we do not change the app codes.
4. Avoid the cloud vendor lock-in, and the support team is good.
2. One stack real-time HTAP capability
3. It is compatible with MySQL protocol, we do not change the app codes.
4. Avoid the cloud vendor lock-in, and the support team is good.
What do you dislike about the product?
1. The sync diff function is imperfect and cannot compare the json and timestamp fields.
2. There is no mechanism for redirecting to TiKV when TiFlash is down, it will cause some query problems.
2. There is no mechanism for redirecting to TiKV when TiFlash is down, it will cause some query problems.
What problems is the product solving and how is that benefiting you?
The traditional databases needs to rely on application layer implementation for read-write separation and sharding, it brings challenges such as data fragmentation and high operation and maintenance costs. With TiDB distributed database, we have built a reliable, flexible and scalable data platform.
TiDB HTAP enables real-time insights
What do you like best about the product?
TiDB's HTAP capability enables real-time analytics based on the transactional data, it is very important for us to generate instant insights and make decisions.
Horizontal scaling is another one, it benefits us to manage the workload efficiently.
Horizontal scaling is another one, it benefits us to manage the workload efficiently.
What do you dislike about the product?
1. TiDB needs to enhance the optimization for wide table use case.
2. The management console can integrate more clinic and monitoring tools to simply daily operations.
2. The management console can integrate more clinic and monitoring tools to simply daily operations.
What problems is the product solving and how is that benefiting you?
The legacy infrastructure was challenged by data processing, real-time analytics, and scalability during peak business hours. TiDB addressed these issues and improved operational efficiency.
showing 21 - 30