DBMS > EXASOL vs. JaguarDB vs. jBASE vs. RavenDB vs. RocksDB

System Properties Comparison EXASOL vs. JaguarDB vs. jBASE vs. RavenDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Performant, highly scalable DBMS for AI and IoT applications

A robust multi-value DBMS comprising development tools and middleware

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Multivalue DBMS

Document store

Key-value store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.exasol.com

www.jaguardb.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

ravendb.net

rocksdb.org

Technical documentation

www.exasol.com/resources

www.jaguardb.com/support.html

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

ravendb.net/docs

github.com/facebook/rocksdb/wiki

Developer

Exasol

DataJaguar, Inc.

Rocket Software (formerly Zumasys)

Hibernating Rhinos

Facebook, Inc.

Initial release

2000

2015

1991

2010

2013

Current release

3.3 July 2023

5.7

5.4, July 2022

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

Open Source

AGPL version 3, commercial license available

Open Source

BSD

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

the server part. Clients available in other languages

C++

Server operating systems

Linux

AIX
Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

Embedded SQL for jBASE in BASIC

SQL-like query language (RQL)

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based 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

C++ API
Java API

Supported programming languages

Java
Lua
Python
R

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

.Net
Basic
Jabbascript
Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

yes

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 for users, groups and roles according to SQL-standard

rights management via user accounts

Access rights can be defined down to the item level

Authorization levels configured per client per database

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.