DBMS > Apache IoTDB vs. Interbase vs. Snowflake vs. Titan

System Properties Comparison Apache IoTDB vs. Interbase vs. Snowflake vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

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

Light-weight proven RDBMS

originally from Borland

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

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Time Series DBMS

Relational DBMS

Graph DBMS

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

iotdb.apache.org

www.embarcadero.com/products/interbase

www.snowflake.com

github.com/thinkaurelius/titan

Technical documentation

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

docs.embarcadero.com/products/interbase

docs.snowflake.net/manuals/index.html

github.com/thinkaurelius/titan/wiki

Developer

Apache Software Foundation

Embarcadero

Snowflake Computing Inc.

Aurelius, owned by DataStax

Initial release

2018

1984

2014

2012

Current release

1.1.0, April 2023

InterBase 2020, December 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache license, 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

Server operating systems

All OS with a Java VM (>= 1.8)

Android
iOS
Linux
OS X
Windows

hosted

Linux
OS X
Unix
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.

export as XML data possible

yes

Secondary indexes

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

JavaScript (Node.js)
Python

Clojure
Java
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

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)

none

yes

via pluggable storage backends

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

Interbase Change Views

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

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

User authentification and security via Rexster Graph Server

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.