DBMS > CockroachDB vs. IBM Cloudant vs. Lovefield vs. SQLite vs. YottaDB

System Properties Comparison CockroachDB vs. IBM Cloudant vs. Lovefield vs. SQLite vs. YottaDB

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.

Database as a Service offering based on Apache CouchDB

Embeddable relational database for web apps written in pure JavaScript

Widely used embeddable, in-process RDBMS

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

www.cockroachlabs.com

www.ibm.com/products/cloudant

google.github.io/lovefield

www.sqlite.org

yottadb.com

Technical documentation

www.cockroachlabs.com/docs

cloud.ibm.com/docs/Cloudant

github.com/google/lovefield/blob/master/docs/spec_index.md

www.sqlite.org/docs.html

yottadb.com/resources/documentation

Developer

Cockroach Labs

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Google

Dwayne Richard Hipp

YottaDB, LLC

Initial release

2015

2010

2014

2000

2001

Current release

24.1.0, May 2024

2.1.12, February 2017

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

JavaScript

Server operating systems

Linux
macOS
Windows

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

server-less

Docker
Linux

Data scheme

dynamic schema

schema-free

yes

dynamic column types

schema-free

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

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

by using the Octo plugin

APIs and other access methods

JDBC

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Triggers

yes

Using read-only observers

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

none

yes

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

via file-system locks

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Role-based access control

Access rights for users can be defined per database

Users and groups based on OS-security mechanisms

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.