DBMS > Apache IoTDB vs. Databend vs. Lovefield vs. SQLite

System Properties Comparison Apache IoTDB vs. Databend vs. Lovefield 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

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

Embeddable relational database for web apps written in pure JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Relational DBMS

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

Score	1.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	0.28
Rank	#287	Overall
	#131	Relational DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

github.com/datafuselabs/databend
www.databend.com

google.github.io/lovefield

www.sqlite.org

Technical documentation

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

docs.databend.com

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

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Databend Labs

Google

Dwayne Richard Hipp

Initial release

2018

2021

2014

2000

Current release

1.1.0, April 2023

1.0.59, April 2023

2.1.12, February 2017

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

Apache 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

Rust

JavaScript

Server operating systems

All OS with a Java VM (>= 1.8)

hosted
Linux
macOS

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

tested with Chrome, Firefox, IE, Safari

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

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

yes

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

CLI Client
JDBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Go
Java
JavaScript (Node.js)
Python
Rust

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

Server-side scripts

Stored procedures

yes

Triggers

yes

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

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

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

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Users with fine-grained authorization concept, user 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.