DBMS > Riak KV vs. SiteWhere vs. Snowflake vs. Transbase

System Properties Comparison Riak KV vs. SiteWhere vs. Snowflake vs. Transbase

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

Cloud-based data warehousing service for structured and semi-structured data

A resource-optimized, high-performance, universally applicable RDBMS

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	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

github.com/sitewhere/sitewhere

www.snowflake.com

www.transaction.de/en/products/transbase.html

Technical documentation

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

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

Developer

OpenSource, formerly Basho Technologies

SiteWhere

Snowflake Computing Inc.

Transaction Software GmbH

Initial release

2009

2010

2014

1987

Current release

3.2.0, December 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

Open Source

Common Public Attribution License Version 1.0

commercial

free development license

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

C and C++

Server operating systems

Linux
OS X

Linux
OS X
Windows

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

predefined scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

HTTP REST

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

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

JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Erlang

user defined functions

yes

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on HBase

yes

Source-replica replication

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

yes

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.

User concepts

Access control

yes, using Riak Security

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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.