DBMS > EXASOL vs. Geode vs. Sadas Engine vs. Snowflake vs. Splice Machine

System Properties Comparison EXASOL vs. Geode vs. Sadas Engine vs. Snowflake vs. Splice Machine

Editorial information provided by DB-Engines

Name

Description

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

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

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

Technical documentation

www.exasol.com/resources

geode.apache.org/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

docs.snowflake.net/manuals/index.html

splicemachine.com/how-it-works

Developer

Exasol

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

SADAS s.r.l.

Snowflake Computing Inc.

Splice Machine

Initial release

2000

2002

2006

2014

Current release

1.1, February 2017

8.0

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free trial version available

commercial

Open Source

AGPL 3.0, commercial license available

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++

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Linux
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

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

yes

Typing

predefined data types such as float or date

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

.Net
JDBC
ODBC
WebSocket

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol

CLI Client
JDBC
ODBC

JDBC
Native Spark Datasource
ODBC

Supported programming languages

Java
Lua
Python
R

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

JavaScript (Node.js)
Python

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

yes

Java

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

managed by 'Learn by Usage'

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 for users, groups and roles according to SQL-standard

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

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

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.