DBMS > Apache IoTDB vs. etcd vs. HarperDB vs. SQLite

System Properties Comparison Apache IoTDB vs. etcd vs. HarperDB 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

A distributed reliable key-value store

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

etcd.io
github.com/etcd-io/etcd

www.harperdb.io

www.sqlite.org

Technical documentation

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

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.harperdb.io/docs

www.sqlite.org/docs.html

Developer

Apache Software Foundation

HarperDB

Dwayne Richard Hipp

Initial release

2018

2017

2000

Current release

1.1.0, April 2023

3.4, August 2019

3.1, August 2021

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

commercial

free community edition available

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

Node.js

Server operating systems

All OS with a Java VM (>= 1.8)

FreeBSD
Linux
Windows

experimental

Linux
OS X

server-less

Data scheme

yes

schema-free

dynamic schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL

Support of SQL

SQL-like query language

SQL-like data manipulation statements

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

gRPC
JSON over HTTP

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

Custom Functions

since release 3.1

Triggers

yes

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

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

A table resides as a whole on one (or more) nodes in a cluster

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

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

the nodes on which a table resides can be defined

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

yes, using LMDB

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

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.