DBMS > Geode vs. IRONdb vs. Kinetica vs. Snowflake vs. STSdb

System Properties Comparison Geode vs. IRONdb vs. Kinetica vs. Snowflake vs. STSdb

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

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

Fully vectorized database across both GPUs and CPUs

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

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

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

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

geode.apache.org

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

www.kinetica.com

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

geode.apache.org/docs

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

docs.kinetica.com

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.

Circonus LLC.

Kinetica

Snowflake Computing Inc.

STS Soft SC

Initial release

2002

2017

2012

2014

2011

Current release

1.1, February 2017

V0.10.20, January 2018

7.1, August 2021

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPLv2, 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 and C++

C, C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

hosted

Windows

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

primitive types and user defined types (classes)

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 (OQL)

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like DML and DDL statements

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

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

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

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

user defined functions

yes, in Lua

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

Automatic, metric affinity per node

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

configurable replication factor, datacenter aware

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

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

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

User concepts

Access control

Access rights per client and object definable

Access rights for users and roles on table level

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.