DBMS > Greenplum vs. RDF4J vs. Redis vs. Teradata vs. Vitess

System Properties Comparison Greenplum vs. RDF4J vs. Redis vs. Teradata vs. Vitess

Editorial information provided by DB-Engines

Name

Description

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.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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 hybrid cloud data analytics software platform (Teradata Vantage)

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

RDF store

Key-value store

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

Relational 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

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

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

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

Technical documentation

docs.greenplum.org

rdf4j.org/documentation

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

docs.teradata.com

vitess.io/docs

Developer

Pivotal Software Inc.

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Teradata

The Linux Foundation, PlanetScale

Initial release

2005

2004

2009

1984

2013

Current release

7.0.0, September 2023

7.2.5, May 2024

Teradata Vantage 1.0 MU2, January 2019

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

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

commercial

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.

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

Implementation language

Java

Server operating systems

Linux

Linux
OS X
Unix
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

hosted
Linux

Docker
Linux
macOS

Data scheme

yes

RDF Schemas

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

Secondary indexes

yes

with RediSearch module

yes

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

yes

SQL

Support of SQL

yes

with RediSQL module

yes

SQL 2016 + extensions

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

proprietary protocol

RESP - REdis Serialization Protocol

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
Java
Perl
Python
R

Java
PHP
Python

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
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
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

yes

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

yes

UDFs, stored procedures, table functions in parallel

yes

proprietary syntax

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

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

Sharding

Hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Immediate 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

ACID

Isolation support depends on the API used

Atomic execution of command blocks and scripts and optimistic locking

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

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

fine grained access rights according to SQL-standard

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.