DBMS > Firebase Realtime Database vs. Hawkular Metrics vs. Heroic vs. OrigoDB vs. TinkerGraph

System Properties Comparison Firebase Realtime Database vs. Hawkular Metrics vs. Heroic vs. OrigoDB vs. TinkerGraph

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.

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

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

A fully ACID in-memory object graph database

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store

Time Series DBMS

Document store
Object oriented DBMS

Graph DBMS

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

Score	13.43
Rank	#39	Overall
	#6	Document stores

Score	0.00
Rank	#380	Overall
	#40	Time Series DBMS

Score	0.02
Rank	#368	Overall
	#38	Time Series DBMS

Score	0.00
Rank	#386	Overall
	#54	Document stores
	#20	Object oriented DBMS

Score	0.07
Rank	#346	Overall
	#35	Graph DBMS

Website

firebase.google.com/products/realtime-database

www.hawkular.org

github.com/spotify/heroic

origodb.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

firebase.google.com/docs/database

www.hawkular.org/hawkular-metrics/docs/user-guide

spotify.github.io/heroic

origodb.com/docs

Developer

Google

acquired by Google 2014

Community supported by Red Hat

Spotify

Robert Friberg et al

Initial release

2012

2014

2009

under the name LiveDB

2009

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache 2.0

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

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HTTP REST

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

.NET Client API
HTTP API
LINQ

TinkerPop 3

Supported programming languages

Java
JavaScript
Objective-C

Go
Java
Python
Ruby

.Net

Groovy
Java

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

yes

via Hawkular Alerting

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

Source-replica replication

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency
Immediate Consistency

none

Foreign keys

Referential integrity

depending on model

yes

Relationships in graphs

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

Write ahead log

optional

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

yes, based on authentication and database rules

Role based authorization

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

Instant harkens back to a pre-Google Firebase
2 October 2024, TechCrunch

Supabase vs. Firebase: Which BaaS is Best for Your App?
14 August 2024, Netguru

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

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

Google Cloud beefs up database services for generative AI workloads
2 October 2024, SiliconANGLE News

provided by Google News

How Code Wizards load tested Heroic Labs’ Nakama to two million concurrent players with AWS
1 October 2024, AWS Blog

provided by Google News

Unit testing Apache TinkerPop transactions: From TinkerGraph to Amazon Neptune
3 June 2024, AWS Blog

Simple Deployment of a Graph Database: JanusGraph
12 October 2020, Towards Data Science

Introducing Gremlin query hints for Amazon Neptune
26 February 2019, AWS Blog

provided by Google News

Share this page