DBMS > CockroachDB vs. Dragonfly vs. Oracle Coherence vs. RocksDB

System Properties Comparison CockroachDB vs. Dragonfly vs. Oracle Coherence vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Oracles in-memory data grid solution

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

Primary database model

Relational DBMS

Key-value store

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

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

Website

www.cockroachlabs.com

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

www.oracle.com/java/coherence

rocksdb.org

Technical documentation

www.cockroachlabs.com/docs

www.dragonflydb.io/docs

docs.oracle.com/en/middleware/standalone/coherence

github.com/facebook/rocksdb/wiki

Developer

Cockroach Labs

DragonflyDB team and community contributors

Oracle

Facebook, Inc.

Initial release

2015

2023

2007

2013

Current release

24.1.0, May 2024

1.0, March 2023

14.1, August 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

BSL 1.1

commercial

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

Java

C++

Server operating systems

Linux
macOS
Windows

Linux

All OS with a Java VM

Linux

Data scheme

dynamic schema

scheme-free

schema-free

Typing

predefined data types such as float or date

yes

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

yes, wire compatible with PostgreSQL

APIs and other access methods

JDBC

Proprietary protocol

RESP - REdis Serialization Protocol

JCache
JPA
RESTful HTTP API

C++ API
Java API

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

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

.Net
C++
Java

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Lua

Triggers

publish/subscribe channels provide some trigger functionality

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Source-replica replication

yes, with selectable consistency level

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

configurable

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

optionally

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

Role-based access control

Password-based authentication

authentification to access the cache via certificates or http basic authentication

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.