DBMS > Firebase Realtime Database vs. IRONdb vs. Kinetica vs. Snowflake vs. Spark SQL

System Properties Comparison Firebase Realtime Database vs. IRONdb vs. Kinetica vs. Snowflake vs. Spark SQL

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Fully vectorized database across both GPUs and CPUs

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

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.circonus.com/solutions/time-series-database/

www.kinetica.com

www.snowflake.com

spark.apache.org/sql

Technical documentation

firebase.google.com/docs/database

docs.circonus.com/irondb/category/getting-started

docs.kinetica.com

docs.snowflake.net/manuals/index.html

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

Developer

Google

acquired by Google 2014

Circonus LLC.

Kinetica

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2012

2017

2012

2014

Current release

V0.10.20, January 2018

7.1, August 2021

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

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

C and C++

C, C++

Scala

Server operating systems

hosted

Linux

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like DML and DDL statements

yes

SQL-like DML and DDL statements

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes, in Lua

user defined functions

Triggers

Callbacks are triggered when data changes

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency or Eventual Consistency depending on configuration

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

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

GPU vRAM or System RAM

User concepts

Access control

yes, based on authentication and database rules

Access rights for users and roles on table level

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.