DBMS > Badger vs. CouchDB vs. Dgraph vs. H2 vs. SQLite

System Properties Comparison Badger vs. CouchDB vs. Dgraph vs. H2 vs. SQLite

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.

Distributed and scalable native Graph DBMS

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

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

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/dgraph-io/badger

Technical documentation

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

docs.couchdb.org/en/stable

dgraph.io/docs

www.h2database.com/html/main.html

www.sqlite.org/docs.html

Developer

DGraph Labs

Apache Software Foundation

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

Dgraph Labs, Inc.

Thomas Mueller

Dwayne Richard Hipp

Initial release

2017

2005

2016

2005

2000

Current release

3.3.3, December 2023

2.2.220, July 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

Erlang

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

All OS with a Java VM

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

via views

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP/JSON API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

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

Java

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

View functions in JavaScript

Java Stored Procedures and User-Defined Functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Synchronous replication via Raft

With clustering: 2 database servers on different computers operate on identical copies of a database

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

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

Planned for future releases

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.