DBMS > Firebase Realtime Database vs. HarperDB vs. ITTIA vs. Microsoft SQL Server vs. MySQL

System Properties Comparison Firebase Realtime Database vs. HarperDB vs. ITTIA vs. Microsoft SQL Server vs. MySQL

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.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Edge Time Series DBMS with Real-Time Stream Processing

Microsofts flagship relational DBMS

Widely used open source RDBMS

Primary database model

Document store

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Relational DBMS

Document store
Graph DBMS
Spatial DBMS

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	0.55
Rank	#248	Overall
	#38	Document stores

Score	0.39
Rank	#273	Overall
	#24	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.harperdb.io

www.ittia.com

www.microsoft.com/en-us/sql-server

www.mysql.com

Technical documentation

firebase.google.com/docs/database

docs.harperdb.io/docs

learn.microsoft.com/en-US/sql/sql-server

dev.mysql.com/doc

Developer

Google

acquired by Google 2014

HarperDB

ITTIA L.L.C.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2017

2007

1989

1995

Current release

3.1, August 2021

8.7

SQL Server 2022, November 2022

8.4.0, April 2024

License

Commercial or Open Source

commercial

free community edition available

commercial

restricted free version is available

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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

Node.js

C and C++

C++

C and C++

Server operating systems

hosted

Linux
OS X

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

dynamic schema

Fixed schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

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 data manipulation statements

yes

with proprietary extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

JDBC
ODBC
RESTful HTTP API
WebSocket

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
JavaScript
Objective-C

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C
C++
JavaScript (Node.js)
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Custom Functions

since release 3.1

yes

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

proprietary syntax

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

A table resides as a whole on one (or more) nodes in a cluster

tables can be distributed across several files (horizontal partitioning); sharding through federation

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

yes

yes, but depending on the SQL-Server Edition

Multi-source 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

Transaction concepts

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

yes

Atomic execution of specific operations

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

yes, using LMDB

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

yes, based on authentication and database rules

Access rights for users and roles

Database file passwords

fine grained access rights according to SQL-standard

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.