DBMS > Firebase Realtime Database vs. Machbase Neo vs. Microsoft Azure Data Explorer vs. MySQL vs. Oracle Berkeley DB

System Properties Comparison Firebase Realtime Database vs. Machbase Neo vs. Microsoft Azure Data Explorer vs. MySQL vs. Oracle Berkeley DB

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

Fully managed big data interactive analytics platform

Widely used open source RDBMS

Widely used in-process key-value store

Primary database model

column oriented

Key/Value like access via memcached API

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

Document store
Spatial DBMS

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Website

firebase.google.com/products/realtime-database

machbase.com

azure.microsoft.com/services/data-explorer

www.mysql.com

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

firebase.google.com/docs/database

machbase.com/dbms

docs.microsoft.com/en-us/azure/data-explorer

dev.mysql.com/doc

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Google

acquired by Google 2014

Machbase

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2013

2019

1995

1994

Current release

V8.0, August 2023

cloud service with continuous releases

8.4.0, April 2024

18.1.40, May 2020

License

Commercial or Open Source

commercial

free test version available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial license available

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

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

Linux
macOS
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

only with the Berkeley DB XML edition

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

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

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

Triggers

Callbacks are triggered when data changes

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

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

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

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.