DBMS > CockroachDB vs. Kinetica vs. MySQL vs. SQLite

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

Widely used open source RDBMS

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.cockroachlabs.com

www.kinetica.com

www.mysql.com

www.sqlite.org

Technical documentation

www.cockroachlabs.com/docs

docs.kinetica.com

dev.mysql.com/doc

www.sqlite.org/docs.html

Developer

Cockroach Labs

Kinetica

Oracle

since 2010, originally MySQL AB, then Sun

Dwayne Richard Hipp

Initial release

2015

2012

1995

2000

Current release

24.1.0, May 2024

7.1, August 2021

8.4.0, April 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C, C++

C and C++

Server operating systems

Linux
macOS
Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

SQL-like DML and DDL statements

yes

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native 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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

yes

proprietary syntax

Triggers

yes

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

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Source-replica replication

Multi-source replication
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

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

GPU vRAM or System RAM

yes

User concepts

Access control

Role-based access control

Access rights for users and roles on table level

Users with fine-grained authorization concept

no user groups or roles

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.