DBMS > CockroachDB vs. FatDB vs. PostGIS vs. VoltDB

System Properties Comparison CockroachDB vs. FatDB vs. PostGIS vs. VoltDB

Please select another system to include it in the comparison.

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.

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 extension of PostgreSQL

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store
Key-value store

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

www.cockroachlabs.com

postgis.net

www.voltdb.com

Technical documentation

www.cockroachlabs.com/docs

postgis.net/documentation

docs.voltdb.com

Developer

Cockroach Labs

FatCloud

VoltDB Inc.

Initial release

2015

2012

2005

2010

Current release

24.1.0, May 2024

3.4.2, February 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

GPL v2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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.

Implementation language

Java, C++

Server operating systems

Linux
macOS
Windows

Windows

Linux
OS X

for development

Data scheme

dynamic schema

schema-free

yes

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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

Via inetgration in SQL Server

yes

only a subset of SQL 99

APIs and other access methods

JDBC

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

user defined functions

Java

Triggers

yes

via applications

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

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

selectable replication factor

yes

based on PostgreSQL

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

yes

based on PostgreSQL

Users and roles with access to stored procedures

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Cockroach Labs shakes up its licensing to force bigger companies to pay
15 August 2024, TechCrunch

CockroachDB scuttles away from open source Core offering
19 August 2024, The Register

CockroachDB retires self-hosted Core offering, makes Enterprise version free for companies under $10M in annual revenue
15 August 2024, SDTimes.com

Cockroach Labs Deepens Partnership with Google Cloud, CockroachDB Selected to Join Google Distributed Cloud
9 April 2024, PR Newswire

DoorDash Uses CockroachDB to Create Config Management Platform for Microservices
14 February 2024, InfoQ.com

provided by Google News

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

Unveiling Volt Active Data’s game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Aims for Fast Big Data Development
29 January 2015, ADT Magazine

VoltDB Announces Key New Hires
26 October 2021, citybiz

Solutions Review Sits Down with VoltDB CEO David Flower
17 April 2018, Solutions Review

provided by Google News

Share this page