DBMS > Datomic vs. Riak KV vs. STSdb vs. TerarkDB

System Properties Comparison Datomic vs. Riak KV vs. STSdb vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Distributed, fault tolerant key-value store

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Key-value store

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

Key-value store

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.datomic.com

github.com/STSSoft/STSdb4

github.com/bytedance/terarkdb

Technical documentation

docs.datomic.com

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Cognitect

OpenSource, formerly Basho Technologies

STS Soft SC

ByteDance, originally Terark

Initial release

2012

2009

2011

2016

Current release

1.0.6735, June 2023

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

commercial

restricted open source version 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, Clojure

Erlang

C++

Server operating systems

All OS with a Java VM

Linux
OS X

Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

.NET Client API

C++ API
Java API

Supported programming languages

Clojure
Java

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

C++
Java

Server-side scripts

Stored procedures

yes

Transaction Functions

Erlang

Triggers

By using transaction functions

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

yes, using Riak Security

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

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Zoona Case Study
16 December 2017, AWS Blog

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Nubank acquires US company; PayPal studies cryptocurrencies
24 July 2020, iupana.com

provided by Google News

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

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

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page