DBMS > EXASOL vs. HEAVY.AI vs. Snowflake vs. TerarkDB vs. TimescaleDB

System Properties Comparison EXASOL vs. HEAVY.AI vs. Snowflake vs. TerarkDB vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

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

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Key-value store

Time Series DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

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

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

www.exasol.com

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

www.snowflake.com

github.com/bytedance/terarkdb

www.timescale.com

Technical documentation

www.exasol.com/resources

docs.heavy.ai

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.timescale.com

Developer

Exasol

HEAVY.AI, Inc.

Snowflake Computing Inc.

ByteDance, originally Terark

Timescale

Initial release

2000

2016

2014

2016

2017

Current release

5.10, January 2022

2.13.0, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

restricted open source version available

Open Source

Apache 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

C++ and CUDA

C++

Server operating systems

Linux

hosted

Linux
OS X
Windows

Data scheme

yes

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

schema-free

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

yes

full PostgreSQL SQL syntax

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC
Thrift
Vega

CLI Client
JDBC
ODBC

C++ API
Java API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Java
Lua
Python
R

All languages supporting JDBC/ODBC/Thrift
Python

JavaScript (Node.js)
Python

C++
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

yes

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

Source-replica replication with hot standby and reads on replicas

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

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

fine grained access rights according to SQL-standard

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.