DBMS > Firebase Realtime Database vs. Snowflake vs. Tibero vs. Titan

System Properties Comparison Firebase Realtime Database vs. Snowflake vs. Tibero vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

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

A secure RDBMS, designed for easy portability from Oracle

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Document store

Relational DBMS

Graph DBMS

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	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.snowflake.com

us.tmaxsoft.com/products/tibero

github.com/thinkaurelius/titan

Technical documentation

firebase.google.com/docs/database

docs.snowflake.net/manuals/index.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

github.com/thinkaurelius/titan/wiki

Developer

Google

acquired by Google 2014

Snowflake Computing Inc.

TmaxSoft

Aurelius, owned by DataStax

Initial release

2012

2014

2003

2012

Current release

6, April 2015

License

Commercial or Open Source

commercial

Open Source

Apache license, version 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 Assembler

Java

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X
Unix
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

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

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

Java
JavaScript
Objective-C

JavaScript (Node.js)
Python

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Clojure
Java
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Persistent Stored Procedure (PSM)

yes

Triggers

Callbacks are triggered when data changes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning

by range, hash, list or composite

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graph

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

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

planned for next version

User concepts

Access control

yes, based on authentication and database rules

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

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

User authentification and security via Rexster Graph Server

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.