DBMS > Apache IoTDB vs. Atos Standard Common Repository vs. SQLite vs. Yaacomo

System Properties Comparison Apache IoTDB vs. Atos Standard Common Repository vs. SQLite vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Yaacomo seems to be discontinued and is 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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Widely used embeddable, in-process RDBMS

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Time Series DBMS

Document store
Key-value store

Relational DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

iotdb.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.sqlite.org

yaacomo.com

Technical documentation

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

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Atos Convergence Creators

Dwayne Richard Hipp

Q2WEB GmbH

Initial release

2018

2016

2000

2009

Current release

1.1.0, April 2023

1703

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Public Domain

commercial

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

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

server-less

Android
Linux
Windows

Data scheme

yes

Schema and schema-less with LDAP views

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

yes

APIs and other access methods

JDBC
Native API

LDAP

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

All languages with LDAP bindings

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

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

cell division

none

horizontal partitioning

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

none

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

Immediate Consistency or Eventual Consistency depending on configuration

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

yes

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

LDAP bind authentication

fine grained access rights according to SQL-standard

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.