DBMS > EJDB vs. IRONdb vs. RethinkDB vs. Snowflake

System Properties Comparison EJDB vs. IRONdb vs. RethinkDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb 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)

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	2.58
Rank	#105	Overall
	#20	Document stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

github.com/Softmotions/ejdb

www.circonus.com/solutions/time-series-database/

rethinkdb.com

www.snowflake.com

Technical documentation

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

docs.circonus.com/irondb/category/getting-started

rethinkdb.com/docs

docs.snowflake.net/manuals/index.html

Developer

Softmotions

Circonus LLC.

The Linux Foundation

since July 2017

Snowflake Computing Inc.

Initial release

2012

2017

2009

2014

Current release

V0.10.20, January 2018

2.4.1, August 2020

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache Version 2

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

C and C++

C++

Server operating systems

server-less

Linux

Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

text, numeric, histograms

yes

string, binary, float, bool, date, geometry

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 query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

in-process shared library

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

Triggers

Client-side triggers through changefeeds

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

Sharding

range based

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

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 per node, eventual consistency across nodes

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

MVCC based

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

yes

users and table-level permissions

Users with fine-grained authorization concept, user roles and pluggable authentication

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.