DBMS > Apache IoTDB vs. Atos Standard Common Repository vs. DataFS vs. GeoMesa

System Properties Comparison Apache IoTDB vs. Atos Standard Common Repository vs. DataFS vs. GeoMesa

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.

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

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Primary database model

Time Series DBMS

Document store
Key-value store

Object oriented DBMS

Spatial DBMS

Secondary database models

Graph 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.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Website

iotdb.apache.org

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

newdatabase.com

www.geomesa.org

Technical documentation

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

dev.mobiland.com/Overview.xsp

www.geomesa.org/documentation/stable/user/index.html

Developer

Apache Software Foundation

Atos Convergence Creators

Mobiland AG

CCRi and others

Initial release

2018

2016

2018

2014

Current release

1.1.0, April 2023

1703

1.1.263, October 2022

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache License 2.0

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

Scala

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

Windows

Data scheme

yes

Schema and schema-less with LDAP views

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

yes

Typing

predefined data types such as float or date

yes

optional

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

APIs and other access methods

JDBC
Native API

LDAP

.NET Client API
Proprietary client DLL
WinRT client

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

All languages with LDAP bindings

.Net
C
C#
C++
VB.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

no, except callback-events from server when changes happened

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

cell division

Proprietary Sharding system

depending on storage layer

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

depending on storage layer

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

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

depending on storage layer

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

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

depending on storage layer

User concepts

Access control

yes

LDAP bind authentication

Windows-Profile

yes

depending on the DBMS used for storage

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

Linux 6.5 With AMD P-State EPP Default Brings Performance & Power Efficiency Benefits For Ryzen Servers
21 September 2023, Phoronix

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

IoTDB Provides Data Management for Industrial Edge IT
15 October 2020, The New Stack

provided by Google News

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Share this page