Scalability
TiDB offers horizontal scalability, allowing you to add more nodes to handle increased loads seamlessly. This makes it suitable for applications expected to grow rapidly.
MySQL Compatibility
TiDB is highly compatible with MySQL, enabling easy migration from MySQL databases and allowing developers to use familiar MySQL tools and syntax.
Distributed Architecture
TiDB's distributed architecture allows it to maintain high availability and reliability, with the ability to continue operating even if some nodes fail.
HTAP Capabilities
TiDB supports Hybrid Transactional/Analytical Processing (HTAP), which lets users perform real-time analytical queries on fresh transactional data without needing separate systems.
Strong Consistency
TiDB ensures strong consistency across distributed transactions, maintaining data integrity without sacrificing performance.
We have collected here some useful links to help you find out if TiDB is good.
Check the traffic stats of TiDB on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of TiDB on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of TiDB's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of TiDB on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about TiDB on Reddit. This can help you find out how popualr the product is and what people think about it.
A similar issue was also found in Tidb:. - Source: dev.to / 5 months ago
I do want to clarify a few points, on the project page it does provide the following information: > Distributed Transactions: TiDB uses a two-phase commit protocol to ensure ACID compliance, providing strong consistency. Transactions span multiple nodes, and TiDB's distributed nature ensures data correctness even in the presence of network partitions or node failures. > โฆ > High Availability: Built-in Raft... - Source: Hacker News / over 1 year ago
Note that TiDB did subject itself to Jepsen testing (relatively) early. Here's their 2019 results: https://jepsen.io/analyses/tidb-2.1.7 The devil is in the details, and anyone who is looking to implement TiDB for data correctness should read through not just this but other currently-open correctness-related Github issues: e.g., https://github.com/pingcap/tidb/issues?q=is%3Aissue%20state%3Aopen%20correctness. - Source: Hacker News / over 1 year ago
Tidb has been around for a while, it is distributed, written in Go and Rust, and MySQL compatible. https://github.com/pingcap/tidb. - Source: Hacker News / over 2 years ago
PingCAP | https://www.pingcap.com | Database Engineer, Product Manager, Developer Advocate and more | Remote in California | Full-time We work on a MySQL compatible distributed database called TiDB https://github.com/pingcap/tidb/. - Source: Hacker News / over 3 years ago
Isn't TiDB built on top of TiKV?[0] [0]: https://github.com/pingcap/tidb. - Source: Hacker News / almost 4 years ago
OLTP usually comes with high throughput of transactions, which means usually write(e.g., IUD - insert, update, delete) to read (e.g., select) ratio is above 4 or 5 or even higher. There are some good benchmarks to test OLTP workload like TPC-C (https://www.tpc.org/tpcc/), and some benchmarks to test OLAP workload like TPC-H (https://www.tpc.org/tpch/). For mixed or hybrid OLTP and OLAP (it's called HTAP, see this... - Source: Hacker News / almost 4 years ago
I am very agree with some options of this blog. As the maintainer of the open source distributed database TiDB https://github.com/pingcap/tidb, we also face the same problem of choice. We have a community version, an enterprise version(of course, we must sell it to our customers to earn money) and also a cloud service named TiDB cloud. Seven years before, we started to build TiDB to solve MySQL sharding problem,... - Source: Hacker News / about 4 years ago
Yes, hardware has limits and you just cannot have a single machine with unlimited number of cores and disks. But as the article mentioned, NewSQL is already there. DBs in this category has actually been awhile. I think Spanner's paper was 10 years ago. And it is ubiquitous across Google. So let's just accept that we should think things differently in 2022. Distributed RDBMS is already a thing, used in production,... - Source: Hacker News / about 4 years ago
Disclaimer: I now work at https://www.yugabyte.com/yugabytedb/, I joined because I liked their approach and think it has a lot of merit. But there are also https://www.cockroachlabs.com/product/, https://github.com/pingcap/tidb and. - Source: Hacker News / about 4 years ago
Tidb - TiDB is a distributed SQL database. Inspired by the design of Google F1. Source: about 4 years ago
Gitea is very easy to use, but I find the Activity feature is a little slow. I experienced the "Try Gitea" service and migrated our TiDB repo https://github.com/pingcap/tidb to it. When I clicked the Activity tab and selected "1 year" period, I found the page loading was so slow, nearly 90s. And I also found that this Activity doesn't have a Cache, I re-selected "1 year" again, and the page loading was... - Source: Hacker News / about 4 years ago
As the database supporter for ossinsight.io, I also use this to get many insights for TiDB itself, see https://ossinsight.io/analyze/pingcap/tidb. Source: about 4 years ago
Fair enough. Indeed I didn't consider support costs. Thank you for your answer! Actually let me ask another thing. Your FAQ mentions you're considering hosting CockroachDB as a drop-in distributed replacement for PostgreSQL [0], and also you currently offer a distributed, eventually consistent PostgreSQL replication solution [1]. Is either Tikv [2] (distributed key-value store) or Tidb [3] (distributed database... - Source: Hacker News / over 4 years ago
Yes, this is most popular way to make money from open source. You can see so many start-ups start their business in this way recently, e.g. https://github.com/cockroachdb/cockroach, https://github.com/pingcap/tidb, https://github.com/taosdata/TDengine, including my project, https://github.com/rustdesk/rustdesk, though it is still my personal project. Source: about 5 years ago
My knowledge is still quite limited because I never worked on the internals of distributed databases (I've only used and deployed them as an intern) but I have taken Advanced Databases CZ4031 in NTU and Parallel and Distributed Algorithms CS4231 in NUS which helped me get some basic understanding so you can consider taking those if you are interested. If you want to see how an open source database looks like, I... Source: about 5 years ago
Another Chinese database seems to be doing a better job at this front: https://github.com/pingcap/tidb. - Source: Hacker News / about 5 years ago
TiDB is the leading open-source, MySQL compatible, distributed NewSQL database in the industry that supports hybrid transactional and analytical processing (HTAP), which allows businesses to run real-time analytical queries. It also features horizontal scalability, strong consistency, and high availability. Source: about 5 years ago
TiDB, a cloud-native distributed SQL database maintained by PingCAP, has garnered significant attention in the database engineering community. As an open-source project, TiDB is known for its compatibility with the MySQL wire protocol while offering enhanced capabilities in distributed environments. Originally devised to address the challenges of MySQL sharding, TiDB has expanded into a robust NewSQL engine offering a combination of traditional relational database functionalities and NoSQL flexibility.
TiDB distinguishes itself with several features aimed at ensuring high performance and reliability. Its use of a two-phase commit protocol enables ACID-compliant distributed transactions across multiple nodes, ensuring robust data integrity even in cases of network partitions or node failures. The databaseโs architecture integrates a Raft consensus protocol, which underlies its high availability and automated failover mechanisms. With multiple data replicas spread geographically, TiDB caters to diverse disaster tolerance needs, maintaining data availability and consistency even in the event of node or replica failures.
The database has also been subject to rigorous Jepsen testingโa widely respected benchmark for data correctness in distributed systemsโwhich verifies TiDB's transactional integrity under stress. Nonetheless, some open issues related to data correctness remain actively discussed within the community, suggesting an ongoing commitment to transparency and improvement.
Strategically positioned among competitors like OceanBase, MySQL, StarRocks, and others, TiDB competes effectively with its MySQL compatibility and the ability to handle hybrid transactional and analytical processing (HTAP) workloads. This makes TiDB an attractive option for businesses requiring real-time analytical query support without sacrificing transactional integrity or availabilityโa nuanced requirement that not all databases in its category address adequately.
TiDBโs emphasis on an open-source ethos has cultivated a significant user base, leveraging community-driven development to maintain feature parity between its community and enterprise editions. The enterprise version includes minor differentiations like audit logs and IP whitelisting, but generally, both editions offer similar core functionalities. This strategy fosters community engagement while providing monetization avenues through enhanced services and features in the cloud offering, such as the TiDB Cloud.
Compared to traditional relational databases like MySQL, TiDB provides scalability through horizontal expansion, reducing the complexities associated with managing sharded workloads in MySQL. Against other distributed SQL solutions like CockroachDB, TiDB offers the advantage of native HTAP support, a feature that appeals to businesses looking for integrated analytical capabilities alongside transactional operations.
In context with technologies like Google Spannerโoften perceived as the progenitor of distributed RDBMS architecturesโTiDB offers a familiar SQL interface while circumventing the intricacies involved with scaling Spannerโs commercial model.
Overall, TiDB is celebrated as a cutting-edge database solution, embodying the best of both relational and non-relational paradigms. Its open-source nature, coupled with sophisticated scaling, availability, and consistency features, continues to gain traction as enterprises seek flexible, robust solutions for modern data challenges. As competition in the NewSQL and distributed database niche intensifies, TiDB's commitment to technical excellence and community engagement remains pivotal in its journey within the ever-evolving landscape of data technologies.
Do you know an article comparing TiDB to other products?
Suggest a link to a post with product alternatives.
Is TiDB good? This is an informative page that will help you find out. Moreover, you can review and discuss TiDB here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.