DBMS > CockroachDB vs. Snowflake vs. SQLite vs. StarRocks

System Properties Comparison CockroachDB vs. Snowflake vs. SQLite vs. StarRocks

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.

Cloud-based data warehousing service for structured and semi-structured data

Widely used embeddable, in-process RDBMS

An open source, high-performance columnar analytical database that enables real-time, multi-dimensional, and highly concurrent data analytics

Forked from Apache Doris

Primary database model

Relational DBMS

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.93
Rank	#198	Overall
	#93	Relational DBMS

Website

www.cockroachlabs.com

www.snowflake.com

www.sqlite.org

www.starrocks.io

Technical documentation

www.cockroachlabs.com/docs

docs.snowflake.net/manuals/index.html

www.sqlite.org/docs.html

docs.starrocks.io/en-us/latest/introduction/StarRocks_intro

Developer

Cockroach Labs

Snowflake Computing Inc.

Dwayne Richard Hipp

The Linux Foundation

since Feb 2023

Initial release

2015

2014

2000

2020

Current release

24.1.0, May 2024

3.46.0 (23 May 2024), May 2024

2.5.3, March 2023

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

Public Domain

Open Source

Apache Version 2.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

C++, Java

Server operating systems

Linux
macOS
Windows

hosted

server-less

Linux

Data scheme

dynamic schema

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

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

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC

CLI Client
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
MySQL protocol

Supported programming languages

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

JavaScript (Node.js)
Python

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

Java

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

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

yes

none

horizontal partitioning (by range and hash)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

yes

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Role based access control and fine grained access rights

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.