DBMS > CockroachDB vs. Cubrid vs. EJDB vs. FatDB

System Properties Comparison CockroachDB vs. Cubrid vs. EJDB vs. FatDB

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.

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Primary database model

Relational DBMS

Document store

Document store
Key-value store

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Website

www.cockroachlabs.com

cubrid.com (korean)
cubrid.org (english)

github.com/Softmotions/ejdb

Technical documentation

www.cockroachlabs.com/docs

cubrid.org/manuals

github.com/Softmotions/ejdb/blob/master/README.md

Developer

Cockroach Labs

CUBRID Corporation, CUBRID Foundation

Softmotions

FatCloud

Initial release

2015

2008

2012

Current release

23.1.1, May 2023

11.0, January 2021

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Apache Version 2.0

Open Source

GPLv2

commercial

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

C, C++, Java

Server operating systems

Linux
macOS
Windows

Linux
Windows

server-less

Windows

Data scheme

dynamic schema

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

Via inetgration in SQL Server

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
OLE DB

in-process shared library

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

Supported programming languages

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

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

via applications

Triggers

yes

via applications

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Source-replica replication

none

selectable replication factor

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

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

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

Netflix, Rightmove, Route, Among Headliners for Next Generation Database User Conference: RoachFest 2024
22 May 2024, PR Newswire

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

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

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

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

provided by Google News

Share this page