DBMS > Geode vs. Graphite vs. RocksDB vs. SwayDB

System Properties Comparison Geode vs. Graphite vs. RocksDB vs. SwayDB

Please select another system to include it in the comparison.

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Key-value store

Time Series DBMS

Key-value store

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

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

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

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

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

geode.apache.org

github.com/graphite-project/graphite-web

rocksdb.org

swaydb.simer.au

Technical documentation

geode.apache.org/docs

graphite.readthedocs.io

github.com/facebook/rocksdb/wiki

Developer

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

Chris Davis

Facebook, Inc.

Simer Plaha

Initial release

2002

2006

2013

2018

Current release

1.1, February 2017

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

BSD

Open Source

GNU Affero GPL V3.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

Python

C++

Scala

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Unix

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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)

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP API
Sockets

C++ API
Java API

Supported programming languages

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

JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

yes

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

locking

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

User concepts

Access control

Access rights per client and object definable

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.