DBMS > GeoSpock vs. IRONdb vs. Snowflake vs. TerarkDB vs. Warp 10

System Properties Comparison GeoSpock vs. IRONdb vs. Snowflake vs. TerarkDB vs. Warp 10

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial and temporal data processing engine for extreme data scale

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Time Series DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

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

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

geospock.com

www.circonus.com/solutions/time-series-database/

www.snowflake.com

github.com/bytedance/terarkdb

www.warp10.io

Technical documentation

docs.circonus.com/irondb/category/getting-started

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

www.warp10.io/content/02_Getting_started

Developer

GeoSpock

Circonus LLC.

Snowflake Computing Inc.

ByteDance, originally Terark

SenX

Initial release

2017

2014

2016

2015

Current release

2.0, September 2019

V0.10.20, January 2018

License

Commercial or Open Source

commercial

restricted open source version available

Open Source

Apache License 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, Javascript

C and C++

C++

Java

Server operating systems

hosted

Linux

hosted

Linux
OS X
Windows

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

text, numeric, histograms

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

temporal, categorical

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

JDBC

HTTP API

CLI Client
JDBC
ODBC

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

yes

WarpScript

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Automatic, metric affinity per node

yes

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of 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

Access rights for users can be defined per table

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.