DBMS > Geode vs. Greenplum vs. RocksDB vs. Stardog

System Properties Comparison Geode vs. Greenplum vs. RocksDB vs. Stardog

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

Technical documentation

geode.apache.org/docs

docs.greenplum.org

github.com/facebook/rocksdb/wiki

docs.stardog.com

Developer

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

Pivotal Software Inc.

Facebook, Inc.

Stardog-Union

Initial release

2002

2005

2013

2010

Current release

1.1, February 2017

7.0.0, September 2023

8.11.4, April 2024

7.3.0, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

BSD

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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++

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

schema-free and OWL/RDFS-schema support

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.

yes

since Version 4.2

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL-like query language (OQL)

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

C++ API
Java API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

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

C
Java
Perl
Python
R

C
C++
Go
Java
Perl
Python
Ruby

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

Cache Event Listeners

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

Transaction concepts

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

yes, on a single node

ACID

yes

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

User concepts

Access control

Access rights per client and object definable

fine grained access rights according to SQL-standard

Access rights for users and 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.