DBMS > Apache IoTDB vs. DolphinDB vs. Google BigQuery vs. Graph Engine

System Properties Comparison Apache IoTDB vs. DolphinDB vs. Google BigQuery vs. Graph Engine

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

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

Large scale data warehouse service with append-only tables

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Primary database model

Time Series DBMS

Relational DBMS

Graph DBMS
Key-value store

Secondary database models

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	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Website

iotdb.apache.org

www.dolphindb.com

cloud.google.com/bigquery

www.graphengine.io

Technical documentation

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

docs.dolphindb.cn/en/help200/index.html

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

Developer

Apache Software Foundation

DolphinDB, Inc

Google

Microsoft

Initial release

2018

2010

Current release

1.1.0, April 2023

v2.00.4, January 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free community version available

commercial

Open Source

MIT License

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

C++

.NET and C

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
Windows

hosted

.NET

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Native API

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

horizontal partitioning

none

horizontal partitioning

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

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Administrators, Users, Groups

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

Google Cloud Identity & Access Management (IAM)

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.