DBMS > Firebase Realtime Database vs. Hypertable vs. MariaDB vs. Tarantool

System Properties Comparison Firebase Realtime Database vs. Hypertable vs. MariaDB vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

An open source BigTable implementation based on distributed file systems such as Hadoop

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store

Wide column store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	15.00
Rank	#39	Overall
	#6	Document stores

Score	93.81
Rank	#13	Overall
	#9	Relational DBMS

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Website

firebase.google.com/products/realtime-database

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

www.tarantool.io

Technical documentation

firebase.google.com/docs/database

mariadb.com/kb/en/library

www.tarantool.io/en/doc

Developer

Google

acquired by Google 2014

Hypertable Inc.

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Initial release

2012

2009

Fork of MySQL, which was first released in 1995

2008

Current release

0.9.8.11, March 2016

11.3.2, February 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

GNU version 3. Commercial license available

Open Source

GPL version 2, commercial enterprise subscription available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++

C and C++

Server operating systems

hosted

Linux
OS X
Windows

an inofficial Windows port is available

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

BSD
Linux
macOS

Data scheme

schema-free

yes

Dynamic columns are supported

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

yes

Secondary indexes

yes

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

with proprietary extensions

Full-featured ANSI SQL support

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

C++ API
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

Open binary protocol

Supported programming languages

Java
JavaScript
Objective-C

C++
Java
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Eiffel
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

PL/SQL compatibility added with version 10.3

Lua, C and SQL stored procedures

Triggers

Callbacks are triggered when data changes

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

several options for horizontal partitioning and Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor on file system level

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes, write ahead logging

In-memory capabilities

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

yes

with MEMORY storage engine

yes, full featured in-memory storage engine with persistence

User concepts

Access control

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» 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.