DBMS > CockroachDB vs. Dragonfly vs. Linter vs. Snowflake

System Properties Comparison CockroachDB vs. Dragonfly vs. Linter vs. Snowflake

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 drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

RDBMS for high security requirements

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

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

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.49
Rank	#261	Overall
	#38	Key-value stores

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.cockroachlabs.com

github.com/dragonflydb/dragonfly
www.dragonflydb.io

linter.ru

www.snowflake.com

Technical documentation

www.cockroachlabs.com/docs

www.dragonflydb.io/docs

docs.snowflake.net/manuals/index.html

Developer

Cockroach Labs

DragonflyDB team and community contributors

relex.ru

Snowflake Computing Inc.

Initial release

2015

2023

1990

2014

Current release

24.1.0, May 2024

1.0, March 2023

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

BSL 1.1

commercial

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++

C and C++

Server operating systems

Linux
macOS
Windows

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

Data scheme

dynamic schema

scheme-free

yes

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

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

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

APIs and other access methods

JDBC

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax with the possibility to convert from PL/SQL

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

yes

similar concept for controling cloud resources

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

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

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

Password-based authentication

fine grained access rights according to SQL-standard

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

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.