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

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

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.

Performant, highly scalable DBMS for AI and IoT applications

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Time Series DBMS

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Document store
Spatial 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	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	1.04
Rank	#191	Overall
	#89	Relational DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

www.exasol.com/resources

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

vitess.io/docs

Developer

Rackspace

Exasol

DataJaguar, Inc.

Snowflake Computing Inc.

The Linux Foundation, PlanetScale

Initial release

2013

2000

2015

2014

2013

Current release

3.3 July 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL V3.0

commercial

Open Source

Apache Version 2.0, commercial licenses 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++

the server part. Clients available in other languages

Server operating systems

Linux
OS X

Linux

hosted

Docker
Linux
macOS

Data scheme

predefined scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

HTTP REST

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC

CLI Client
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java
Lua
Python
R

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

JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

rights management via user accounts

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

Users with fine-grained authorization concept

no user groups or roles

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.