DBMS > Apache IoTDB vs. Infobright vs. Snowflake vs. TimesTen

System Properties Comparison Apache IoTDB vs. Infobright vs. Snowflake vs. TimesTen

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

In-Memory RDBMS compatible to Oracle

Primary database model

Time Series DBMS

Relational DBMS

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

iotdb.apache.org

ignitetech.com/softwarelibrary/infobrightdb

www.snowflake.com

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

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

docs.snowflake.net/manuals/index.html

docs.oracle.com/database/timesten-18.1

Developer

Apache Software Foundation

Ignite Technologies Inc.; formerly InfoBright Inc.

Snowflake Computing Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2018

2005

2014

1998

Current release

1.1.0, April 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Java

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data 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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Native API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

user defined functions

PL/SQL

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

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

none

yes

none

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

Source-replica replication

yes

Multi-source replication
Source-replica replication

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

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.