DBMS > Riak KV vs. STSdb vs. XTDB vs. YottaDB

System Properties Comparison Riak KV vs. STSdb vs. XTDB vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed, fault tolerant key-value store

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A general purpose database with bitemporal SQL and Datalog and graph queries

A fast and solid embedded Key-value store

Primary database model

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

Document store

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	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Score	0.18
Rank	#332	Overall
	#46	Document stores

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

Website

github.com/STSSoft/STSdb4

github.com/xtdb/xtdb
www.xtdb.com

yottadb.com

Technical documentation

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

www.xtdb.com/docs

yottadb.com/resources/documentation

Developer

OpenSource, formerly Basho Technologies

STS Soft SC

Juxt Ltd.

YottaDB, LLC

Initial release

2009

2011

2019

2001

Current release

3.2.0, December 2022

4.0.8, September 2015

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

Open Source

MIT License

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

Erlang

Clojure

Server operating systems

Linux
OS X

Windows

All OS with a Java 8 (and higher) VM
Linux

Docker
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

yes, extensible-data-notation format

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

restricted

yes

SQL

Support of SQL

limited SQL, making use of Apache Calcite

by using the Octo plugin

APIs and other access methods

HTTP API
Native Erlang Interface

.NET Client API

HTTP REST
JDBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

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

Clojure
Java

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

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes, each node contains all data

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

yes, using Riak Security

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.

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

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho launches complete NoSQL software kit - DCD
28 May 2015, DatacenterDynamics

provided by Google News

Share this page