DBMS > Firebase Realtime Database vs. Machbase Neo vs. Riak KV vs. SAP HANA

System Properties Comparison Firebase Realtime Database vs. Machbase Neo vs. Riak KV vs. SAP HANA

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

Distributed, fault tolerant key-value store

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Time Series DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

firebase.google.com/products/realtime-database

machbase.com

www.sap.com/products/hana.html

Technical documentation

firebase.google.com/docs/database

machbase.com/dbms

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

help.sap.com/hana

Developer

Google

acquired by Google 2014

Machbase

OpenSource, formerly Basho Technologies

SAP

Initial release

2012

2013

2009

2010

Current release

V8.0, August 2023

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

free test version available

Open Source

Apache version 2, commercial enterprise edition

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

Server operating systems

hosted

Linux
macOS
Windows

Linux
OS X

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

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

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

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

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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'

Erlang

SQLScript, R

Triggers

Callbacks are triggered when data changes

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

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.

yes

volatile and lookup table

yes

User concepts

Access control

yes, based on authentication and database rules

simple password-based access control

yes, using Riak Security

yes

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.