DBMS > CockroachDB vs. Cubrid vs. PlanetScale vs. Tkrzw

System Properties Comparison CockroachDB vs. Cubrid vs. PlanetScale vs. Tkrzw

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.

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

www.cockroachlabs.com

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

planetscale.com

dbmx.net/tkrzw

Technical documentation

www.cockroachlabs.com/docs

cubrid.org/manuals

planetscale.com/docs

Developer

Cockroach Labs

CUBRID Corporation, CUBRID Foundation

PlanetScale

Mikio Hirabayashi

Initial release

2015

2008

2020

Current release

24.1.0, May 2024

11.0, January 2021

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++, Java

C++

Server operating systems

Linux
macOS
Windows

Linux
Windows

Docker
Linux
macOS

Linux
macOS

Data scheme

dynamic schema

yes

schema-free

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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

with proprietary extensions

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
MySQL protocol
ODBC

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

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

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Source-replica replication

Multi-source replication
Source-replica replication

none

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

Immediate Consistency

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

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

using specific database classes

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.

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

Cockroach Labs Deepens Partnership with Google Cloud, CockroachDB Selected to Join Google Distributed Cloud
9 April 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

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

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

provided by Google News

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

PlanetScale Named to Fortune 2023 Best Small Workplaces
31 August 2023, Business Wire

How to Migrate to PlanetScale's Serverless Database
14 October 2021, The New Stack

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

provided by Google News

Share this page