DBMS > Apache IoTDB vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. Newts vs. Snowflake

System Properties Comparison Apache IoTDB vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. Newts 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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Time Series DBMS based on Cassandra

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

Primary database model

Time Series DBMS

Document store
Key-value store

Document store

Time Series DBMS

Relational DBMS

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

Score	1.19
Rank	#176	Overall
	#15	Time Series DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

iotdb.apache.org

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

cloud.google.com/datastore

opennms.github.io/newts

www.snowflake.com

Technical documentation

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

cloud.google.com/datastore/docs

github.com/OpenNMS/newts/wiki

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Atos Convergence Creators

Google

OpenNMS Group

Snowflake Computing Inc.

Initial release

2018

2016

2008

2014

Current release

1.1.0, April 2023

1703

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache 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

All OS with a Java VM (>= 1.8)

Linux

hosted

Linux
OS X
Windows

hosted

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

yes

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

Typing

predefined data types such as float or date

yes

optional

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
Native API

LDAP

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP REST
Java API

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

All languages with LDAP bindings

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

using Google App Engine

user defined functions

Triggers

yes

Callbacks using the Google Apps Engine

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

Sharding

based on Cassandra

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

Multi-source replication using Paxos

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

using Google Cloud Dataflow

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 or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.