DBMS > EJDB vs. Geode vs. RavenDB vs. SAP HANA vs. Spark SQL

System Properties Comparison EJDB vs. Geode vs. RavenDB vs. SAP HANA vs. Spark SQL

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series 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	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

github.com/Softmotions/ejdb

geode.apache.org

ravendb.net

www.sap.com/products/hana.html

spark.apache.org/sql

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

geode.apache.org/docs

ravendb.net/docs

help.sap.com/hana

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Softmotions

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

Hibernating Rhinos

SAP

Apache Software Foundation

Initial release

2012

2002

2010

2014

Current release

1.1, February 2017

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

AGPL version 3, commercial license available

commercial

Open Source

Apache 2.0

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

Java

Scala

Server operating systems

server-less

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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 (RQL)

yes

SQL-like DML and DDL statements

APIs and other access methods

in-process shared library

Java Client API
Memcached protocol
RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

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

Java
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

yes

SQLScript, R

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

yes, on a single node

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

Authorization levels configured per client per database

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.