DBMS > Apache IoTDB vs. Ehcache vs. GeoSpock vs. Snowflake vs. TerarkDB

System Properties Comparison Apache IoTDB vs. Ehcache vs. GeoSpock vs. Snowflake vs. TerarkDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded 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

A widely adopted Java cache with tiered storage options

Spatial and temporal data processing engine for extreme data scale

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Time Series 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.89
Rank	#67	Overall
	#8	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

iotdb.apache.org

www.ehcache.org

geospock.com

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

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

www.ehcache.org/documentation

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Terracotta Inc, owned by Software AG

GeoSpock

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2018

2009

2014

2016

Current release

1.1.0, April 2023

3.10.0, March 2022

2.0, September 2019

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

restricted open source version 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

Java, Javascript

C++

Server operating systems

All OS with a Java VM (>= 1.8)

All OS with a Java VM

hosted

Data scheme

yes

schema-free

yes

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

schema-free

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

temporal, categorical

SQL

Support of SQL

SQL-like query language

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC
Native API

JCache

JDBC

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Java

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Cache Event Listeners

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

by using Terracotta Server

Automatic 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

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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 rights for users can be defined per table

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.