DBMS > Apache IoTDB vs. FoundationDB vs. MySQL

System Properties Comparison Apache IoTDB vs. FoundationDB vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the 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

Ordered key-value store. Core features are complimented by layers.

Widely used open source RDBMS

Primary database model

Time Series DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

iotdb.apache.org

github.com/apple/foundationdb

www.mysql.com

Technical documentation

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

apple.github.io/foundationdb

dev.mysql.com/doc

Developer

Apache Software Foundation

FoundationDB

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2018

2013

1995

Current release

1.1.0, April 2023

6.2.28, November 2020

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++

C and C++

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

some layers support schemas

yes

Typing

predefined data types such as float or date

yes

some layers support typing

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

supported in specific SQL layer only

yes

with proprietary extensions

APIs and other access methods

JDBC
Native API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

in SQL-layer only

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

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

Multi-source replication
Source-replica replication

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

Linearizable consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 with fine-grained authorization concept

no user groups or 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.