DBMS > 4D vs. CockroachDB vs. ToroDB vs. Vitess

System Properties Comparison 4D vs. CockroachDB vs. ToroDB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Application development environment with integrated database management system

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 MongoDB-compatible JSON document store, built on top of PostgreSQL

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.68
Rank	#110	Overall
	#54	Relational DBMS

Score	6.10
Rank	#58	Overall
	#33	Relational DBMS

Score	1.04
Rank	#191	Overall
	#89	Relational DBMS

Website

www.4d.com

www.cockroachlabs.com

github.com/torodb/server

vitess.io

Technical documentation

developer.4d.com

www.cockroachlabs.com/docs

vitess.io/docs

Developer

4D, Inc

Cockroach Labs

8Kdata

The Linux Foundation, PlanetScale

Initial release

1984

2015

2016

2013

Current release

v20, April 2023

23.1.1, May 2023

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

Open Source

AGPL-V3

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

Java

Server operating systems

OS X
Windows

Linux
macOS
Windows

All OS with a Java 7 VM

Docker
Linux
macOS

Data scheme

yes

dynamic schema

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, 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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

4D proprietary IDE
PHP

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

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

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using RAFT

Source-replica replication

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
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

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

Users and groups

Role-based access control

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

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

Cockroach Labs Deepens Partnership with Google Cloud, CockroachDB Selected to Join Google Distributed Cloud
9 April 2024, Yahoo Finance

provided by Google News

Vitess, the database clustering system powering YouTube, graduates CNCF incubation
5 November 2019, SiliconANGLE News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page