DBMS > CockroachDB vs. EDB Postgres vs. SQLite vs. Vitess

System Properties Comparison CockroachDB vs. EDB Postgres vs. SQLite vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

Widely used embeddable, in-process RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Secondary database models

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	1.86
Rank	#131	Overall
	#61	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

www.cockroachlabs.com

www.enterprisedb.com

www.sqlite.org

vitess.io

Technical documentation

www.cockroachlabs.com/docs

www.enterprisedb.com/docs

www.sqlite.org/docs.html

vitess.io/docs

Developer

Cockroach Labs

EnterpriseDB

Dwayne Richard Hipp

The Linux Foundation, PlanetScale

Initial release

2015

2005

2000

2013

Current release

24.1.0, May 2024

14, December 2021

3.46.1 (13 August 2024), August 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

BSD for PostgreSQL-components

Open Source

Public Domain

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

Linux
macOS
Windows

Linux
Windows

server-less

Docker
Linux
macOS

Data scheme

dynamic schema

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.

yes

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

standard with numerous extensions

yes

SQL-92 is not fully supported

yes

with proprietary extensions

APIs and other access methods

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

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

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

proprietary syntax

Triggers

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

horizontal partitioning

by hash, list or range

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

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

fine grained access rights according to SQL-standard

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.