DBMS > CockroachDB vs. FatDB vs. Google Cloud Firestore vs. Hazelcast vs. MySQL

System Properties Comparison CockroachDB vs. FatDB vs. Google Cloud Firestore vs. Hazelcast vs. MySQL

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.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

A widely adopted in-memory data grid

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

www.cockroachlabs.com

firebase.google.com/products/firestore

hazelcast.com

www.mysql.com

Technical documentation

www.cockroachlabs.com/docs

firebase.google.com/docs/firestore

hazelcast.org/imdg/docs

dev.mysql.com/doc

Developer

Cockroach Labs

FatCloud

Google

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

2012

2017

2008

1995

Current release

24.1.0, May 2024

5.3.6, November 2023

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

C and C++

Server operating systems

Linux
macOS
Windows

Windows

hosted

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

Via inetgration in SQL Server

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC

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

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

yes, Firebase Rules & Cloud Functions

yes

Event Listeners, Executor Services

yes

proprietary syntax

Triggers

yes

via applications

yes, with Cloud Functions

yes

Events

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

selectable replication factor

Multi-source replication

yes

Replicated Map

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

one or two-phase-commit; repeatable reads; read commited

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Can implement custom security layer via applications

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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.