DBMS > Apache Druid vs. Datomic vs. EXASOL vs. HEAVY.AI vs. Snowflake

System Properties Comparison Apache Druid vs. Datomic vs. EXASOL vs. HEAVY.AI vs. Snowflake

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

druid.apache.org

www.datomic.com

www.exasol.com

github.com/heavyai/heavydb
www.heavy.ai

www.snowflake.com

Technical documentation

druid.apache.org/docs/latest/design

docs.datomic.com

www.exasol.com/resources

docs.heavy.ai

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation and contributors

Cognitect

Exasol

HEAVY.AI, Inc.

Snowflake Computing Inc.

Initial release

2012

2000

2016

2014

Current release

29.0.1, April 2024

1.0.7075, December 2023

5.10, January 2022

License

Commercial or Open Source

Open Source

Apache license v2

commercial

limited edition free

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

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, Clojure

C++ and CUDA

Server operating systems

Linux
OS X
Unix

All OS with a Java VM

Linux

hosted

Data scheme

yes

schema-less columns are supported

yes

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

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

SQL

Support of SQL

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC
Thrift
Vega

CLI Client
JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Clojure
Java

Java
Lua
Python
R

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

But extensive use of caching in the application peers

Sharding

Round robin

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

But extensive use of caching in the application peers

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

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

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

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.