DBMS > ArangoDB vs. EJDB vs. MySQL

System Properties Comparison ArangoDB vs. EJDB vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native multi-model DBMS for graph, document, key/value and search. All in one engine and accessible with one query language.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Widely used open source RDBMS

Primary database model

Document store
Graph DBMS
Key-value store
Search engine

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.96
Rank	#89	Overall
	#15	Document stores
	#5	Graph DBMS
	#13	Key-value stores
	#10	Search engines

Score	0.14
Rank	#331	Overall
	#47	Document stores

Score	1003.76
Rank	#2	Overall
	#2	Relational DBMS

Website

arangodb.com

github.com/Softmotions/ejdb

www.mysql.com

Technical documentation

docs.arangodb.com

github.com/Softmotions/ejdb/blob/master/README.md

dev.mysql.com/doc

Developer

ArangoDB Inc.

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

1995

Current release

3.11.5, November 2023

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2; Commercial license (Enterprise) available

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C and C++

Server operating systems

Linux
OS X
Windows

server-less

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

automatically recognizes schema within a collection

schema-free

yes

Typing

predefined data types such as float or date

yes

string, double, boolean, list, hash

yes

string, integer, double, bool, date, object_id

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

AQL
Foxx Framework
Graph API (Gremlin)
GraphQL query language
HTTP API
Java & SpringData
JSON style queries
VelocyPack/VelocyStream

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
Clojure
Elixir
Go
Java
JavaScript (Node.js)
PHP
Python
R
Rust

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

since version 2.0

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication with configurable replication factor

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be done with stored procedures in JavaScript

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

configurable per collection or per write
Immediate Consistency
OneShard (highly available, fault-tolerant deployment mode with ACID semantics)

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

yes

Users with fine-grained authorization concept

no user groups or roles

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.