DBMS > CockroachDB vs. FatDB vs. Infobright vs. Lovefield

System Properties Comparison CockroachDB vs. FatDB vs. Infobright vs. Lovefield

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.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Website

www.cockroachlabs.com

ignitetech.com/softwarelibrary/infobrightdb

google.github.io/lovefield

Technical documentation

www.cockroachlabs.com/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Cockroach Labs

FatCloud

Ignite Technologies Inc.; formerly InfoBright Inc.

Google

Initial release

2015

2012

2005

2014

Current release

23.1.1, May 2023

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

Apache 2.0

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

JavaScript

Server operating systems

Linux
macOS
Windows

Windows

Linux
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

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.

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

Via inetgration in SQL Server

yes

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JDBC

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

ADO.NET
JDBC
ODBC

Supported programming languages

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Using read-only observers

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

selectable replication factor

Source-replica replication

none

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

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

User concepts

Access control

Role-based access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

Recent citations in the news

CockroachDB 23.2 Enhances Enterprise Architectures with Improved Postgres Compatibility and Built-in Resilience
18 January 2024, PR Newswire

CockroachDB tempts legacy databases to crawl into the cloud age
29 January 2024, The Register

How to Unlock Real-Time Data Streams with CockroachDB and Amazon MSK | Amazon Web Services
6 November 2023, AWS Blog

How DoorDash Migrated from Aurora Postgres to CockroachDB
5 December 2023, The New Stack

CockroachDB's Latest Enhancements Focus on Resilience
18 January 2024, Database Trends and Applications

provided by Google News

Share this page