DBMS > Firebase Realtime Database vs. Machbase Neo vs. RRDtool vs. TerarkDB

System Properties Comparison Firebase Realtime Database vs. Machbase Neo vs. RRDtool vs. TerarkDB

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.

TimeSeries DBMS for AIoT and BigData

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store

Time Series DBMS

Key-value store

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

firebase.google.com/products/realtime-database

machbase.com

oss.oetiker.ch/rrdtool

github.com/bytedance/terarkdb

Technical documentation

firebase.google.com/docs/database

machbase.com/dbms

oss.oetiker.ch/rrdtool/doc

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Google

acquired by Google 2014

Machbase

Tobias Oetiker

ByteDance, originally Terark

Initial release

2012

2013

1999

2016

Current release

V8.0, August 2023

1.8.0, 2022

License

Commercial or Open Source

commercial

free test version available

Open Source

GPL V2 and FLOSS

commercial

restricted open source version available

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

Implementations in Java (e.g. RRD4J) and C# available

C++

Server operating systems

hosted

Linux
macOS
Windows

HP-UX
Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

in-process shared library
Pipes

C++ API
Java API

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

C++
Java

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Triggers

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

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

none

Foreign keys

Referential integrity

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

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

volatile and lookup table

yes

User concepts

Access control

yes, based on authentication and database rules

simple password-based access control

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

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

Time Series DBMS as a new trend?
1 June 2015, 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

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

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

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

provided by Google News

Cacti servers under attack by attackers exploiting CVE-2022-46169
16 January 2023, Help Net Security

Critical IP spoofing bug patched in Cacti
15 December 2022, The Daily Swig

How to install Cacti SNMP Monitor on Ubuntu
24 November 2017, TechRepublic

Installation Guide for Collectd and Collectd-Web to Monitor Server Resources in Linux
29 November 2017, Linux.com

SNMP: The Little Protocol That Could
7 November 2020, Techopedia

provided by Google News

Share this page