DBMS > Firebase Realtime Database vs. GridDB vs. Machbase Neo vs. RocksDB

System Properties Comparison Firebase Realtime Database vs. GridDB vs. Machbase Neo 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.

Scalable in-memory time series database optimized for IoT and Big Data

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Document store

Time Series DBMS

Key-value store

Secondary database models

Key-value store
Relational DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	1.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

firebase.google.com/products/realtime-database

griddb.net

machbase.com

rocksdb.org

Technical documentation

firebase.google.com/docs/database

docs.griddb.net

machbase.com/dbms

github.com/facebook/rocksdb/wiki

Developer

Google

acquired by Google 2014

Toshiba Corporation

Machbase

Facebook, Inc.

Initial release

2012

2013

Current release

5.1, August 2022

V8.0, August 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

free test version available

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

C++

Server operating systems

hosted

Linux

Linux
macOS
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

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

C++ API
Java API

Supported programming languages

Java
JavaScript
Objective-C

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

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

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

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 within container, eventual consistency across containers

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID at container level

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.

yes

volatile and lookup table

yes

User concepts

Access control

yes, based on authentication and database rules

Access rights for users can be defined per database

simple password-based access control

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.