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

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

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Primary database model

Document store
Relational DBMS

Time Series DBMS

Document store
Key-value store

Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

iotdb.apache.org

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

www.snowflake.com

Technical documentation

drill.apache.org/docs

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

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Atos Convergence Creators

Snowflake Computing Inc.

Initial release

2012

2018

2016

2014

Current release

1.20.3, January 2023

1.1.0, April 2023

1703

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

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

Linux
OS X
Windows

All OS with a Java VM (>= 1.8)

Linux

hosted

Data scheme

schema-free

yes

Schema and schema-less with LDAP views

yes

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

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 SELECT statement is SQL:2003 compliant

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
Native API

LDAP

CLI Client
JDBC
ODBC

Supported programming languages

C++

C
C#
C++
Go
Java
Python
Scala

All languages with LDAP bindings

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

yes

LDAP bind authentication

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

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.