DBMS > Blueflood vs. Cassandra vs. Graph Engine vs. HEAVY.AI

System Properties Comparison Blueflood vs. Cassandra vs. Graph Engine vs. HEAVY.AI

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Primary database model

Time Series DBMS

Wide column store

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Vector DBMS

starting with release V5

Spatial DBMS

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Website

blueflood.io

cassandra.apache.org

www.graphengine.io

github.com/heavyai/heavydb
www.heavy.ai

Technical documentation

github.com/rax-maas/blueflood/wiki

cassandra.apache.org/doc/latest

www.graphengine.io/docs/manual

docs.heavy.ai

Developer

Rackspace

Apache Software Foundation

Apache top level project, originally developped by Facebook

Microsoft

HEAVY.AI, Inc.

Initial release

2013

2008

2010

2016

Current release

4.1.3, July 2023

5.10, January 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

Open Source

MIT License

Open Source

Apache Version 2; enterprise edition available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

.NET and C

C++ and CUDA

Server operating systems

Linux
OS X

BSD
Linux
OS X
Windows

.NET

Linux

Data scheme

predefined scheme

schema-free

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.

Secondary indexes

restricted

only equality queries, not always the best performing solution

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

yes

APIs and other access methods

HTTP REST

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

Supported programming languages

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

no "single point of failure"

horizontal partitioning

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

selectable replication factor

Representation of geographical distribution of servers is possible

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomicity and isolation are supported for single operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 can be defined per object

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» more

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.