DBMS > EJDB vs. EXASOL vs. Geode vs. Microsoft Azure Table Storage vs. Snowflake

System Properties Comparison EJDB vs. EXASOL vs. Geode vs. Microsoft Azure Table Storage vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A Wide Column Store for rapid development using massive semi-structured datasets

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

Primary database model

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/Softmotions/ejdb

www.exasol.com

geode.apache.org

azure.microsoft.com/en-us/services/storage/tables

www.snowflake.com

Technical documentation

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

www.exasol.com/resources

geode.apache.org/docs

docs.snowflake.net/manuals/index.html

Developer

Softmotions

Exasol

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

Snowflake Computing Inc.

Initial release

2012

2000

2002

2012

2014

Current release

1.1, February 2017

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Server operating systems

server-less

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Data scheme

schema-free

yes

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

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

yes

SQL-like query language (OQL)

yes

APIs and other access methods

in-process shared library

.Net
JDBC
ODBC
WebSocket

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
Lua
Python
R

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

ACID

yes, on a single node

optimistic locking

ACID

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.

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

Access rights per client and object definable

Access rights based on private key authentication or shared access signatures

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.