DBMS > Apache Impala vs. EJDB vs. KairosDB vs. MySQL vs. RavenDB

System Properties Comparison Apache Impala vs. EJDB vs. KairosDB vs. MySQL vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Distributed Time Series DBMS based on Cassandra or H2

Widely used open source RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Key/Value like access via memcached API

Document store

Secondary database models

Document store

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

impala.apache.org

github.com/Softmotions/ejdb

github.com/kairosdb/kairosdb

www.mysql.com

ravendb.net

Technical documentation

impala.apache.org/impala-docs.html

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

kairosdb.github.io

dev.mysql.com/doc

ravendb.net/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Hibernating Rhinos

Initial release

2013

2012

2013

1995

2010

Current release

4.1.0, June 2022

1.2.2, November 2018

8.4.0, April 2024

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL version 3, commercial license 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.

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

Implementation language

C++

Java

C and C++

Server operating systems

Linux

server-less

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

SQL-like DML and DDL statements

yes

with proprietary extensions

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

in-process shared library

Graphite protocol
HTTP REST
Telnet API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

Java
JavaScript

Node.js
PHP
Python

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

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

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

yes

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

Authorization levels configured per client per database

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.