DBMS > CockroachDB vs. FatDB vs. SQLite vs. TiDB

System Properties Comparison CockroachDB vs. FatDB vs. SQLite vs. TiDB

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.

Widely used embeddable, in-process RDBMS

TiDB is an open source distributed SQL database that supports Hybrid Transactional/Analytical Processing (HTAP) workloads. It is MySQL compatible and features horizontal scalability, strong consistency, and high availability.

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	6.10
Rank	#58	Overall
	#33	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Score	4.94
Rank	#72	Overall
	#40	Relational DBMS

Website

www.cockroachlabs.com

www.sqlite.org

pingcap.com

Technical documentation

www.cockroachlabs.com/docs

www.sqlite.org/docs.html

docs.pingcap.com/tidb/stable

Developer

Cockroach Labs

FatCloud

Dwayne Richard Hipp

PingCAP, Inc.

Initial release

2015

2012

2000

2016

Current release

23.1.1, May 2023

3.45.3 (15 April 2024), April 2024

8.0.0, March 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

Public Domain

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.

TiDB Cloud: Fully-managed TiDB Service. Bring everything great about TiDB to the cloud.

Implementation language

Go, Rust

Server operating systems

Linux
macOS
Windows

Windows

server-less

Linux

Data scheme

dynamic schema

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Via inetgration in SQL Server

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GORM
JDBC
ODBC
Proprietary protocol
SQLAlchemy

Supported programming languages

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

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

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

none

horizontal partitioning (by key range)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

selectable replication factor

none

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with TiSpark Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

full support since version 6.6

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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.

yes

User concepts

Access control

Role-based access control

Can implement custom security layer via applications

Fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

TiDB is an advanced open-source, distributed SQL database for modern application...
» more

Competitive advantages

- HORIZONTAL SCALING : TiDB grants total transparency into your data workloads without...
» more

Typical application scenarios

TiDB is ideal for transactional applications that require extreme scalability and...
» more

Key customers

Block, Pinterest, Catalyst, Bolt, Flipkart, Capcom, Shopee (E-commerce), JD Cloud...
» more

Market metrics

34K+ GitHub stars 5K+ members in TiDB Community Slack 1K+ community contributors...
» more

Licensing and pricing models

TiDB Community : Free open source software (Apache 2.0) TiDB Self-Hosted : Enterprise...
» more

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.