DBMS > Blueflood vs. Firebase Realtime Database vs. Ingres vs. Snowflake vs. Spark SQL

System Properties Comparison Blueflood vs. Firebase Realtime Database vs. Ingres vs. Snowflake vs. Spark SQL

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Well established RDBMS

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

Document store

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	13.64
Rank	#39	Overall
	#6	Document stores

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

blueflood.io

firebase.google.com/products/realtime-database

www.actian.com/databases/ingres

www.snowflake.com

spark.apache.org/sql

Technical documentation

github.com/rax-maas/blueflood/wiki

firebase.google.com/docs/database

docs.actian.com/ingres

docs.snowflake.net/manuals/index.html

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

Developer

Rackspace

Google

acquired by Google 2014

Actian Corporation

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2013

2012

1974

originally developed at University Berkely in early 1970s

2014

Current release

11.2, May 2022

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache 2.0

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

Scala

Server operating systems

Linux
OS X

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

hosted

Linux
OS X
Windows

Data scheme

predefined scheme

schema-free

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

APIs and other access methods

HTTP REST

Android
iOS
JavaScript API
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

JavaScript (Node.js)
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

user defined functions

Triggers

Callbacks are triggered when data changes

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Ingres Replicator

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

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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.

User concepts

Access control

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

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.