DBMS > Apache IoTDB vs. SiteWhere vs. Snowflake vs. Splunk

System Properties Comparison Apache IoTDB vs. SiteWhere vs. Snowflake vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

M2M integration platform for persisting/querying time series data

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

Analytics Platform for Big Data

Primary database model

Time Series DBMS

Relational DBMS

Search engine

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

iotdb.apache.org

github.com/sitewhere/sitewhere

www.snowflake.com

www.splunk.com

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

SiteWhere

Snowflake Computing Inc.

Splunk Inc.

Initial release

2018

2010

2014

2003

Current release

1.1.0, April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Common Public Attribution License Version 1.0

commercial

Limited free edition and free developer edition 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

Java

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

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

yes

SQL

Support of SQL

SQL-like query language

yes

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
Native API

HTTP REST

CLI Client
JDBC
ODBC

HTTP REST

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

JavaScript (Node.js)
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

based on HBase

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

selectable replication factor

based on HBase

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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.

yes

User concepts

Access control

yes

Users with fine-grained authorization concept

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

Access rights for users and roles

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.