Knex.js vs RethinkDB: What are the differences?
What is Knex.js? SQL query builder for Postgres, MySQL, MariaDB, SQLite3, and Oracle. Knex.js is a "batteries included" SQL query builder for Postgres, MySQL, MariaDB, SQLite3, and Oracle designed to be flexible, portable, and fun to use. It features both traditional node style callbacks as well as a promise interface for cleaner async flow control, a stream interface, full featured query and schema builders, transaction support (with savepoints), connection pooling and standardized responses between different query clients and dialects.
What is 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.
Knex.js can be classified as a tool in the "Database Tools" category, while RethinkDB is grouped under "Databases".
"Write once and then connect to almost any sql engine" is the primary reason why developers consider Knex.js over the competitors, whereas "Powerful query language" was stated as the key factor in picking RethinkDB.
Knex.js and RethinkDB are both open source tools. RethinkDB with 22.3K GitHub stars and 1.73K forks on GitHub appears to be more popular than Knex.js with 9.79K GitHub stars and 1.22K GitHub forks.
miDrive, Runbook, and The Control Group are some of the popular companies that use RethinkDB, whereas Knex.js is used by Decision6, Zube, and Habx. RethinkDB has a broader approval, being mentioned in 37 company stacks & 25 developers stacks; compared to Knex.js, which is listed in 10 company stacks and 9 developer stacks.
What is Knex.js?
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 Knex.js?
What are the cons of using RethinkDB?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake 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.
Not an ORM but a query builder. So developers are encouraged or sometimes forced to think about SQL and database layer, which is a good thing.
Main database, using it in multiple datacenters in an active-active configuration.