CrateIO vs RethinkDB: What are the differences?
Developers describe CrateIO as "The Distributed Database for Docker". Crate is a distributed data store. Simply install Crate directly on your application servers and make the big centralized database a thing of the past. Crate takes care of synchronization, sharding, scaling, and replication even for mammoth data sets. On the other hand, RethinkDB is detailed 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.
CrateIO and RethinkDB belong to "Databases" category of the tech stack.
Some of the features offered by CrateIO are:
- Familiar SQL syntax
- Semi-structured data
- High availability, resiliency, and scalability in a distributed design
On the other hand, RethinkDB provides the following key features:
- JSON data model and immediate consistency.
- Distributed joins, subqueries, aggregation, atomic updates.
- Secondary, compound, and arbitrarily computed indexes.
"Simplicity" is the top reason why over 2 developers like CrateIO, while over 46 developers mention "Powerful query language" as the leading cause for choosing RethinkDB.
CrateIO and RethinkDB are both open source tools. It seems that RethinkDB with 22.4K GitHub stars and 1.74K forks on GitHub has more adoption than CrateIO with 2.49K GitHub stars and 333 GitHub forks.
What is CrateIO?
What is RethinkDB?
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 CrateIO?
What are the cons of using RethinkDB?
What companies use CrateIO?
Sign up to get full access to all the companiesMake informed product decisions
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.