DBMS > EJDB vs. FatDB vs. GeoSpock vs. JaguarDB vs. SAP HANA

System Properties Comparison EJDB vs. FatDB vs. GeoSpock vs. JaguarDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Spatial and temporal data processing engine for extreme data scale

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Document store

Document store
Key-value store

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

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.27
Rank	#297	Overall
	#44	Document stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

github.com/Softmotions/ejdb

geospock.com

www.jaguardb.com

www.sap.com/products/hana.html

Technical documentation

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

www.jaguardb.com/support.html

help.sap.com/hana

Developer

Softmotions

FatCloud

GeoSpock

DataJaguar, Inc.

SAP

Initial release

2012

2015

2010

Current release

2.0, September 2019

3.3 July 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

GPL V3.0

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

C++

the server part. Clients available in other languages

Server operating systems

server-less

Windows

hosted

Linux

Appliance or cloud-service

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

temporal, categorical

yes

SQL

Support of SQL

Via inetgration in SQL Server

ANSI SQL for query only (using Presto)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

in-process shared library

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC

JDBC
ODBC

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

via applications

SQLScript, R

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Automatic sharding

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency

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

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

Can implement custom security layer via applications

Access rights for users can be defined per table

rights management via user accounts

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.