DBMS > CockroachDB vs. FatDB vs. GeoSpock vs. OpenTSDB vs. Snowflake

System Properties Comparison CockroachDB vs. FatDB vs. GeoSpock vs. OpenTSDB vs. Snowflake

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Spatial and temporal data processing engine for extreme data scale

Scalable Time Series DBMS based on HBase

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

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Time Series 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.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.cockroachlabs.com

geospock.com

opentsdb.net

www.snowflake.com

Technical documentation

www.cockroachlabs.com/docs

opentsdb.net/docs/build/html/index.html

docs.snowflake.net/manuals/index.html

Developer

Cockroach Labs

FatCloud

GeoSpock

currently maintained by Yahoo and other contributors

Snowflake Computing Inc.

Initial release

2015

2012

2011

2014

Current release

24.1.0, May 2024

2.0, September 2019

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

LGPL

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

Java

Server operating systems

Linux
macOS
Windows

Windows

hosted

Linux
Windows

hosted

Data scheme

dynamic schema

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

Via inetgration in SQL Server

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC

HTTP API
Telnet API

CLI Client
JDBC
ODBC

Supported programming languages

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

Erlang
Go
Java
Python
R
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via applications

user defined functions

Triggers

yes

via applications

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

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

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.

User concepts

Access control

Role-based access control

Can implement custom security layer via applications

Access rights for users can be defined per table

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.