DBMS > CockroachDB vs. Google Cloud Spanner vs. OpenTSDB vs. SQLite

System Properties Comparison CockroachDB vs. Google Cloud Spanner vs. OpenTSDB 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 horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Scalable Time Series DBMS based on HBase

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	2.69
Rank	#101	Overall
	#51	Relational DBMS

Score	1.59
Rank	#140	Overall
	#12	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.cockroachlabs.com

cloud.google.com/spanner

opentsdb.net

www.sqlite.org

Technical documentation

www.cockroachlabs.com/docs

cloud.google.com/spanner/docs

opentsdb.net/docs/build/html/index.html

www.sqlite.org/docs.html

Developer

Cockroach Labs

Google

currently maintained by Yahoo and other contributors

Dwayne Richard Hipp

Initial release

2015

2017

2011

2000

Current release

24.1.0, May 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

LGPL

Open Source

Public Domain

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

Java

Server operating systems

Linux
macOS
Windows

hosted

Linux
Windows

server-less

Data scheme

dynamic schema

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

Query statements complying to ANSI 2011

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

HTTP API
Telnet 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

Go
Java
JavaScript (Node.js)
Python

Erlang
Go
Java
Python
R
Ruby

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

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

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication with 3 replicas for regional instances.

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

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

ACID

Strict serializable isolation

ACID

Concurrency

Support for concurrent manipulation of data

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.