TiDB Cloud
PingCAPExternal reviews
76 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Scalable, Efficient, and Developer-Friendly
What do you like best about the product?
I use TiDB as the main database for my project, Zesty, because it's reliable, scalable, and fast. I like that it handles scalability well; as the workload increases with growing user data, TiDB doesn't slow down, which is crucial for a growing AI platform. It also makes management easier by automatically dealing with complex tasks like database sharding and distribution. I really enjoy that TiDB scales easily without needing to change how my application works and handles heavy traffic and real-time data efficiently. Its strong consistency and dependable performance are also highly appreciated. TiDB feels like using a regular SQL database but runs as a strong distributed system, allowing me to use standard MySQL-like queries, which makes development feel easier and more familiar. Additionally, TiDB handles both transactional and analytical tasks without needing separate systems, which suits my needs perfectly.
What do you dislike about the product?
At first, understanding the distributed architecture took some time. More real-world examples of SaaS and AI in the documentation would be helpful. Performance tuning feels a bit complicated for beginners. Making some small changes to the onboarding process would improve the experience. It was hard to grasp how performance tuning works in a distributed system that includes TiDB, TiKV, and PD. There were a lot of metrics and dashboards, which made things a bit confusing for someone just starting out. A straightforward, step-by-step guide on performance tuning for typical SaaS or AI workloads would make it much easier for new users to get started.
What problems is the product solving and how is that benefiting you?
I use TiDB for its scalability and reliability in managing Zesty's growing user data. It handles heavy traffic, maintains strong consistency, and simplifies database management, allowing me to focus on developing features. TiDB combines SQL familiarity with distributed power and handles both transactional and analytical tasks without separate systems.
TiDB: Seamless Scalability with Transactional Consistency
What do you like best about the product?
I like that TiDB combines strong transactional consistency with horizontal scalability while supporting analytical queries in the same system. This is especially valuable for Branchat where we manage complex, evolving conversation structures and need fast insights from historical data. TiDB's MySQL compatibility, reliability, and reduced operational overhead make it easy to adopt and maintain, allowing us to scale confidently without redesigning our architecture. The initial setup was straightforward and smooth. Its MySQL compatibility made it easy to integrate with our existing development workflow, and the documentation helped us to get up and running quickly.
What do you dislike about the product?
If there's one area for improvement, it would be simplifying advanced configuration and tuning for newer users, especially around performance optimization at scale. Some distributed system concepts have a learning curve.
What problems is the product solving and how is that benefiting you?
TiDB solves scalability, consistency, and data complexity for us. It handles structured conversations with strong transactional consistency and scalable analytical queries. TiDB's horizontal scalability and reduced need for separate OLAP systems allow us to grow smoothly as data increases.
TiDB Delivers NoSQL-Scale with SQL Simplicity and MySQL Compatibility
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product 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.
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.
Effortless Setup and High-Speed Performance
What do you like best about the product?
I have used TiDB for high-speed caching and really enjoy its RAG service using vector DB inference features. The high-speed inference and easy SQL capabilities are great. I particularly like TiDB's AI helper, which has been a huge help in writing proper schemas. I also enjoy the clustering aspect of TiDB. Everything worked well for me, and I found the initial setup to be very easy.
What do you dislike about the product?
Nothing
What problems is the product solving and how is that benefiting you?
I use TiDB for high speed caching and RAG with its vector DB inference features, benefiting from high speed inference and easy SQL.
Efficient Scaling with Strong Developer Support
What do you like best about the product?
I use TiDB primarily for storing relational data and transactions. A managed instance removes the pain of self-hosting on the cloud, and it performs well under high traffic loads. It's a great product with good developer support and constant updates introducing new features. I rely on developer tools and the console UI, appreciate the frequent backups and metrics for observability, and make use of the Python SDK. The initial setup was easy because there are enough docs for it.
What do you dislike about the product?
More integration with 3rd party tools would be helpful. Currently, only a handful of integrations are supported.
What problems is the product solving and how is that benefiting you?
I use TiDB as a database that eliminates the pain of self-hosting on a cloud, performing well under high traffic loads.
Low-Effort Setup with High Availability in a Distributed Database
What do you like best about the product?
I like that it’s a low effort setup, high availability and distributed database.
What do you dislike about the product?
It has quite a few of parameters that make it complicated, at least for the self hosted version.
What problems is the product solving and how is that benefiting you?
It’s solving scalability and needing separate solutions for analytics queries.
TiDB’s Simplicity Makes Database Management Effortless
What do you like best about the product?
The simplicity of using TiDB is the best thing about it!
What do you dislike about the product?
Initially it was a bit difficult to navigate the platform and find where exactly the Database and other functionality is located. The UX can be improved by having a more refined on-board experience
What problems is the product solving and how is that benefiting you?
The ease of using vector search in an SQL DB is a great feature by TiDB that is quite beneficial as well
Easy to integrate cloude DB
What do you like best about the product?
It is free and easy to implemntation and speedy sql database
What do you dislike about the product?
I haven't found anything significant that I would consider a real dislike. as i was use multiple features in it.
What problems is the product solving and how is that benefiting you?
I am a student searching for a platform that offers something initially free and reliable for the future.
Great All-in-one database platform, very good performance, simple to set up and maintain
What do you like best about the product?
Hybrid approach, best of both worlds: OLTP and OLAP without handling sync.
What do you dislike about the product?
Does not always select the appropriate engine (TiFlash vs TiKV on version 7.5)
What problems is the product solving and how is that benefiting you?
We have a lot of rows (3B+) and also need transactions and constraints. OLTP + OLAP kept in sync under the hood was the decisive factor for us.
works for enterprise. you're better with supabase if you're just hacking
What do you like best about the product?
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
What do you dislike about the product?
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
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
What problems is the product solving and how is that benefiting you?
helped me learn about few things that i would never otherwise consider. also found few tutorial on query optimisation which were super helpful
showing 21 - 30