DBMS > CrateDB vs. Riak TS vs. SQLite vs. YottaDB

System Properties Comparison CrateDB vs. Riak TS vs. SQLite vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Database based on Lucene

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

Widely used embeddable, in-process RDBMS

A fast and solid embedded Key-value store

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Time Series DBMS

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

cratedb.com

www.sqlite.org

yottadb.com

Technical documentation

cratedb.com/docs

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

www.sqlite.org/docs.html

yottadb.com/resources/documentation

Developer

Crate

Open Source, formerly Basho Technologies

Dwayne Richard Hipp

YottaDB, LLC

Initial release

2013

2015

2000

2001

Current release

3.0.0, September 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Public Domain

Open Source

AGPL 3.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.

Implementation language

Java

Erlang

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Linux
OS X

server-less

Docker
Linux

Data scheme

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

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

yes, but no triggers and constraints, and PostgreSQL compatibility

yes, limited

yes

SQL-92 is not fully supported

by using the Octo plugin

APIs and other access methods

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

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

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

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

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

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions (Javascript)

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

selectable replication factor

none

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

Foreign keys

Referential integrity

links between datasets can be stored

yes

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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 and groups based on OS-security mechanisms

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.