DBMS > CouchDB vs. Dragonfly vs. RocksDB vs. VelocityDB

System Properties Comparison CouchDB vs. Dragonfly vs. RocksDB vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Document store

Key-value store

Graph DBMS
Object oriented DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

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

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

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

couchdb.apache.org

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

rocksdb.org

velocitydb.com

Technical documentation

docs.couchdb.org/en/stable

www.dragonflydb.io/docs

github.com/facebook/rocksdb/wiki

velocitydb.com/UserGuide

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

DragonflyDB team and community contributors

Facebook, Inc.

VelocityDB Inc

Initial release

2005

2023

2013

2011

Current release

3.3.3, December 2023

1.0, March 2023

9.2.1, May 2024

7.x

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

BSL 1.1

Open Source

BSD

commercial

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

Erlang

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux

Any that supports .NET

Data scheme

schema-free

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

via views

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protocol

C++ API
Java API

.Net

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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++
Go
Java
Perl
Python
Ruby

.Net

Server-side scripts

Stored procedures

View functions in JavaScript

Lua

Triggers

yes

publish/subscribe channels provide some trigger functionality

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica 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

Transaction concepts

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

atomic operations within a single document possible

Atomic execution of command blocks and scripts

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

User concepts

Access control

Access rights for users can be defined per database

Password-based authentication

Based on Windows 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.