ArangoDB vs RethinkDB

Overview

RethinkDB

Stacks292

Followers406

Votes307

GitHub Stars27.0K

Forks1.9K

ArangoDB

Stacks273

Followers442

Votes192

ArangoDB vs RethinkDB: What are the differences?

Data Model: ArangoDB uses a multi-model approach, allowing users to store data in a document format, graph format, or key-value pairs. On the other hand, RethinkDB solely focuses on a document-based data model.
Query Language: ArangoDB uses its query language called AQL (ArangoDB Query Language) which supports complex queries and joins. In contrast, RethinkDB uses ReQL (RethinkDB Query Language) specifically designed for its document-based data model.
Horizontal Scalability: ArangoDB supports a native sharding feature for horizontal scalability, allowing users to distribute data across multiple servers. RethinkDB, on the other hand, lacks built-in support for sharding, making horizontal scalability more complex to achieve.
Change Feeds: RethinkDB provides real-time updates to queries through its change feeds feature, allowing applications to react to changes immediately. ArangoDB does not have a built-in change feed feature, requiring developers to implement custom solutions for real-time data updates.
Community Support: ArangoDB has a larger community base and more extensive documentation compared to RethinkDB, making it easier for users to find solutions to problems and access resources for development.
Transactions: ArangoDB supports multi-document transactions that allow users to perform ACID-compliant operations across multiple documents or collections. RethinkDB, on the other hand, does not offer native support for multi-document transactions, making complex transactional operations more challenging to implement.

In Summary, ArangoDB offers a multi-model approach, native sharding for scalability, and extensive community support, while RethinkDB focuses on a document-based data model, real-time change feeds, and simpler query language.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on RethinkDB, ArangoDB

Feb 24, 2022

Decided

I’m newbie I was developing a pouchdb and couchdb app cause if the sync. Lots of learning very little code available. I dropped the project cause it consumed my life. Yeats later I’m back into it. I researched other db and came across rethinkdb and mongo for the subscription features. With socketio I should be able to create and similar sync feature. Attempted to use mongo. I attempted to use rethink. Rethink for the win. Super clear l. I had it running in minutes on my local machine and I believe it’s supposed to scale easy. Mongo wasn’t as easy and there free online db is so slow what’s the point. Very easy to find mongo code examples and use rethink code in its place. I wish I went this route years ago. All that corporate google Amazon crap get bent. The reason they have so much power in the world is cause you guys are giving it to them.

79.7k views79.7k

Comments

gitgkk

Oct 19, 2021

Needs adviceon

TinyMCE

JSON

ArangoDB

Hello All, I'm building an app that will enable users to create documents using ckeditor or TinyMCE editor. The data is then stored in a database and retrieved to display to the user, these docs can contain image data also. The number of pages generated for a single document can go up to 1000. Therefore by design, each page is stored in a separate JSON. I'm wondering which database is the right one to choose between ArangoDB and PostgreSQL. Your thoughts, advice please. Thanks, Kashyap

64.3k views64.3k

Comments

Detailed Comparison

RethinkDB	ArangoDB
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.	A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.
JSON data model and immediate consistency.;Distributed joins, subqueries, aggregation, atomic updates.;Secondary, compound, and arbitrarily computed indexes.;Hadoop-style map/reduce.;Friendly web and command-line administration tools.;Takes care of machine failures and network interrupts.;Multi-datacenter replication and failover.;Sharding and replication to multiple nodes.;Queries are automatically parallelized and distributed.;Lock-free operation via MVCC concurrency.	multi-model nosql db; acid; transactions; javascript; database; nosql; sharding; replication; query language; joins; aql; documents; graphs; key-values; graphdb
Statistics
GitHub Stars 27.0K	GitHub Stars -
GitHub Forks 1.9K	GitHub Forks -
Stacks 292	Stacks 273
Followers 406	Followers 442
Votes 307	Votes 192
Pros & Cons
Pros 48 Powerful query language 46 Excellent dashboard 42 JSON 41 Distributed database 38 Open source	Pros 37 Grahps and documents in one DB 26 Intuitive and rich query language 25 Good documentation 25 Open source 21 Joins for collections Cons 3 Web ui has still room for improvement 2 No support for blueprints standard, using custom AQL
Integrations
Amazon EC2	No integrations available

What are some alternatives to RethinkDB, ArangoDB?

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

InfluxDB

InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running. InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out.

CouchDB

Apache CouchDB is a database that uses JSON for documents, JavaScript for MapReduce indexes, and regular HTTP for its API. CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents and query your indexes with your web browser, via HTTP. Index, combine, and transform your documents with JavaScript.

Related Comparisons

ArangoDB vs RethinkDB: What are the differences?

Data Model: ArangoDB uses a multi-model approach, allowing users to store data in a document format, graph format, or key-value pairs. On the other hand, RethinkDB solely focuses on a document-based data model.
Query Language: ArangoDB uses its query language called AQL (ArangoDB Query Language) which supports complex queries and joins. In contrast, RethinkDB uses ReQL (RethinkDB Query Language) specifically designed for its document-based data model.
Horizontal Scalability: ArangoDB supports a native sharding feature for horizontal scalability, allowing users to distribute data across multiple servers. RethinkDB, on the other hand, lacks built-in support for sharding, making horizontal scalability more complex to achieve.
Change Feeds: RethinkDB provides real-time updates to queries through its change feeds feature, allowing applications to react to changes immediately. ArangoDB does not have a built-in change feed feature, requiring developers to implement custom solutions for real-time data updates.
Community Support: ArangoDB has a larger community base and more extensive documentation compared to RethinkDB, making it easier for users to find solutions to problems and access resources for development.
Transactions: ArangoDB supports multi-document transactions that allow users to perform ACID-compliant operations across multiple documents or collections. RethinkDB, on the other hand, does not offer native support for multi-document transactions, making complex transactional operations more challenging to implement.

ArangoDB vs RethinkDB

Overview