DBMS > Blueflood vs. EXASOL vs. HBase vs. JaguarDB vs. Snowflake

System Properties Comparison Blueflood vs. EXASOL vs. HBase vs. JaguarDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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

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

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Time Series DBMS

Relational DBMS

Wide column store

Key-value store
Vector DBMS

Relational DBMS

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

Score	0.09
Rank	#353	Overall
	#33	Time Series DBMS

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

www.exasol.com/resources

hbase.apache.org/book.html

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Rackspace

Exasol

Apache Software Foundation

Apache top-level project, originally developed by Powerset

DataJaguar, Inc.

Snowflake Computing Inc.

Initial release

2013

2000

2008

2015

2014

Current release

2.3.4, January 2021

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache version 2

Open Source

GPL V3.0

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

C++

the server part. Clients available in other languages

Server operating systems

Linux
OS X

Linux
Unix
Windows

using Cygwin

Linux

hosted

Data scheme

predefined scheme

yes

schema-free, schema definition possible

yes

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

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

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

HTTP REST

.Net
JDBC
ODBC
WebSocket

Java API
RESTful HTTP API
Thrift

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

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

based on Cassandra

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Immediate Consistency or Eventual Consistency

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

rights management via user accounts

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.