DBMS > CrateDB vs. PlanetScale vs. Riak TS vs. RocksDB

System Properties Comparison CrateDB vs. PlanetScale vs. Riak TS vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Database based on Lucene

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Time Series DBMS

Key-value store

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.71
Rank	#227	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#10	Vector DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

cratedb.com

planetscale.com

rocksdb.org

Technical documentation

cratedb.com/docs

planetscale.com/docs

www.tiot.jp/riak-docs/riak/ts/latest

github.com/facebook/rocksdb/wiki

Developer

Crate

PlanetScale

Open Source, formerly Basho Technologies

Facebook, Inc.

Initial release

2013

2020

2015

2013

Current release

3.0.0, September 2022

9.2.1, May 2024

License

Commercial or Open Source

Open Source

commercial

Open Source

BSD

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

Java

Erlang

C++

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Docker
Linux
macOS

Linux
OS X

Linux

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

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

restricted

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

with proprietary extensions

yes, limited

APIs and other access methods

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions (Javascript)

yes

proprietary syntax

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

Multi-source replication
Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Read-after-write consistency on record level

Eventual Consistency across shards
Immediate Consistency within a shard

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

links between datasets can be stored

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

ACID at shard level

yes

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

User concepts

Access control

rights management via user accounts

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.