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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source Time Series DBMS and monitoring system

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

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

Relational DBMS

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

Score	7.56
Rank	#49	Overall
	#3	Time Series DBMS

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

Website

prometheus.io

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

prometheus.io/docs

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

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

OpenSource, formerly Basho Technologies

SiteWhere

Snowflake Computing Inc.

Initial release

2015

2009

2010

2014

Current release

3.2.0, December 2022

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

commercial

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

Linux
Windows

Linux
OS X

Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

predefined scheme

yes

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

Typing

predefined data types such as float or date

Numeric data only

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.

Import of XML data possible

yes

Secondary indexes

restricted

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

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

yes

by Federation

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

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

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.