DBMS > Firebase Realtime Database vs. Fujitsu Enterprise Postgres vs. Riak TS vs. RocksDB

System Properties Comparison Firebase Realtime Database vs. Fujitsu Enterprise Postgres vs. Riak TS vs. RocksDB

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.

Enterprise-grade PostgreSQL-based DBMS with security enhancements such as Transparent Data Encryption and Data Masking, plus high-availability and performance improvement features.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.37
Rank	#278	Overall
	#128	Relational DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

firebase.google.com/products/realtime-database

www.postgresql.fastware.com

rocksdb.org

Technical documentation

firebase.google.com/docs/database

www.postgresql.fastware.com/product-manuals

www.tiot.jp/riak-docs/riak/ts/latest

github.com/facebook/rocksdb/wiki

Developer

Google

acquired by Google 2014

PostgreSQL Global Development Group, Fujitsu Australia Software Technology

Open Source, formerly Basho Technologies

Facebook, Inc.

Initial release

2012

2015

2013

Current release

Fujitsu Enterprise Postgres 14, January 2022

3.0.0, September 2022

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

BSD

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

Erlang

C++

Server operating systems

hosted

Linux
Windows

Linux
OS X

Linux

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

yes, limited

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

Java
JavaScript
Objective-C

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Erlang

Triggers

Callbacks are triggered when data changes

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

partitioning by range, list and by hash

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

100% compatible with community PostgreSQL
» more

Competitive advantages

Built-in TDE and Data Masking security. In-Memory Columnar Index, and a high speed...
» more

Typical application scenarios

Transactional payments applications, reporting and mixed workloads.
» more

Market metrics

Over 30 years experience in database technology. Over 20 years in Postgres development...
» more

Licensing and pricing models

Core based licensing
» more

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.