DBMS > Dragonfly vs. Heroic vs. IBM Db2 vs. Oracle

System Properties Comparison Dragonfly vs. Heroic vs. IBM Db2 vs. Oracle

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Common in IBM host environments, 2 different versions for host and Windows/Linux

Widely used RDBMS

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.42
Rank	#271	Overall
	#38	Key-value stores

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	127.49
Rank	#8	Overall
	#5	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Website

github.com/dragonflydb/dragonfly
www.dragonflydb.io

github.com/spotify/heroic

www.ibm.com/products/db2

www.oracle.com/database

Technical documentation

www.dragonflydb.io/docs

spotify.github.io/heroic

www.ibm.com/docs/en/db2

docs.oracle.com/en/database

Developer

DragonflyDB team and community contributors

Spotify

IBM

Oracle

Initial release

2023

2014

1983

host version

1980

Current release

1.0, March 2023

12.1, October 2016

23c, September 2023

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache 2.0

commercial

free version is available

commercial

restricted free version is available

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++

Java

C and C++

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows
z/OS

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

scheme-free

schema-free

yes

Schemaless in JSON and XML columns

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

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
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

Lua

yes

PL/SQL

also stored procedures in Java possible

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

with separate tools (MQ, InfoSphere)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate 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

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Password-based authentication

fine grained access rights according to SQL-standard

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.