DBMS > Apache Druid vs. EsgynDB vs. Riak TS vs. SAP HANA

System Properties Comparison Apache Druid vs. EsgynDB vs. Riak TS vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

druid.apache.org

www.esgyn.cn

www.sap.com/products/hana.html

Technical documentation

druid.apache.org/docs/latest/design

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

help.sap.com/hana

Developer

Apache Software Foundation and contributors

Esgyn

Open Source, formerly Basho Technologies

SAP

Initial release

2012

2015

2010

Current release

29.0.1, April 2024

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++, Java

Erlang

Server operating systems

Linux
OS X
Unix

Linux

Linux
OS X

Appliance or cloud-service

Data scheme

yes

schema-less columns are supported

yes

schema-free

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SQL for querying

yes

yes, limited

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

All languages supporting JDBC/ODBC/ADO.Net

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

Java Stored Procedures

Erlang

SQLScript, R

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication between multi datacenters

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

fine grained access rights according to SQL-standard

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.