RethinkDB vs TiDB: What are the differences?
Developers describe RethinkDB as "JSON. Scales to multiple machines with very little effort. Open source". RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn. On the other hand, TiDB is detailed as "A distributed NewSQL database compatible with MySQL protocol". Inspired by the design of Google F1, TiDB supports the best features of both traditional RDBMS and NoSQL.
RethinkDB and TiDB can be categorized as "Databases" tools.
Some of the features offered by RethinkDB are:
- JSON data model and immediate consistency.
- Distributed joins, subqueries, aggregation, atomic updates.
- Secondary, compound, and arbitrarily computed indexes.
On the other hand, TiDB provides the following key features:
- Horizontal scalability
- Asynchronous schema changes
- Consistent distributed transactions
RethinkDB and TiDB are both open source tools. It seems that RethinkDB with 22.4K GitHub stars and 1.74K forks on GitHub has more adoption than TiDB with 19.6K GitHub stars and 2.85K GitHub forks.
What is RethinkDB?
What is TiDB?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using RethinkDB?
What are the cons of using TiDB?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with TiDB?
We initially chose RethinkDB because of the schema-less document store features, and better durability resilience/story than MongoDB In the end, it didn't work out quite as we expected: there's plenty of scalability issues, it's near impossible to run analytical workloads and small community makes working with Rethink a challenge. We're in process of migrating all our workloads to PostgreSQL and hopefully, we will be able to decommission our RethinkDB deployment soon.
High-speed update-aware storage used in our region server infrastructure; provides a good middle layer for storage of rapidly modified information.
Main database, using it in multiple datacenters in an active-active configuration.