DBMS > Blueflood vs. EXASOL vs. OrientDB vs. Snowflake vs. Warp 10

System Properties Comparison Blueflood vs. EXASOL vs. OrientDB vs. Snowflake vs. Warp 10

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.

Multi-model DBMS (Document, Graph, Key/Value)

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

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	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

www.exasol.com/resources

www.orientdb.com/docs/last/index.html

docs.snowflake.net/manuals/index.html

www.warp10.io/content/02_Getting_started

Developer

Rackspace

Exasol

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

SenX

Initial release

2013

2000

2010

2014

2015

Current release

3.2.29, March 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache version 2

commercial

Open Source

Apache License 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

Java

Server operating systems

Linux
OS X

All OS with a Java JDK (>= JDK 6)

hosted

Linux
OS X
Windows

Data scheme

predefined scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

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

schema-free

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

SQL-like query language, no joins

yes

APIs and other access methods

HTTP REST

.Net
JDBC
ODBC
WebSocket

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

Java
Lua
Python
R

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Java, Javascript

user defined functions

yes

WarpScript

Triggers

yes

Hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

relationship in graphs

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

Access rights for users and roles; record level security configurable

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.