DBMS > Firebase Realtime Database vs. Heroic vs. Linter vs. Riak TS

System Properties Comparison Firebase Realtime Database vs. Heroic vs. Linter vs. Riak TS

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

RDBMS for high security requirements

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

Primary database model

Secondary database models

Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

firebase.google.com/products/realtime-database

github.com/spotify/heroic

linter.ru

Technical documentation

firebase.google.com/docs/database

spotify.github.io/heroic

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

Developer

Google

acquired by Google 2014

Spotify

relex.ru

Open Source, formerly Basho Technologies

Initial release

2012

2014

1990

2015

Current release

3.0.0, September 2022

License

Commercial or Open Source

commercial

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

C and C++

Erlang

Server operating systems

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
OS X

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

via Elasticsearch

yes

restricted

SQL

Support of SQL

yes

yes, limited

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

HTTP API
Native Erlang Interface

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
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

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

proprietary syntax with the possibility to convert from PL/SQL

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

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency
Immediate Consistency

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

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

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

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

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

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

Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
18 January 2024, Atos

Google Firebase may have exposed 125M records from misconfigurations
19 March 2024, SC Media

Hundreds of Google Firebase websites might have leaked data online
19 March 2024, TechRadar

provided by Google News

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

СУБД «Линтер Бастион» прошла сертификацию ФСТЭК России по новым требованиям к системам управления ...
11 March 2024, ServerNews

provided by Google News

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

Enterprise NoSQL Database for the IoT Becomes Open Source
11 May 2016, ENGINEERING.com

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

provided by Google News

Share this page