DBMS > Blueflood vs. FatDB vs. Firebase Realtime Database vs. Riak TS

System Properties Comparison Blueflood vs. FatDB vs. Firebase Realtime Database vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Scalable TimeSeries DBMS based on Cassandra

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

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

Primary database model

Time Series DBMS

Document store
Key-value store

Document store

Time Series DBMS

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

Score	0.06
Rank	#352	Overall
	#36	Time Series DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Website

blueflood.io

firebase.google.com/products/realtime-database

Technical documentation

github.com/rax-maas/blueflood/wiki

firebase.google.com/docs/database

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

Developer

Rackspace

FatCloud

Google

acquired by Google 2014

Open Source, formerly Basho Technologies

Initial release

2013

2012

2015

Current release

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

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

Erlang

Server operating systems

Linux
OS X

Windows

hosted

Linux
OS X

Data scheme

predefined scheme

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

Via inetgration in SQL Server

yes, limited

APIs and other access methods

HTTP REST

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

Java
JavaScript
Objective-C

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

Server-side scripts

Stored procedures

yes

via applications

limited functionality with using 'rules'

Erlang

Triggers

yes

via applications

Callbacks are triggered when data changes

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency
Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

yes

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.

User concepts

Access control

Can implement custom security layer via applications

yes, based on authentication and database rules

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Real-Time Performance and Health Monitoring Using Netdata
2 September 2019, CNX Software

provided by Google News

Realtime vs Cloud Firestore: Which Firebase Database to Choose
8 March 2024, Appinventiv

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Misconfigured Firebase instances leaked 19 million plaintext passwords
19 March 2024, BleepingComputer

Misconfigured firebase: A real-time cyber threat
18 January 2024, Atos

Google launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

provided by Google News

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page