DBMS > Apache IoTDB vs. Databricks vs. ObjectBox vs. SQLite

System Properties Comparison Apache IoTDB vs. Databricks vs. ObjectBox 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

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Extremely fast embedded database for small devices, IoT and Mobile

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Document store
Relational DBMS

Object oriented DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	81.08
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	1.29
Rank	#166	Overall
	#5	Object oriented DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

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

docs.databricks.com

docs.objectbox.io

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Databricks

ObjectBox Limited

Dwayne Richard Hipp

Initial release

2018

2013

2017

2000

Current release

1.1.0, April 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache License 2.0

Open Source

Public Domain

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

C and C++

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

Android
iOS
Linux
macOS
Windows

server-less

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

with Databricks SQL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Native API

JDBC
ODBC
RESTful HTTP API

Proprietary native API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Python
R
Scala

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
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

user defined functions and aggregates

Triggers

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

yes

online/offline synchronization between client and server

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

ACID

Concurrency

Support for concurrent manipulation of data

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

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

News

The on-device Vector Database for Android and Java
29 May 2024

Vector search: making sense of search queries
29 May 2024

Python on-device Vector and Object Database for Local AI
28 May 2024

Evolution of search: traditional vs vector search
23 May 2024

On-device Vector Database for Dart/Flutter
21 May 2024

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.