DBMS > Apache IoTDB vs. Atos Standard Common Repository vs. ClickHouse vs. Oracle Berkeley DB vs. Snowflake

System Properties Comparison Apache IoTDB vs. Atos Standard Common Repository vs. ClickHouse vs. Oracle Berkeley DB vs. Snowflake

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

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Widely used in-process key-value store

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

Primary database model

Time Series DBMS

Document store
Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

iotdb.apache.org

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

clickhouse.com

www.oracle.com/database/technologies/related/berkeleydb.html

www.snowflake.com

Technical documentation

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

clickhouse.com/docs

docs.oracle.com/cd/E17076_05/html/index.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Atos Convergence Creators

Clickhouse Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

Initial release

2018

2016

1994

2014

Current release

1.1.0, April 2023

1703

v24.4.1.2088-stable, May 2024

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

Open Source

commercial license available

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.

ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

Java

C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

FreeBSD
Linux
macOS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

Data scheme

yes

Schema and schema-less with LDAP views

yes

schema-free

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

Close to ANSI SQL (SQL/JSON + extensions)

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

JDBC
Native API

LDAP

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

All languages with LDAP bindings

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

only for the SQL API

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

key based and custom

none

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

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Source-replica replication

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

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

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key 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.