I would rate TiDB Cloud overall at an eight out of ten. It has pretty good horizontal scaling and OLTP use. TiDB Cloud stands out because it combines traditional SQL reliability with modern distributed scaling. Most systems separate OLTP and OLAP, but TiDB Cloud runs both. It also has MySQL compatibility. There is no manual sharding. Other manual distributed databases sacrifice consistency, but TiDB Cloud provides full ACID, distributed transactions, and Raft replication. That makes it stand out from others. TiDB Cloud is typically deployed in my organization as a distributed cluster to support high availability. In my company, there was a standard deployment architecture with a service layer behind a load balancer. The second layer was TiKV for distributed storage. TiFlash was optional, but we used it for fast OLAP queries. There were also placement drivers. TiDB Cloud is a strong, modern distributed SQL database. Its real value appears only at scale, with balanced workloads or on a rapidly growing SaaS platform. It really shines there for high-concurrency and mixed workloads. I would tell others looking into using TiDB Cloud that it supports horizontal sharding and node replicas. Use TiDB Cloud for write-heavy workloads, as it outshines others for things such as high-concurrency OLTP and high-throughput data. Benchmark real queries and validate the HTAP benefits. This prevents surprises in production. Plan for proper cluster sizing. We worked mainly with Azure for TiDB Cloud. My overall rating for this product is eight out of ten.
Overall, I would rate it a seven out of ten. Because it is open source, I can recommend it to those who are looking for a cheap product and don't want to invest heavily in a database. However, if they use TiDB, they need to plan their development so that most of the logic is written on the application side, as TiDB does not support features like functions and procedures. If they are comfortable with that approach, then it's fine.
There are a few pitfalls and some complexity, but overall it's highly recommended. It's particularly useful for tracing the applications and use cases of complex data. I recommend the solution. The advice is to use TiDB Cloud for any product or evaluate it based on your use cases. Consider what is important for you: whether you can manage it yourself or prefer to delegate those efforts to your provider, who will handle things for you. TiDB Cloud is powerful for connecting your metrics to understand behavior, both on the product side and the insight engineering side. Additionally, TiDB Cloud is useful for identifying issues if something goes wrong. Overall, I rate the solution a nine out of ten.
Unleash the power of AI-generated SQL and Serverless HTAP in a single cloud-native database. Experience real-time analytics and elastic scaling, all in a fully managed service.
Elastically and transparently scale to hundreds of nodes for critical workloads without changing business logic.
Use what you know about SQL – maintain your relational model and global ACID transactions while coping with your hybrid workloads at ease.
Equipped with built-in high performance analytics engine to analyze...
I would rate TiDB Cloud overall at an eight out of ten. It has pretty good horizontal scaling and OLTP use. TiDB Cloud stands out because it combines traditional SQL reliability with modern distributed scaling. Most systems separate OLTP and OLAP, but TiDB Cloud runs both. It also has MySQL compatibility. There is no manual sharding. Other manual distributed databases sacrifice consistency, but TiDB Cloud provides full ACID, distributed transactions, and Raft replication. That makes it stand out from others. TiDB Cloud is typically deployed in my organization as a distributed cluster to support high availability. In my company, there was a standard deployment architecture with a service layer behind a load balancer. The second layer was TiKV for distributed storage. TiFlash was optional, but we used it for fast OLAP queries. There were also placement drivers. TiDB Cloud is a strong, modern distributed SQL database. Its real value appears only at scale, with balanced workloads or on a rapidly growing SaaS platform. It really shines there for high-concurrency and mixed workloads. I would tell others looking into using TiDB Cloud that it supports horizontal sharding and node replicas. Use TiDB Cloud for write-heavy workloads, as it outshines others for things such as high-concurrency OLTP and high-throughput data. Benchmark real queries and validate the HTAP benefits. This prevents surprises in production. Plan for proper cluster sizing. We worked mainly with Azure for TiDB Cloud. My overall rating for this product is eight out of ten.
Overall, I would rate it a seven out of ten. Because it is open source, I can recommend it to those who are looking for a cheap product and don't want to invest heavily in a database. However, if they use TiDB, they need to plan their development so that most of the logic is written on the application side, as TiDB does not support features like functions and procedures. If they are comfortable with that approach, then it's fine.
There are a few pitfalls and some complexity, but overall it's highly recommended. It's particularly useful for tracing the applications and use cases of complex data. I recommend the solution. The advice is to use TiDB Cloud for any product or evaluate it based on your use cases. Consider what is important for you: whether you can manage it yourself or prefer to delegate those efforts to your provider, who will handle things for you. TiDB Cloud is powerful for connecting your metrics to understand behavior, both on the product side and the insight engineering side. Additionally, TiDB Cloud is useful for identifying issues if something goes wrong. Overall, I rate the solution a nine out of ten.