RethinkDB vs Scylla: What are the differences?
RethinkDB: 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; Scylla: Next Generation Cassandra. Real-time big data database, with scale-up performance of 1,000,000 IOPS per node, scale-out to 100s of nodes and 99 latency of less than 1 msec.
RethinkDB and Scylla belong to "Databases" category of the tech stack.
RethinkDB and Scylla are both open source tools. It seems that RethinkDB with 22.4K GitHub stars and 1.74K forks on GitHub has more adoption than Scylla with 5.18K GitHub stars and 615 GitHub forks.
miDrive, Rove.me, and Lastbackend are some of the popular companies that use RethinkDB, whereas Scylla is used by Investing.com, Dstillery, and Yieldbot. RethinkDB has a broader approval, being mentioned in 37 company stacks & 25 developers stacks; compared to Scylla, which is listed in 11 company stacks and 5 developer stacks.
What is RethinkDB?
What is Scylla?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Scylla?
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 Scylla?
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.
ScyllaDB provides all of the goodies of Apache Cassandra, including HA, multiDC, replication sharding and so forth. The implementation is in C++ and the internal design is better and thus it achieves 10X the throughput, low 99% latency and more
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.