DBMS > Newts vs. Riak KV vs. SiteWhere vs. XTDB

System Properties Comparison Newts vs. Riak KV vs. SiteWhere vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS based on Cassandra

Distributed, fault tolerant key-value store

M2M integration platform for persisting/querying time series data

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Time Series DBMS

Key-value store

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

Time Series DBMS

Document store

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

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

opennms.github.io/newts

github.com/sitewhere/sitewhere

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

github.com/OpenNMS/newts/wiki

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

sitewhere1.sitewhere.io/index.html

www.xtdb.com/docs

Developer

OpenNMS Group

OpenSource, formerly Basho Technologies

SiteWhere

Juxt Ltd.

Initial release

2014

2009

2010

2019

Current release

3.2.0, December 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

Common Public Attribution License Version 1.0

Open Source

MIT License

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

Erlang

Java

Clojure

Server operating systems

Linux
OS X
Windows

Linux
OS X

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

predefined scheme

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

HTTP REST
Java API

HTTP API
Native Erlang Interface

HTTP REST

HTTP REST
JDBC

Supported programming languages

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

Clojure
Java

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

no "single point of failure"

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

selectable replication factor

based on HBase

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

User concepts

Access control

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

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

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

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Basho Advances NoSQL Riak Enterprise 2.0 With Search, Advanced Data Types
15 September 2014, Data Center Knowledge

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Ten Popular IoT Platforms You Should be Aware of
27 March 2023, Open Source For You

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

provided by Google News

Share this page