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.
Crucial for Scalable, AI-Powered Emotional Context Processing
What do you like best about the product?
I really like TiDB Serverless for its built-in vector search and scalable setup. The cosine similarity search allows MindVector AI to match emotion and context vectors quickly without needing an extra database, making our design simpler. The serverless model automatically handles scaling, ensuring smooth performance during real-time recommendations. Its compatibility with MySQL made connecting to our Python backend very easy. Plus, TiDB's ability to manage both structured data and vectors in one platform increases efficiency, reduces operational complexity, and helps us develop AI-powered emotional support features more reliably.
What do you dislike about the product?
One part of TiDB Serverless that could use improvement is its documentation and examples, especially those related to vector search and AI applications. As a developer working on MindVector AI, I found it difficult at first to understand how to design a good vector schema, choose the right indexing methods, and fine-tuning performance because there weren't enough simple, practical examples. More tutorials that show how to integrate with machine learning pipelines, particularly reinforcement learning workflows, would be really helpful. Also, better debugging and visualization tools for checking vector similarity queries would make it easier for developers to check and trust their results. Adding more built-in support for AI-related tasks and clearer guidelines on best practices would definitely make development faster and greatly improve the overall experience for developers.
What problems is the product solving and how is that benefiting you?
I use TiDB for high-dimensional vector storage and real-time matching for personalized stress management. Its serverless scalability boosts performance, simplifying development with built-in vector search and single-system data management.
Unified Data Management Enhances Telemedicine
What do you like best about the product?
I like how TiDB lets us manage both relational data and embeddings within a single unified architecture, making development easier and reducing operational complexity. It effectively handles scalability issues, which is crucial for a telemedicine platform that deals with concurrent consultations and multilingual interactions. TiDB's distributed design ensures reliable performance as our user base grows. Its ability to merge structural healthcare data with vector-based knowledge retrieval in one scalable system is also impressive.
What do you dislike about the product?
One area that could be improved is providing clearer guidance on best practices for combining relational workloads with vector search in production settings. Although TiDB's hybrid features are strong, real world examples focused on RAG based healthcare or knowledge heavy applications would make it easier for users to get started. We had to experiment a bit to adjust how we index data and understand how the system performs when many people are using it at the same time. Having more detailed guides on optimizing performance for mixed workloads that include both SQL and vector operations would make it easier and more confident for teams to set up and use the system quickly.
What problems is the product solving and how is that benefiting you?
TiDB merges structural healthcare data with vector-based retrieval, supporting our telemedicine needs in one scalable system. It handles patient records and doctor profiles with consistency and powers fast vector searches. Its unified architecture simplifies development and ensures reliable performance as the user base grows.
Scalable and Efficient Database Solution for Modern AI Workloads
What do you like best about the product?
I really like how well TiDB works with both organized data and vector embeddings all in one distributed database. This let me handle research metadata and embedding vectors together without needing multiple systems, which made the overall architecture of InsightForge AI much simpler. I also value its strong consistency and quick query responses, which made sure the Retrieval-Augmented Generation process was reliable and accurate. Plus, TiDB's scalability helped me manage growing research data without slowing things down. Since it works well with SQL, integrating it was easy, allowing me to create a solid, efficient, and scalable backend. The SQL compatibility helped me design schemas, query research metadata, and integrate TiDB smoothly with my Node.js backend. The distributed architecture ensured high availability and consistent performance as I added more embedding data and research documents. I also used TiDB to store and retrieve vector embeddings efficiently, which allowed for accurate semantic search in my pipeline. Its ability to handle both structured queries and similarity-based searches was key for producing reliable, citation-backed research reports.
What do you dislike about the product?
One area where TiDB could improve is how easy it is to work with vector embeddings and semantic search processes. Although TiDB can store and query vector data, getting good performance for large-scale embedding searches often needs extra query tuning and changes to the database structure. Having more built-in tools for vector indexing, optimizing similarity searches, and monitoring performance would make development easier. Also, better documentation and examples for setting up Retrieval-Augmented Generational pipelines would help developers use TiDB more effectively. Improving debugging and observability when handling mixed workloads that include both SQL and vector queries would also make the overall experience better and simplify integration.
What problems is the product solving and how is that benefiting you?
I use TiDB for scalable storage and quick data retrieval, storing both structured metadata and vector embeddings. Its distributed nature ensures fast, consistent, and scalable operations, allowing efficient querying and integrating semantic vector searches with SQL queries.
Effortlessly Scalable, Robust MySQL Alternative
What do you like best about the product?
I like TiDB's ability to combine scalability, strong consistency, and MySQL compatibility in a single distributed SQL database. The horizontal scalability is particularly impressive because we can scale out by adding nodes without downtime or major architectural changes, which is ideal for growing applications with unpredictable workloads. I really appreciate TiDB's operational simplicity for a distributed database. The scalability, performance, and operational simplicity are what make TiDB most valuable to us. The ability to scale horizontally allows us to handle growing traffic and data without redesigning our system. Performance remains stable even under high concurrency, which is critical for our production workloads. Operational features like automatic failover, replication, and data rebalancing reduce maintenance overhead and minimize downtime risk. Overall, TiDB helps us grow confidently while keeping infrastructure management efficient and predictable.
What do you dislike about the product?
While TiDB performs well overall, there are a few areas that could be improved. First, operating a distributed database can still be complex, especially for smaller teams without strong DevOps experience. Although TiDB simplifies many aspects, understanding cluster tuning and resource planning requires a learning curve. Second, certain advanced query optimizations may require manual tuning in very complex workloads. Performance is strong, but fine-tuning for edge cases can take time.
What problems is the product solving and how is that benefiting you?
We use TiDB to handle high-traffic transactional workloads and real-time analytics, allowing us to scale horizontally without redesign. It solves performance bottlenecks under high concurrency and eliminates single points of failure with built-in replication and automatic failover.
Scalable and Consistent Database Solution
What do you like best about the product?
I really like TiDB's strong transactional consistency. When a document is uploaded and processed, several related records like chunk mappings, summaries, and action items need to be stored reliably. TiDB's ACID guarantees ensure these operations are consistent and atomic. I also value the MySQL compatibility, as it made it easy for us to integrate with our Python backend without changing how we develop, and it also sets us up for scaling beyond a prototype.
What do you dislike about the product?
One area that could be improved is how clearly new teams understand the onboarding process for distributed SQL systems. Although TiDB is compatible with MySQL, learning how query performance works in a distributed setup may need extra effort, particularly for teams moving from simpler single node databases.
What problems is the product solving and how is that benefiting you?
TiDB addresses handling structured metadata and query states, ensuring reliable tracking of document ownership, connections, summaries, and queries. It provides a consistent, scalable database solution with MySQL compatibility, simplifying integration with our backend and aiding scalability beyond a prototype.
Effortless Integration of Structured and Vector Data
What do you like best about the product?
I like how well TiDB handles both structured data and vector search in one place. It makes it easy to store shelter details and vector embeddings in the same database, allowing me to do semantic matching and apply filters like capacity and distance in a single query. The integration of relational and vector data management in one system significantly simplifies development and maintenance. TiDB Serverless is also great for its scalability and ease of setup, enabling me to quickly build and test systems without handling infrastructure setup. Despite constant updates from AI agents, the performance remains steady, making it reliable for real-time situations like disaster response.
What do you dislike about the product?
One area where TiDB could improve is by offering more detailed documentation and examples focused on vector search scenarios. Although the core features worked well, I initially needed to experiment with query structures, similarity thresholds, and indexing approaches to get accurate shelter matching results. More hands-on guides or best practices for real-world AI applications would make it easier for people to adopt and use TiDB effectively. Also, having better built-in observability for vector queries, like clearer performance metrics or explanations of similarity scores, would help with tuning and troubleshooting. Since my project involved multiple AI agents and real-time updates, greater transparency into how vector queries perform would make optimization easier.
What problems is the product solving and how is that benefiting you?
I use TiDB to handle structured data and vector embeddings in one database, allowing me to perform semantic and structured searches efficiently, manage real-time updates, and ensure reliability and responsiveness for disaster response.
Scalable and Reliable HTAP Solution
What do you like best about the product?
I used TiDB as the main database for my AI-powered product support platform, and it did a great job of handling real-time user queries and storing data reliably. TiDB's compatibility with MySQL made integration with my Flask backend easy using standard SQL queries. I really appreciated TiDB's HTAP feature because it let me handle both transactional and analytical tasks within the same database. With TiFlash replication, I was able to run analytical queries on tasks and user data without slowing down the real-time performance of my applications. Its distributed structure made it easy to expand the system as more products, users, and documents were added. TiDB offered strong consistency and reliability, ensuring that user interactions were handled accurately, and its distributed setup helped with scalability and high availability.
What do you dislike about the product?
One challenge I faced was tuning queries for analytical workloads with TiFlash, which needed careful planning of the schema and proper indexing to achieve the best performance. Because my platform handles both transactional and analytical queries, I had to learn how replication and query execution work, which required some trial and error. Having better examples and guidelines for HTAP scenarios, especially for analytics dashboards and task monitoring, would help developers improve performance more quickly. Another challenge was keeping track of and fixing how queries performed in both transactional and analytical tasks. Even though TiDB has helpful tools, it took a while to figure out which queries were using TiKV or TiFlash and then improve their performance. Having simpler dashboards and more straightforward information about how queries run would help developers spot and fix performance problems faster. Also, more easy-to-use examples for integrating TiDB with frameworks like Flask would make it 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 high availability, handling both transactional and analytical data efficiently. It integrates easily due to MySQL compatibility and allows quick analytical queries with TiFlash. It ensures reliability, supports real-time insights, and manages growing user data seamlessly.
TiDB: Real-Time Scalability with Consistency for Fraud Detection
What do you like best about the product?
I use TiDB Serverless as the main transactional database for my fraud detection platform because TiDB offers fast read and write operations that are crucial for real-time decision-making in fraud detection. I appreciate how TiDB helps scale real-time transaction processing without losing consistency or needing a complicated database setup, allowing us to handle transactions efficiently. I really enjoy TiDB's horizontal scalability combined with the ease of using SQL, as it allows us to manage various tasks smoothly without changing our data structure or switching to a new model. I also like the strong consistency TiDB offers, ensuring all transaction details, risk evaluations, and alert logs are saved together, which gives us trust in the system's reliability.
What do you dislike about the product?
One thing that could be better is the process of getting new terms up to speed when moving from a single node database like SQLite or regular MySQL to TiDB. Even though TiDB works with MySQL, it takes extra learning to understand how queries work in a distributed system, how to set up indexes, and how to tune performance for a distributed setup.
What problems is the product solving and how is that benefiting you?
I use TiDB Serverless for seamless real-time transaction processing in FraudSentinel AI. It scales efficiently without losing consistency, ensuring reliable fraud detection by handling high read-write workloads while maintaining data integrity and using standard SQL.
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.
showing 11 - 20