DBMS > Firebase Realtime Database vs. Snowflake vs. TempoIQ vs. TerminusDB vs. UniData,UniVerse

System Properties Comparison Firebase Realtime Database vs. Snowflake vs. TempoIQ vs. TerminusDB vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed 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.

Cloud-based data warehousing service for structured and semi-structured data

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

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

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Secondary database models

Document store
RDF store

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Website

firebase.google.com/products/realtime-database

www.snowflake.com

tempoiq.com (offline)

terminusdb.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

firebase.google.com/docs/database

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Google

acquired by Google 2014

Snowflake Computing Inc.

TempoIQ

DataChemist Ltd.

Rocket Software

Initial release

2012

2014

2012

2018

1985

Current release

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3

commercial

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

Prolog, Rust

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

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

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

SQL-like query language (WOQL)

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

Java
JavaScript
Objective-C

JavaScript (Node.js)
Python

C#
Java
JavaScript

Node.js
Python
Ruby

JavaScript
Python

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

yes

Triggers

Callbacks are triggered when data changes

similar concept for controling cloud resources

yes

Realtime Alerts

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

yes

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Journaling Streams

Source-replica replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

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

simple authentication-based access control

Role-based access control

Access rights according to SQL-standard and operating system based

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.