DBMS > CockroachDB vs. EXASOL vs. GeoSpock vs. JaguarDB vs. Snowflake

System Properties Comparison CockroachDB vs. EXASOL vs. GeoSpock vs. JaguarDB vs. Snowflake

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Spatial and temporal data processing engine for extreme data scale

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

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	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.cockroachlabs.com

www.exasol.com

geospock.com

www.jaguardb.com

www.snowflake.com

Technical documentation

www.cockroachlabs.com/docs

www.exasol.com/resources

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Cockroach Labs

Exasol

GeoSpock

DataJaguar, Inc.

Snowflake Computing Inc.

Initial release

2015

2000

2015

2014

Current release

23.1.1, May 2023

2.0, September 2019

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

GPL V3.0

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

Java, Javascript

C++

the server part. Clients available in other languages

Server operating systems

Linux
macOS
Windows

hosted

Linux

hosted

Data scheme

dynamic schema

yes

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

Typing

predefined data types such as float or date

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

temporal, categorical

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

ANSI SQL for query only (using Presto)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

JDBC

.Net
JDBC
ODBC
WebSocket

JDBC

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
Lua
Python
R

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

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

Sharding

Automatic sharding

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

Concurrency

Support for concurrent manipulation of data

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

Access rights for users, groups and roles according to SQL-standard

Access rights for users can be defined per table

rights management via user accounts

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.