DBMS > EJDB vs. PostGIS vs. Rockset vs. SAP HANA

System Properties Comparison EJDB vs. PostGIS vs. Rockset vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of PostgreSQL

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Primary database model

Secondary database models

Relational DBMS

Relational DBMS
Search engine

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	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

github.com/Softmotions/ejdb

postgis.net

rockset.com

www.sap.com/products/hana.html

Technical documentation

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

postgis.net/documentation

docs.rockset.com

help.sap.com/hana

Developer

Softmotions

Rockset

SAP

Initial release

2012

2005

2019

2010

Current release

3.4.2, February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL v2.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

C++

Server operating systems

server-less

hosted

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

Read-only SQL queries, including JOINs

yes

APIs and other access methods

in-process shared library

HTTP REST

JDBC
ODBC

Supported programming languages

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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

based on PostgreSQL

Access rights for users and organizations can be defined via Rockset console

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.