DBMS > Citus vs. Geode vs. Kinetica vs. Sadas Engine vs. Snowflake

System Properties Comparison Citus vs. Geode vs. Kinetica vs. Sadas Engine vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

Fully vectorized database across both GPUs and CPUs

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

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

Spatial DBMS
Time Series DBMS

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

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

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

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

docs.citusdata.com

geode.apache.org/docs

docs.kinetica.com

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

docs.snowflake.net/manuals/index.html

Developer

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

Kinetica

SADAS s.r.l.

Snowflake Computing Inc.

Initial release

2010

2002

2012

2006

2014

Current release

8.1, December 2018

1.1, February 2017

7.1, August 2021

8.0

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free trial version 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, C++

C++

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

AIX
Linux
Windows

hosted

Data scheme

yes

schema-free

yes

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

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

SQL-like query language (OQL)

SQL-like DML and DDL statements

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
Proprietary protocol

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

C++
Java
JavaScript (Node.js)
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

Triggers

yes

Cache Event Listeners

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

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

GPU vRAM or System RAM

yes

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

Access rights for users and roles on table level

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

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.