DBMS > Firebase Realtime Database vs. OpenTSDB vs. Oracle Berkeley DB vs. Snowflake

System Properties Comparison Firebase Realtime Database vs. OpenTSDB vs. Oracle Berkeley DB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Scalable Time Series DBMS based on HBase

Widely used in-process key-value store

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

Primary database model

Document store

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

firebase.google.com/products/realtime-database

opentsdb.net

www.oracle.com/database/technologies/related/berkeleydb.html

www.snowflake.com

Technical documentation

firebase.google.com/docs/database

opentsdb.net/docs/build/html/index.html

docs.oracle.com/cd/E17076_05/html/index.html

docs.snowflake.net/manuals/index.html

Developer

Google

acquired by Google 2014

currently maintained by Yahoo and other contributors

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Snowflake Computing Inc.

Initial release

2012

2011

1994

2014

Current release

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

LGPL

Open Source

commercial license available

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

Java

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API
Telnet API

CLI Client
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

Erlang
Go
Java
Python
R
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Triggers

Callbacks are triggered when data changes

yes

only for the SQL API

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on HBase

Source-replica replication

yes

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

based on HBase

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

User concepts

Access control

yes, based on authentication and database rules

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.