DBMS > Apache IoTDB vs. Atos Standard Common Repository vs. Snowflake vs. YottaDB

System Properties Comparison Apache IoTDB vs. Atos Standard Common Repository vs. Snowflake vs. YottaDB

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

Cloud-based data warehousing service for structured and semi-structured data

A fast and solid embedded Key-value store

Primary database model

Time Series DBMS

Document store
Key-value store

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

iotdb.apache.org

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

www.snowflake.com

yottadb.com

Technical documentation

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

docs.snowflake.net/manuals/index.html

yottadb.com/resources/documentation

Developer

Apache Software Foundation

Atos Convergence Creators

Snowflake Computing Inc.

YottaDB, LLC

Initial release

2018

2016

2014

2001

Current release

1.1.0, April 2023

1703

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPL 3.0

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

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

hosted

Docker
Linux

Data scheme

yes

Schema and schema-less with LDAP views

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

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

yes

by using the Octo plugin

APIs and other access methods

JDBC
Native API

LDAP

CLI Client
JDBC
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

All languages with LDAP bindings

JavaScript (Node.js)
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

cell division

yes

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

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

optimistic locking

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

User concepts

Access control

yes

LDAP bind authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

Users and groups based on OS-security mechanisms

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.