DBMS > Dragonfly vs. Geode vs. Kinetica vs. SAP HANA vs. SpaceTime

System Properties Comparison Dragonfly vs. Geode vs. Kinetica vs. SAP HANA vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

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

In-memory, column based data store. Available as appliance or cloud service

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Key-value store

Relational DBMS

Spatial DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

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

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

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

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

github.com/dragonflydb/dragonfly
www.dragonflydb.io

geode.apache.org

www.kinetica.com

www.sap.com/products/hana.html

www.mireo.com/spacetime

Technical documentation

www.dragonflydb.io/docs

geode.apache.org/docs

docs.kinetica.com

help.sap.com/hana

Developer

DragonflyDB team and community contributors

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

Kinetica

SAP

Mireo

Initial release

2023

2002

2012

2010

2020

Current release

1.0, March 2023

1.1, February 2017

7.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

C, C++

C++

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Appliance or cloud-service

Linux

Data scheme

scheme-free

schema-free

yes

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like DML and DDL statements

yes

A subset of ANSI SQL is implemented

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

RESTful HTTP API

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

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

C++
Java
JavaScript (Node.js)
Python

C#
C++
Python

Server-side scripts

Stored procedures

Lua

user defined functions

SQLScript, R

Triggers

publish/subscribe channels provide some trigger functionality

yes

Cache Event Listeners

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

Source-replica replication

yes

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Atomic execution of command blocks and scripts

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

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

User concepts

Access control

Password-based authentication

Access rights per client and object definable

Access rights for users and roles on table level

yes

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.