DBMS > EXASOL vs. HBase vs. Infobright vs. Snowflake vs. TerarkDB

System Properties Comparison EXASOL vs. HBase vs. Infobright vs. Snowflake vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Primary database model

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

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

www.exasol.com

hbase.apache.org

ignitetech.com/softwarelibrary/infobrightdb

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

www.exasol.com/resources

hbase.apache.org/book.html

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Exasol

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Ignite Technologies Inc.; formerly InfoBright Inc.

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2000

2008

2005

2014

2016

Current release

2.3.4, January 2021

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

restricted open source version available

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

C++

Server operating systems

Linux
Unix
Windows

using Cygwin

Linux
Windows

hosted

Data scheme

yes

schema-free, schema definition possible

yes

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

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

Knowledge Grid Technology used instead

SQL

Support of SQL

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Java API
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

Java
Lua
Python
R

C
C#
C++
Groovy
Java
PHP
Python
Scala

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

Coprocessors in Java

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.