DBMS > Apache IoTDB vs. Databricks vs. Google BigQuery vs. Snowflake

System Properties Comparison Apache IoTDB vs. Databricks vs. Google BigQuery vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Large scale data warehouse service with append-only tables

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

Primary database model

Time Series DBMS

Document store
Relational DBMS

Relational DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

iotdb.apache.org

www.databricks.com

cloud.google.com/bigquery

www.snowflake.com

Technical documentation

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

docs.databricks.com

cloud.google.com/bigquery/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Databricks

Google

Snowflake Computing Inc.

Initial release

2018

2013

2010

2014

Current release

1.1.0, April 2023

License

Commercial or Open Source

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

All OS with a Java VM (>= 1.8)

hosted

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

yes

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

Typing

predefined data types such as float or date

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

with Databricks SQL

yes

APIs and other access methods

JDBC
Native API

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Python
R
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and aggregates

user defined functions

in JavaScript

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)

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

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.