DBMS > Apache IoTDB vs. FatDB vs. Lovefield vs. SQLite vs. TempoIQ

System Properties Comparison Apache IoTDB vs. FatDB vs. Lovefield vs. SQLite vs. TempoIQ

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

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 .NET NoSQL DBMS that can integrate with and extend SQL Server.

Embeddable relational database for web apps written in pure JavaScript

Widely used embeddable, in-process RDBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Time Series DBMS

Document store
Key-value store

Relational DBMS

Time Series DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

google.github.io/lovefield

www.sqlite.org

tempoiq.com (offline)

Technical documentation

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

github.com/google/lovefield/blob/master/docs/spec_index.md

www.sqlite.org/docs.html

Developer

Apache Software Foundation

FatCloud

Google

Dwayne Richard Hipp

TempoIQ

Initial release

2018

2012

2014

2000

2012

Current release

1.1.0, April 2023

2.1.12, February 2017

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

Open Source

Public Domain

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

JavaScript

Server operating systems

All OS with a Java VM (>= 1.8)

Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

server-less

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

Via inetgration in SQL Server

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

JavaScript

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Using read-only observers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

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

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

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, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

yes

Can implement custom security layer via applications

simple authentication-based access control

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.