DBMS > Apache Impala vs. Firebase Realtime Database vs. NuoDB vs. SQLite vs. TerminusDB

System Properties Comparison Apache Impala vs. Firebase Realtime Database vs. NuoDB vs. SQLite vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Widely used embeddable, in-process RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store

Document store
RDF store

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

impala.apache.org

firebase.google.com/products/realtime-database

www.3ds.com/nuodb-distributed-sql-database

www.sqlite.org

terminusdb.com

Technical documentation

impala.apache.org/impala-docs.html

firebase.google.com/docs/database

doc.nuodb.com

www.sqlite.org/docs.html

terminusdb.github.io/terminusdb/#

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

acquired by Google 2014

Dassault Systèmes

originally NuoDB, Inc.

Dwayne Richard Hipp

DataChemist Ltd.

Initial release

2013

2012

2013

2000

2018

Current release

4.1.0, June 2022

3.45.3 (15 April 2024), April 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

Open Source

Public Domain

Open Source

GPL V3

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++

Prolog, Rust

Server operating systems

Linux

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

server-less

Linux

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript
Objective-C

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

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

JavaScript
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

limited functionality with using 'rules'

Java, SQL

yes

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

data is dynamically stored/cached on the nodes where it is read/written

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Managed transparently by NuoDB

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

tunable commit protocol

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

Temporary table

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

yes, based on authentication and database rules

Standard SQL roles/ privileges, Administrative Users

Role-based access control

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.