DBMS > EJDB vs. Hypertable vs. KairosDB vs. KeyDB vs. SAP HANA

System Properties Comparison EJDB vs. Hypertable vs. KairosDB vs. KeyDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

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

An open source BigTable implementation based on distributed file systems such as Hadoop

Distributed Time Series DBMS based on Cassandra or H2

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/Softmotions/ejdb

github.com/kairosdb/kairosdb

github.com/Snapchat/KeyDB
keydb.dev

www.sap.com/products/hana.html

Technical documentation

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

kairosdb.github.io

docs.keydb.dev

help.sap.com/hana

Developer

Softmotions

Hypertable Inc.

EQ Alpha Technology Ltd.

SAP

Initial release

2012

2009

2013

2019

2010

Current release

0.9.8.11, March 2016

1.2.2, November 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GNU version 3. Commercial license available

Open Source

Apache 2.0

Open Source

BSD-3

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java

C++

Server operating systems

server-less

Linux
OS X
Windows

an inofficial Windows port is available

Linux
OS X
Windows

Linux

Appliance or cloud-service

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

Secondary indexes

restricted

only exact value or prefix value scans

yes

by using the Redis Search module

yes

SQL

Support of SQL

yes

APIs and other access methods

in-process shared library

C++ API
Thrift

Graphite protocol
HTTP REST
Telnet API

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC

Supported programming languages

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

C++
Java
Perl
PHP
Python
Ruby

Java
JavaScript

Node.js
PHP
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

Lua

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor on file system level

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control

simple password-based access control and ACL

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.