DBMS > Geode vs. HEAVY.AI vs. Rockset vs. Snowflake vs. XTDB

System Properties Comparison Geode vs. HEAVY.AI vs. Rockset vs. Snowflake vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Spatial DBMS

Relational DBMS
Search engine

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

geode.apache.org

github.com/heavyai/heavydb
www.heavy.ai

rockset.com

www.snowflake.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

geode.apache.org/docs

docs.heavy.ai

docs.rockset.com

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

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

HEAVY.AI, Inc.

Rockset

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2002

2016

2019

2014

2019

Current release

1.1, February 2017

5.10, January 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

MIT License

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

C++

Clojure

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

yes

yes, extensible-data-notation format

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.

ingestion from XML files supported

yes

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

Read-only SQL queries, including JOINs

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

HTTP REST

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

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

All languages supporting JDBC/ODBC/Thrift
Python

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Clojure
Java

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

Sharding

Round robin

Automatic sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 per client and object definable

fine grained access rights according to SQL-standard

Access rights for users and organizations can be defined via Rockset console

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.