DBMS > Firebase Realtime Database vs. Interbase vs. Machbase Neo vs. MySQL vs. OrigoDB

System Properties Comparison Firebase Realtime Database vs. Interbase vs. Machbase Neo vs. MySQL vs. OrigoDB

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.

Light-weight proven RDBMS

originally from Borland

TimeSeries DBMS for AIoT and BigData

Widely used open source RDBMS

A fully ACID in-memory object graph database

Primary database model

Key/Value like access via memcached API

Document store
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

www.embarcadero.com/products/interbase

machbase.com

www.mysql.com

origodb.com

Technical documentation

firebase.google.com/docs/database

docs.embarcadero.com/products/interbase

machbase.com/dbms

dev.mysql.com/doc

origodb.com/docs

Developer

Google

acquired by Google 2014

Embarcadero

Machbase

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

Initial release

2012

1984

2013

1995

2009

under the name LiveDB

Current release

InterBase 2020, December 2019

V8.0, August 2023

8.4.0, April 2024

License

Commercial or Open Source

commercial

free test version available

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

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

export as XML data possible

yes

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC

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

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

Supported programming languages

Java
JavaScript
Objective-C

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

.Net

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Interbase procedure and trigger language

yes

proprietary syntax

yes

Triggers

Callbacks are triggered when data changes

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Write ahead log

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

fine grained access rights according to SQL-standard

simple password-based access control

Users with fine-grained authorization concept

no user groups or roles

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.