DBMS > etcd vs. Riak KV vs. Sadas Engine vs. Tkrzw

System Properties Comparison etcd vs. Riak KV vs. Sadas Engine vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed, fault tolerant key-value store

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Key-value store

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

Relational DBMS

Key-value store

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

Score	7.64
Rank	#54	Overall
	#5	Key-value stores

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Score	0.09
Rank	#354	Overall
	#51	Key-value stores

Website

etcd.io
github.com/etcd-io/etcd

www.sadasengine.com

dbmx.net/tkrzw

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

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

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

OpenSource, formerly Basho Technologies

SADAS s.r.l.

Mikio Hirabayashi

Initial release

2009

2006

2020

Current release

3.4, August 2019

3.2.0, December 2022

8.0

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

free trial version available

Open Source

Apache Version 2.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

C++

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux
OS X

AIX
Linux
Windows

Linux
macOS

Data scheme

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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

gRPC
JSON over HTTP

HTTP API
Native Erlang Interface

JDBC
ODBC
Proprietary protocol

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
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

.Net
C
C#
C++
Groovy
Java
PHP
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Erlang

Triggers

yes, watching key changes

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

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

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

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

managed by 'Learn by Usage'

yes

using specific database classes

User concepts

Access control

yes, using Riak Security

Access rights for users, groups and roles according to SQL-standard

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

Monitor Amazon EKS Control Plane metrics using AWS Open Source monitoring services | Amazon Web Services
12 October 2023, AWS Blog

ETCD directives don't go well with RBI's stellar reputation
14 April 2024, Business Standard

Killing a market, softly: How an RBI communique could end India's thriving ETCD market
7 April 2024, The Economic Times

RBI reiterates need for underlying forex exposure for rupee derivatives transactions | Mint
5 April 2024, Mint

RBI defers exchange traded currency derivatives norms
5 April 2024, The Indian Express

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