DBMS > EJDB vs. Heroic vs. Hypertable vs. Hyprcubd vs. Microsoft Azure Cosmos DB

System Properties Comparison EJDB vs. Heroic vs. Hypertable vs. Hyprcubd vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

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

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Serverless Time Series DBMS

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

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.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

github.com/Softmotions/ejdb

github.com/spotify/heroic

hyprcubd.com (offline)

azure.microsoft.com/services/cosmos-db

Technical documentation

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

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

Developer

Softmotions

Spotify

Hypertable Inc.

Hyprcubd, Inc.

Microsoft

Initial release

2012

2014

2009

2014

Current release

0.9.8.11, March 2016

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

GNU version 3. Commercial license available

commercial

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.

Implementation language

Java

C++

Server operating systems

server-less

Linux
OS X
Windows

an inofficial Windows port is available

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

time, int, uint, float, string

yes

JSON types

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

yes

via Elasticsearch

restricted

only exact value or prefix value scans

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

APIs and other access methods

in-process shared library

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Thrift

gRPC (https)

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

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

C++
Java
Perl
PHP
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor on file system level

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

User concepts

Access control

token access

Access rights can be defined down to the item level

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.