DBMS > EventStoreDB vs. Geode vs. Microsoft Azure Table Storage vs. OrientDB vs. SAP HANA

System Properties Comparison EventStoreDB vs. Geode vs. Microsoft Azure Table Storage vs. OrientDB 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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A Wide Column Store for rapid development using massive semi-structured datasets

Multi-model DBMS (Document, Graph, Key/Value)

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

Primary database model

Event Store

Key-value store

Wide column store

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

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	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.eventstore.com

geode.apache.org

azure.microsoft.com/en-us/services/storage/tables

orientdb.org

www.sap.com/products/hana.html

Technical documentation

developers.eventstore.com

geode.apache.org/docs

www.orientdb.com/docs/last/index.html

help.sap.com/hana

Developer

Event Store Limited

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

Microsoft

OrientDB LTD; CallidusCloud; SAP

SAP

Initial release

2012

2002

2012

2010

Current release

21.2, February 2021

1.1, February 2017

3.2.29, March 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

Apache version 2

commercial

Cloud-based only

Only available as a cloud service

yes

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

Java

Server operating systems

Linux
Windows

All OS with a Java VM

the JDK (8 or later) is also required

hosted

All OS with a Java JDK (>= JDK 6)

Appliance or cloud-service

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like query language, no joins

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

Java, Javascript

SQLScript, R

Triggers

yes

Cache Event Listeners

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

yes, on a single node

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights based on private key authentication or shared access signatures

Access rights for users and roles; record level security configurable

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.