DBMS > Geode vs. Greenplum vs. Postgres-XL vs. Redis vs. TigerGraph

System Properties Comparison Geode vs. Greenplum vs. Postgres-XL vs. Redis vs. TigerGraph

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.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Key-value store

Relational DBMS

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector 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	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

Technical documentation

geode.apache.org/docs

docs.greenplum.org

www.postgres-xl.org/documentation

docs.redis.com/latest/index.html
redis.io/docs

docs.tigergraph.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.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2002

2005

2014

since 2012, originally named StormDB

2009

2017

Current release

1.1, February 2017

7.0.0, September 2023

10 R1, October 2018

7.2.4, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

Mozilla public license

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Linux
macOS

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

yes

XML type, but no XML query functionality

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

SQL-like query language (OQL)

yes

distributed, parallel query execution

with RediSQL module

SQL-like query language (GSQL)

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

proprietary protocol

RESP - REdis Serialization Protocol

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

C
Java
Perl
Python
R

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Lua; Redis Functions coming in Redis 7 (slides and Github)

yes

Triggers

yes

Cache Event Listeners

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

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

MVCC

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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 Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

Role-based access control

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.