DBMS > CockroachDB vs. Kinetica vs. Lovefield vs. SQLite

System Properties Comparison CockroachDB vs. Kinetica vs. Lovefield 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.

Fully vectorized database across both GPUs and CPUs

Embeddable relational database for web apps written in pure JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.cockroachlabs.com

www.kinetica.com

google.github.io/lovefield

www.sqlite.org

Technical documentation

www.cockroachlabs.com/docs

docs.kinetica.com

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

www.sqlite.org/docs.html

Developer

Cockroach Labs

Kinetica

Google

Dwayne Richard Hipp

Initial release

2015

2012

2014

2000

Current release

24.1.0, May 2024

7.1, August 2021

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

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

C, C++

JavaScript

Server operating systems

Linux
macOS
Windows

Linux

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

tested with Chrome, Firefox, IE, Safari

server-less

Data scheme

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

SQL-like DML and DDL statements

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

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

C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

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

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

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

GPU vRAM or System RAM

yes

using MemoryDB

yes

User concepts

Access control

Role-based access control

Access rights for users and roles on table level

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.