DBMS > Riak KV vs. SiteWhere vs. SQLite vs. SQream DB

System Properties Comparison Riak KV vs. SiteWhere vs. SQLite vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed, fault tolerant key-value store

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Key-value store

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

Time Series DBMS

Relational DBMS

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

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

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

github.com/sitewhere/sitewhere

www.sqlite.org

sqream.com

Technical documentation

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

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

docs.sqream.com

Developer

OpenSource, formerly Basho Technologies

SiteWhere

Dwayne Richard Hipp

SQream Technologies

Initial release

2009

2010

2000

2017

Current release

3.2.0, December 2022

3.46.0 (23 May 2024), May 2024

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

commercial

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

Java

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux
OS X

Linux
OS X
Windows

server-less

Linux

Data scheme

schema-free

predefined scheme

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes, ANSI Standard SQL 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

restricted

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

HTTP API
Native Erlang Interface

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net
JDBC
ODBC

Supported programming languages

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

user defined functions in Python

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

based on HBase

none

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.