DBMS > Geode vs. Graph Engine vs. RocksDB vs. Vitess

System Properties Comparison Geode vs. Graph Engine vs. RocksDB vs. Vitess

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Key-value store

Graph DBMS
Key-value store

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial 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.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

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

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

Technical documentation

geode.apache.org/docs

www.graphengine.io/docs/manual

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

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

Microsoft

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2002

2010

2013

Current release

1.1, February 2017

9.2.1, May 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

MIT License

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses available

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

.NET and C

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

.NET

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

yes

with proprietary extensions

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C#
C++
F#
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes, on a single node

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Users with fine-grained authorization concept

no user groups or roles

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.