DBMS > CockroachDB vs. CouchDB vs. SiriDB vs. SQLite

System Properties Comparison CockroachDB vs. CouchDB vs. SiriDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

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

Open Source Time Series DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.cockroachlabs.com

couchdb.apache.org

siridb.com

www.sqlite.org

Technical documentation

www.cockroachlabs.com/docs

docs.couchdb.org/en/stable

docs.siridb.com

www.sqlite.org/docs.html

Developer

Cockroach Labs

Apache Software Foundation

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

Cesbit

Dwayne Richard Hipp

Initial release

2015

2005

2017

2000

Current release

24.1.0, May 2024

3.3.3, December 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Apache version 2

Open Source

MIT 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

Server operating systems

Linux
macOS
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux

server-less

Data scheme

dynamic schema

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data

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, wire compatible with PostgreSQL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

RESTful HTTP/JSON API

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

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

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

improved architecture with release 2.0

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Role-based access control

Access rights for users can be defined per database

simple rights management via user accounts

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.