DBMS > Apache IoTDB vs. Rockset vs. Snowflake vs. SQLite vs. Tigris

System Properties Comparison Apache IoTDB vs. Rockset vs. Snowflake vs. SQLite vs. Tigris

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Widely used embeddable, in-process RDBMS

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Time Series DBMS

Document store

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

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.82
Rank	#212	Overall
	#36	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

Technical documentation

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

docs.rockset.com

docs.snowflake.net/manuals/index.html

www.sqlite.org/docs.html

www.tigrisdata.com/docs

Developer

Apache Software Foundation

Rockset

Snowflake Computing Inc.

Dwayne Richard Hipp

Tigris Data, Inc.

Initial release

2018

2019

2014

2000

2022

Current release

1.1.0, April 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Public Domain

Open Source

Apache Version 2.0

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

C++

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

server-less

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

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

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

dynamic typing

yes

not rigid because of 'dynamic typing' concept.

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.

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

Read-only SQL queries, including JOINs

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

HTTP REST

CLI Client
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

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

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

user defined functions

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)

Automatic sharding

yes

none

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

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

yes, using FoundationDB

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

Access rights for users and organizations can be defined via Rockset console

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.