DBMS > Dragonfly vs. IBM Cloudant vs. JaguarDB vs. SAP HANA

System Properties Comparison Dragonfly vs. IBM Cloudant vs. JaguarDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Database as a Service offering based on Apache CouchDB

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Key-value store

Document store

Key-value store
Vector DBMS

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	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	2.68
Rank	#106	Overall
	#20	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/dragonflydb/dragonfly
www.dragonflydb.io

www.ibm.com/products/cloudant

www.jaguardb.com

www.sap.com/products/hana.html

Technical documentation

www.dragonflydb.io/docs

cloud.ibm.com/docs/Cloudant

www.jaguardb.com/support.html

help.sap.com/hana

Developer

DragonflyDB team and community contributors

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

DataJaguar, Inc.

SAP

Initial release

2023

2010

2015

2010

Current release

1.0, March 2023

3.3 July 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

BSL 1.1

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

C++

Erlang

C++

the server part. Clients available in other languages

Server operating systems

Linux

hosted

Linux

Appliance or cloud-service

Data scheme

scheme-free

schema-free

yes

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

Lua

View functions (Map-Reduce) in JavaScript

SQLScript, R

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Optimistic 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

Password-based authentication

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.