DBMS > EJDB vs. PostGIS vs. RocksDB vs. Rockset

System Properties Comparison EJDB vs. PostGIS vs. RocksDB vs. Rockset

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

Primary database model

Secondary database models

Relational DBMS

Relational DBMS
Search engine

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	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

github.com/Softmotions/ejdb

postgis.net

rocksdb.org

rockset.com

Technical documentation

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

postgis.net/documentation

github.com/facebook/rocksdb/wiki

docs.rockset.com

Developer

Softmotions

Facebook, Inc.

Rockset

Initial release

2012

2005

2013

2019

Current release

3.4.2, February 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL v2.0

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

yes

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

Linux

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

dynamic typing

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

SQL

Support of SQL

yes

Read-only SQL queries, including JOINs

APIs and other access methods

in-process shared library

C++ API
Java API

HTTP REST

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

horizontal partitioning

Automatic sharding

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

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

yes

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

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.