DBMS > Apache IoTDB vs. Graphite vs. HugeGraph vs. SQLite

System Properties Comparison Apache IoTDB vs. Graphite vs. HugeGraph vs. SQLite

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

A fast-speed and highly-scalable Graph DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Graph DBMS

Relational DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

github.com/graphite-project/graphite-web

github.com/hugegraph
hugegraph.apache.org

www.sqlite.org

Technical documentation

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

graphite.readthedocs.io

hugegraph.apache.org/docs

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Chris Davis

Baidu

Dwayne Richard Hipp

Initial release

2018

2006

2018

2000

Current release

1.1.0, April 2023

0.9

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Python

Java

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
Unix

Linux
macOS
Unix

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

also supports composite index and range index

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

HTTP API
Sockets

Java API
RESTful HTTP API
TinkerPop Gremlin

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

JavaScript (Node.js)
Python

Groovy
Java
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

Server-side scripts

Stored procedures

yes

asynchronous Gremlin script jobs

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

yes

depending on used storage backend, e.g. Cassandra and HBase

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

none

yes

depending on used storage backend, e.g. Cassandra and HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

none

Eventual Consistency

Foreign keys

Referential integrity

yes

edges in graph

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

via file-system locks

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, roles and permissions

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.