DBMS > Apache Impala vs. Firebase Realtime Database vs. MySQL vs. OpenMLDB

System Properties Comparison Apache Impala vs. Firebase Realtime Database vs. MySQL vs. OpenMLDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Widely used open source RDBMS

An open-source machine learning database that provides a feature platform for training and inference

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store

Document store
Spatial DBMS

Relational DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.02
Rank	#367	Overall
	#37	Time Series DBMS

Website

impala.apache.org

firebase.google.com/products/realtime-database

www.mysql.com

openmldb.ai

Technical documentation

impala.apache.org/impala-docs.html

firebase.google.com/docs/database

dev.mysql.com/doc

openmldb.ai/docs/zh/main

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

4 Paradigm Inc.

Initial release

2013

2012

1995

2020

Current release

4.1.0, June 2022

8.4.0, April 2024

2024-2 February 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

C++, Java, Scala

Server operating systems

Linux

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Fixed schema

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
SQLAlchemy

Supported programming languages

All languages supporting JDBC/ODBC

Java
JavaScript
Objective-C

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

C++
Go
Java
Python
Scala

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

limited functionality with using 'rules'

yes

proprietary syntax

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

yes, based on authentication and database rules

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.