DBMS > Apache Drill vs. EsgynDB vs. H2GIS vs. Heroic vs. Riak TS

System Properties Comparison Apache Drill vs. EsgynDB vs. H2GIS vs. Heroic vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Spatial extension of H2

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Document store
Relational DBMS

Relational DBMS

Spatial DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

drill.apache.org

www.esgyn.cn

www.h2gis.org

github.com/spotify/heroic

Technical documentation

drill.apache.org/docs

www.h2gis.org/docs/home

spotify.github.io/heroic

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Apache Software Foundation

Esgyn

CNRS

Spotify

Open Source, formerly Basho Technologies

Initial release

2012

2015

2013

2014

2015

Current release

1.20.3, January 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

LGPL 3.0

Open Source

Apache 2.0

Open Source

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java

Java

Erlang

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X

Data scheme

schema-free

yes

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.

Secondary indexes

yes

via Elasticsearch

restricted

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

yes, limited

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

C++

All languages supporting JDBC/ODBC/ADO.Net

Java

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

yes

based on H2

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

based on H2

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

yes

based on H2

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

MapR to Speak on Stream Processing Systems, Apache Spark and Drill at Industry Events in January
31 May 2024, Yahoo Movies UK

Apache Drill vs. Apache Spark — Which SQL query engine is better for you?
23 September 2019, Towards Data Science

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page