DBMS > Couchbase vs. Riak TS vs. SingleStore

System Properties Comparison Couchbase vs. Riak TS vs. SingleStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	16.74
Rank	#33	Overall
	#5	Document stores

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Website

www.couchbase.com

www.singlestore.com

Technical documentation

docs.couchbase.com

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

docs.singlestore.com

Developer

Couchbase, Inc.

Open Source, formerly Basho Technologies

SingleStore Inc.

Initial release

2011

2015

2013

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.0.0, September 2022

8.5, January 2024

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

commercial

free developer edition 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

C, C++, Go and Erlang

Erlang

C++, Go

Server operating systems

Linux
OS X
Windows

Linux
OS X

Linux

64 bit version required

Data scheme

schema-free

yes

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

yes

restricted

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes, limited

yes

but no triggers and foreign keys

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

HTTP API
Native Erlang Interface

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

Erlang

yes

Triggers

yes

via the TAP protocol

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

selectable replication factor

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets 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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

In-memory capabilities

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

yes

Ephemeral buckets

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Fine grained access control via users, groups and roles

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.