DBMS > Greenplum vs. Oracle Berkeley DB vs. Qdrant vs. Redis vs. Sphinx

System Properties Comparison Greenplum vs. Oracle Berkeley DB vs. Qdrant vs. Redis vs. Sphinx

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.

Widely used in-process key-value store

A high-performance vector database with neural network or semantic-based matching

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.

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Vector DBMS

Key-value store

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

Search engine

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	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

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

Score	5.97
Rank	#56	Overall
	#5	Search engines

Website

greenplum.org

www.oracle.com/database/technologies/related/berkeleydb.html

github.com/qdrant/qdrant
qdrant.tech

redis.com
redis.io

sphinxsearch.com

Technical documentation

docs.greenplum.org

docs.oracle.com/cd/E17076_05/html/index.html

qdrant.tech/documentation

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

sphinxsearch.com/docs

Developer

Pivotal Software Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Qdrant

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Sphinx Technologies Inc.

Initial release

2005

1994

2021

2009

2001

Current release

7.0.0, September 2023

18.1.40, May 2020

7.2.5, May 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

Apache Version 2.0

Open Source

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

Open Source

GPL version 2, commercial licence 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.

Implementation language

C, Java, C++ (depending on the Berkeley DB edition)

Rust

C++

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Docker
Linux
macOS
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

with RediSearch module

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

with RediSQL module

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

proprietary protocol

RESP - REdis Serialization Protocol

Proprietary protocol

Supported programming languages

C
Java
Perl
Python
R

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

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

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

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

Triggers

yes

only for the SQL API

publish/subscribe channels provide some trigger functionality; RedisGears

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

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Collection-level replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

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, tunable 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

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

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

The original contents of fields are not stored in the Sphinx index.

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

Key-based authentication

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.