DBMS > IBM Cloudant vs. Riak KV vs. SiteWhere vs. STSdb

System Properties Comparison IBM Cloudant vs. Riak KV vs. SiteWhere vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Distributed, fault tolerant key-value store

M2M integration platform for persisting/querying time series data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store

Key-value store

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

Time Series DBMS

Key-value store

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

Score	2.73
Rank	#108	Overall
	#20	Document stores

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

Score	0.06
Rank	#367	Overall
	#36	Time Series DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

www.ibm.com/products/cloudant

github.com/sitewhere/sitewhere

github.com/STSSoft/STSdb4

Technical documentation

cloud.ibm.com/docs/Cloudant

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

sitewhere1.sitewhere.io/index.html

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

OpenSource, formerly Basho Technologies

SiteWhere

STS Soft SC

Initial release

2010

2009

2010

2011

Current release

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

Common Public Attribution License Version 1.0

Open Source

GPLv2, commercial license available

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

Java

Server operating systems

hosted

Linux
OS X

Linux
OS X
Windows

Windows

Data scheme

schema-free

predefined scheme

yes

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/JSON API

HTTP API
Native Erlang Interface

HTTP REST

.NET Client API

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

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"

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate 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

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

User concepts

Access control

Access rights for users can be defined per database

yes, using Riak Security

Users with fine-grained authorization concept

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

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, ibm.com

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, ibm.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

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

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page