DBMS > Amazon DocumentDB vs. Apache Impala vs. JaguarDB vs. MySQL vs. Realm

System Properties Comparison Amazon DocumentDB vs. Apache Impala vs. JaguarDB vs. MySQL vs. Realm

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Analytic DBMS for Hadoop

Performant, highly scalable DBMS for AI and IoT applications

Widely used open source RDBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Document store

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Website

aws.amazon.com/documentdb

Technical documentation

aws.amazon.com/documentdb/resources

impala.apache.org/impala-docs.html

www.jaguardb.com/support.html

dev.mysql.com/doc

realm.io/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

DataJaguar, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Realm, acquired by MongoDB in May 2019

Initial release

2019

2013

2015

1995

2014

Current release

4.1.0, June 2022

3.3 July 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GPL V3.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

the server part. Clients available in other languages

C and C++

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Android
Backend: server-less
iOS
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

selectable replication factor

Multi-source replication

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-document operations

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

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

In-Memory realm

User concepts

Access control

Access rights for users and roles

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

yes

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.