DBMS > Apache IoTDB vs. Google Cloud Datastore vs. GridGain vs. MariaDB vs. TimescaleDB

System Properties Comparison Apache IoTDB vs. Google Cloud Datastore vs. GridGain vs. MariaDB vs. TimescaleDB

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

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

GridGain is an in-memory computing platform, built on Apache Ignite

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Time Series DBMS

Document store

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial 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	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

iotdb.apache.org

cloud.google.com/datastore

www.gridgain.com

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

www.timescale.com

Technical documentation

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

cloud.google.com/datastore/docs

www.gridgain.com/docs/index.html

mariadb.com/kb/en/library

docs.timescale.com

Developer

Apache Software Foundation

Google

GridGain Systems, Inc.

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Timescale

Initial release

2018

2008

2007

2009

Fork of MySQL, which was first released in 1995

2017

Current release

1.1.0, April 2023

GridGain 8.5.1

11.3.2, February 2024

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2, commercial enterprise subscription available

Open Source

Apache 2.0

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

Java, C++, .Net

C and C++

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

Linux
OS X
Solaris
Windows

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Dynamic columns are supported

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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)

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
Native API

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

using Google App Engine

yes (compute grid and cache interceptors can be used instead)

yes

PL/SQL compatibility added with version 10.3

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Callbacks using the Google Apps Engine

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

several options for horizontal partitioning and Sharding

yes, across time and space (hash partitioning) attributes

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 using Paxos

yes (replicated cache)

Multi-source replication
Source-replica replication

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

using Google Cloud Dataflow

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

with MEMORY storage engine

User concepts

Access control

yes

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» 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.