DBMS > Geode vs. RocksDB vs. STSdb vs. TerminusDB vs. Warp 10

System Properties Comparison Geode vs. RocksDB vs. STSdb vs. TerminusDB vs. Warp 10

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Key-value store

Graph DBMS

Time Series DBMS

Secondary database models

Document store
RDF store

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

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

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

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

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

geode.apache.org

rocksdb.org

github.com/STSSoft/STSdb4

terminusdb.com

www.warp10.io

Technical documentation

geode.apache.org/docs

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

www.warp10.io/content/02_Getting_started

Developer

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

Facebook, Inc.

STS Soft SC

DataChemist Ltd.

SenX

Initial release

2002

2013

2011

2018

2015

Current release

1.1, February 2017

9.2.1, May 2024

4.0.8, September 2015

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD

Open Source

GPLv2, commercial license available

Open Source

GPL V3

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Prolog, Rust

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language (WOQL)

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

.NET Client API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

HTTP API
Jupyter
WebSocket

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

C#
Java

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

yes

WarpScript

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Graph Partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

Journaling Streams

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

yes

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

Role-based access control

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.