DBMS > Firebase Realtime Database vs. Microsoft Access vs. QuestDB vs. SAP HANA

System Properties Comparison Firebase Realtime Database vs. Microsoft Access vs. QuestDB vs. SAP HANA

Please select another system to include it in the comparison.

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.

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

A high performance open source SQL database for time series data

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Relational DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

firebase.google.com/products/realtime-database

www.microsoft.com/en-us/microsoft-365/access

questdb.io

www.sap.com/products/hana.html

Technical documentation

firebase.google.com/docs/database

developer.microsoft.com/en-us/access

questdb.io/docs

help.sap.com/hana

Developer

Google

acquired by Google 2014

Microsoft

QuestDB Technology Inc

SAP

Initial release

2012

1992

2014

2010

Current release

1902 (16.0.11328.20222), March 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java (Zero-GC), C++, Rust

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

Linux
macOS
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL with time-series extensions

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

since Access 2010 using the ACE-engine

SQLScript, R

Triggers

Callbacks are triggered when data changes

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by timestamps)

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with eventual consistency

yes

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

Transaction concepts

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

yes

ACID

but no files for transaction logging

ACID for single-table writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

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

yes

through memory mapped files

yes

User concepts

Access control

yes, based on authentication and database rules

a simple user-level security was built in till version Access 2003

yes

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

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.