DBMS > Blueflood vs. Graphite vs. Snowflake vs. Spark SQL vs. Vitess

System Properties Comparison Blueflood vs. Graphite vs. Snowflake vs. Spark SQL vs. Vitess

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

blueflood.io

github.com/graphite-project/graphite-web

www.snowflake.com

spark.apache.org/sql

vitess.io

Technical documentation

github.com/rax-maas/blueflood/wiki

graphite.readthedocs.io

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

vitess.io/docs

Developer

Rackspace

Chris Davis

Snowflake Computing Inc.

Apache Software Foundation

The Linux Foundation, PlanetScale

Initial release

2013

2006

2014

2013

Current release

3.5.0 ( 2.13), September 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

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

Python

Scala

Server operating systems

Linux
OS X

Linux
Unix

hosted

Linux
OS X
Windows

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

Numeric data only

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 DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

HTTP REST

HTTP API
Sockets

CLI Client
JDBC
ODBC

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

JavaScript (Node.js)
Python

Java
Python
R
Scala

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

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

yes

yes, utilizing Spark Core

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

none

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

locking

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

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.