DBMS > Badger vs. CouchDB vs. Dragonfly vs. STSdb

System Properties Comparison Badger vs. CouchDB vs. Dragonfly vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store

Document store

Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

github.com/dgraph-io/badger

couchdb.apache.org

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

github.com/STSSoft/STSdb4

Technical documentation

godoc.org/github.com/dgraph-io/badger

docs.couchdb.org/en/stable

www.dragonflydb.io/docs

Developer

DGraph Labs

Apache Software Foundation

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

DragonflyDB team and community contributors

STS Soft SC

Initial release

2017

2005

2023

2011

Current release

3.3.3, December 2023

1.0, March 2023

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

Open Source

BSL 1.1

Open Source

GPLv2, commercial license 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

Erlang

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux

Windows

Data scheme

schema-free

scheme-free

yes

Typing

predefined data types such as float or date

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

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

APIs and other access methods

RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protocol

.NET Client API

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#
Java

Server-side scripts

Stored procedures

View functions in JavaScript

Lua

Triggers

yes

publish/subscribe channels provide some trigger functionality

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual 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

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Couchbase climbs up the DB-Engines Ranking, increasing its popularity by 10% every month
2 June 2014, Matthias Gelbmann

show all

Recent citations in the news

How to install the CouchDB NoSQL database on Debian Server 11
16 June 2022, TechRepublic

IBM Cloudant pulls plan to fund new foundational layer for CouchDB
15 March 2022, The Register

CouchDB 3.0 puts safety first
27 February 2020, InfoWorld

CouchDB 3.0 ends admin party era • DEVCLASS
27 February 2020, DevClass

How to Connect Your Flask App With CouchDB: A NoSQL Database - MUO
14 August 2021, MakeUseOf

provided by Google News

DragonflyDB Announces $21m in New Funding and General Availability
21 March 2023, Business Wire

DragonflyDB reels in $21M for its speedy in-memory database
21 March 2023, SiliconANGLE News

DragonflyDB Raises $21M in Funding
21 March 2023, FinSMEs

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Intel Linux Kernel Optimizations Show Huge Benefit For High Core Count Servers
29 March 2023, Phoronix

provided by Google News

Share this page