DBMS > EventStoreDB vs. Greenplum vs. Oracle Berkeley DB vs. RDF4J vs. SAP HANA

System Properties Comparison EventStoreDB vs. Greenplum vs. Oracle Berkeley DB vs. RDF4J vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Event Store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

RDF store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.eventstore.com

greenplum.org

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

rdf4j.org

www.sap.com/products/hana.html

Technical documentation

developers.eventstore.com

docs.greenplum.org

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

rdf4j.org/documentation

help.sap.com/hana

Developer

Event Store Limited

Pivotal Software Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

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

SAP

Initial release

2012

2005

1994

2004

2010

Current release

21.2, February 2021

7.0.0, September 2023

18.1.40, May 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based 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)

Java

Server operating systems

Linux
Windows

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

RDF Schemas

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

since Version 4.2

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

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

JDBC
ODBC

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

yes

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.