DBMS > Geode vs. Percona Server for MongoDB vs. RocksDB vs. Teradata

System Properties Comparison Geode vs. Percona Server for MongoDB vs. RocksDB vs. Teradata

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 drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series 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.60
Rank	#246	Overall
	#39	Document stores

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

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

geode.apache.org

www.percona.com/mongodb/software/percona-server-for-mongodb

rocksdb.org

www.teradata.com

Technical documentation

geode.apache.org/docs

docs.percona.com/percona-distribution-for-mongodb

github.com/facebook/rocksdb/wiki

docs.teradata.com

Developer

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

Percona

Facebook, Inc.

Teradata

Initial release

2002

2015

2013

1984

Current release

1.1, February 2017

3.4.10-2.10, November 2017

9.2.1, May 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL Version 2

Open Source

BSD

commercial

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

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

hosted
Linux

Data scheme

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.

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL 2016 + extensions

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

proprietary protocol using JSON

C++ API
Java API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C
C++
Go
Java
Perl
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

JavaScript

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

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 capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

via In-Memory Engine

yes

User concepts

Access control

Access rights per client and object definable

Access rights for users and roles

fine grained access rights according to SQL-standard

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.