DBMS > Axibase vs. Geode vs. Greenplum vs. Percona Server for MongoDB vs. Redis

System Properties Comparison Axibase vs. Geode vs. Greenplum vs. Percona Server for MongoDB vs. Redis

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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.

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

Primary database model

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

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	0.29
Rank	#292	Overall
	#25	Time Series DBMS

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

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

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

Website

axibase.com/docs/atsd/finance

geode.apache.org

greenplum.org

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

redis.com
redis.io

Technical documentation

geode.apache.org/docs

docs.greenplum.org

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

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

Developer

Axibase Corporation

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

Pivotal Software Inc.

Percona

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2013

2002

2005

2015

2009

Current release

15585

1.1, February 2017

7.0.0, September 2023

3.4.10-2.10, November 2017

7.2.4, January 2024

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.0

Open Source

GPL Version 2

Open Source

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

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

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

partial

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

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

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

SQL-like query language

SQL-like query language (OQL)

yes

with RediSQL module

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

proprietary protocol using JSON

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Go
Java
PHP
Python
R
Ruby

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

C
Java
Perl
Python
R

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

Server-side scripts

Stored procedures

yes

user defined functions

yes

JavaScript

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

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

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

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

Transaction concepts

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

yes, on a single node

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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

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.