DBMS > Blueflood vs. Graphite vs. Microsoft Access vs. Snowflake vs. Spark SQL

System Properties Comparison Blueflood vs. Graphite vs. Microsoft Access vs. Snowflake vs. Spark SQL

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

Primary database model

Time Series DBMS

Relational 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	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

blueflood.io

github.com/graphite-project/graphite-web

www.microsoft.com/en-us/microsoft-365/access

www.snowflake.com

spark.apache.org/sql

Technical documentation

github.com/rax-maas/blueflood/wiki

graphite.readthedocs.io

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

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

Developer

Rackspace

Chris Davis

Microsoft

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2013

2006

1992

2014

Current release

1902 (16.0.11328.20222), March 2019

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

commercial

Open Source

Apache 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

Python

C++

Scala

Server operating systems

Linux
OS X

Linux
Unix

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X
Windows

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

but not compliant to any SQL standard

yes

SQL-like DML and DDL statements

APIs and other access methods

HTTP REST

HTTP API
Sockets

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

JavaScript (Node.js)
Python

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

JavaScript (Node.js)
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

yes

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

a simple user-level security was built in till version Access 2003

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

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.