DBMS > Badger vs. CockroachDB vs. Datomic vs. SQLite

System Properties Comparison Badger vs. CockroachDB vs. Datomic 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.

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.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Relational DBMS

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

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/dgraph-io/badger

www.cockroachlabs.com

www.datomic.com

www.sqlite.org

Technical documentation

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

www.cockroachlabs.com/docs

docs.datomic.com

www.sqlite.org/docs.html

Developer

DGraph Labs

Cockroach Labs

Cognitect

Dwayne Richard Hipp

Initial release

2017

2015

2012

2000

Current release

24.1.0, May 2024

1.0.6735, June 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

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

Java, Clojure

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

All OS with a Java VM

server-less

Data scheme

schema-free

dynamic schema

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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

Clojure
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

yes

Transaction Functions

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

none

But extensive use of caching in the application peers

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using RAFT

none

But extensive use of caching in the application peers

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Role-based access control

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.