DBMS > EXASOL vs. Firebase Realtime Database vs. SiteWhere vs. Spark SQL vs. SQLite

System Properties Comparison EXASOL vs. Firebase Realtime Database vs. SiteWhere vs. Spark SQL vs. SQLite

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

M2M integration platform for persisting/querying time series data

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

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.exasol.com

firebase.google.com/products/realtime-database

github.com/sitewhere/sitewhere

spark.apache.org/sql

www.sqlite.org

Technical documentation

www.exasol.com/resources

firebase.google.com/docs/database

sitewhere1.sitewhere.io/index.html

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

www.sqlite.org/docs.html

Developer

Exasol

Google

acquired by Google 2014

SiteWhere

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2000

2012

2010

2014

2000

Current release

3.5.0 ( 2.13), September 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

Apache 2.0

Open Source

Public Domain

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

hosted

Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Android
iOS
JavaScript API
RESTful HTTP API

HTTP REST

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
Lua
Python
R

Java
JavaScript
Objective-C

Java
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

limited functionality with using 'rules'

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Access rights for users, groups and roles according to SQL-standard

yes, based on authentication and database rules

Users with fine-grained authorization concept

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.