DBMS > Apache IoTDB vs. PlanetScale vs. Snowflake vs. WakandaDB

System Properties Comparison Apache IoTDB vs. PlanetScale vs. Snowflake vs. WakandaDB

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Time Series DBMS

Relational DBMS

Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

Technical documentation

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

planetscale.com/docs

docs.snowflake.net/manuals/index.html

wakanda.github.io/doc

Developer

Apache Software Foundation

PlanetScale

Snowflake Computing Inc.

Wakanda SAS

Initial release

2018

2020

2014

2012

Current release

1.1.0, April 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

AGPLv3, extended commercial license available

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++, JavaScript

Server operating systems

All OS with a Java VM (>= 1.8)

Docker
Linux
macOS

hosted

Linux
OS X
Windows

Data scheme

yes

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

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
Native API

ADO.NET
JDBC
MySQL protocol
ODBC

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

yes

none

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

Multi-source replication
Source-replica replication

yes

none

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

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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

yes

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.