DBMS > Blueflood vs. EXASOL vs. Hazelcast vs. Snowflake vs. Tibero

System Properties Comparison Blueflood vs. EXASOL vs. Hazelcast vs. Snowflake vs. Tibero

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.

A widely adopted in-memory data grid

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

us.tmaxsoft.com/products/tibero

Technical documentation

github.com/rax-maas/blueflood/wiki

www.exasol.com/resources

hazelcast.org/imdg/docs

docs.snowflake.net/manuals/index.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Rackspace

Exasol

Hazelcast

Snowflake Computing Inc.

TmaxSoft

Initial release

2013

2000

2008

2014

2003

Current release

5.3.6, November 2023

6, April 2015

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2; commercial licenses 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

C and Assembler

Server operating systems

Linux
OS X

All OS with a Java VM

hosted

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

predefined scheme

yes

schema-free

yes

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

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.

yes

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

HTTP REST

.Net
JDBC
ODBC
WebSocket

JCache
JPA
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

Java
Lua
Python
R

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

JavaScript (Node.js)
Python

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

yes

Event Listeners, Executor Services

user defined functions

Persistent Stored Procedure (PSM)

Triggers

yes

Events

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

yes

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

Replicated Map

yes

Multi-source replication
Source-replica replication

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 selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

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

planned for next version

User concepts

Access control

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

Role-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.