DBMS > etcd vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. Riak TS

System Properties Comparison etcd vs. Machbase Neo vs. Microsoft Azure Cosmos DB vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

TimeSeries DBMS for AIoT and BigData

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Key-value store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

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

Score	0.22
Rank	#324	Overall
	#29	Time Series DBMS

Score	29.85
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.25
Rank	#308	Overall
	#26	Time Series DBMS

Website

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

machbase.com

azure.microsoft.com/services/cosmos-db

Technical documentation

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

machbase.com/dbms

learn.microsoft.com/azure/cosmos-db

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

Developer

Machbase

Microsoft

Open Source, formerly Basho Technologies

Initial release

2013

2014

2015

Current release

3.4, August 2019

V8.0, August 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free test version available

commercial

Open Source

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

Erlang

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux
macOS
Windows

hosted

Linux
OS X

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

restricted

SQL

Support of SQL

SQL-like query language

yes, limited

APIs and other access methods

gRPC
JSON over HTTP

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Server-side scripts

Stored procedures

JavaScript

Erlang

Triggers

yes, watching key changes

JavaScript

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

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

yes

Implicit feature of the cloud service

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

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

volatile and lookup table

User concepts

Access control

simple password-based access control

Access rights can be defined down to the item level

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.