DBMS > Badger vs. Dragonfly vs. Quasardb vs. SQLite

System Properties Comparison Badger vs. Dragonfly vs. Quasardb vs. SQLite

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 drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Distributed, high-performance timeseries database

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

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

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/dgraph-io/badger

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

quasar.ai

www.sqlite.org

Technical documentation

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

www.dragonflydb.io/docs

doc.quasar.ai/master

www.sqlite.org/docs.html

Developer

DGraph Labs

DragonflyDB team and community contributors

quasardb

Dwayne Richard Hipp

Initial release

2017

2023

2009

2000

Current release

1.0, March 2023

3.14.1, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSL 1.1

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Public Domain

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

BSD
Linux
OS X
Windows

server-less

Data scheme

schema-free

scheme-free

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

yes

integer and binary

yes

not rigid because of 'dynamic typing' concept.

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

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Lua

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

via file-system locks

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Password-based authentication

Cryptographically strong user authentication and audit trail

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.