DBMS > Apache Drill vs. IBM Cloudant vs. JaguarDB vs. RocksDB vs. SAP HANA

System Properties Comparison Apache Drill vs. IBM Cloudant vs. JaguarDB vs. RocksDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Database as a Service offering based on Apache CouchDB

Performant, highly scalable DBMS for AI and IoT applications

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

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

Primary database model

Document store
Relational DBMS

Document store

Key-value store
Vector DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

drill.apache.org

www.ibm.com/products/cloudant

www.jaguardb.com

rocksdb.org

www.sap.com/products/hana.html

Technical documentation

drill.apache.org/docs

cloud.ibm.com/docs/Cloudant

www.jaguardb.com/support.html

github.com/facebook/rocksdb/wiki

help.sap.com/hana

Developer

Apache Software Foundation

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

DataJaguar, Inc.

Facebook, Inc.

SAP

Initial release

2012

2010

2015

2013

2010

Current release

1.20.3, January 2023

3.3 July 2023

8.11.4, April 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL V3.0

Open Source

BSD

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

Erlang

C++

the server part. Clients available in other languages

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

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 SELECT statement is SQL:2003 compliant

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

C++ API
Java API

JDBC
ODBC

Supported programming languages

C++

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

View functions (Map-Reduce) in JavaScript

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Access rights for users can be defined per database

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.