DBMS > 4D vs. Firebase Realtime Database vs. MySQL vs. QuestDB vs. TigerGraph

System Properties Comparison 4D vs. Firebase Realtime Database vs. MySQL vs. QuestDB vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

A high performance open source SQL database for time series data

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	2.37
Rank	#110	Overall
	#54	Relational DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Score	1.44
Rank	#152	Overall
	#14	Graph DBMS

Website

www.4d.com

firebase.google.com/products/realtime-database

www.mysql.com

questdb.io

www.tigergraph.com

Technical documentation

developer.4d.com

firebase.google.com/docs/database

dev.mysql.com/doc

questdb.io/docs

docs.tigergraph.com

Developer

4D, Inc

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

QuestDB Technology Inc

Initial release

1984

2012

1995

2014

2017

Current release

v20, April 2023

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

commercial

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.

Implementation language

C and C++

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

C++

Server operating systems

OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux

Data scheme

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

yes

with proprietary extensions

SQL with time-series extensions

SQL-like query language (GSQL)

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

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

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

4D proprietary IDE
PHP

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

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

over HTTP

C++
Java

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

yes

proprietary syntax

yes

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by timestamps)

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

yes

Relationships in graphs

Transaction concepts

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

ACID

yes

ACID

not for MyISAM storage engine

ACID for single-table writes

ACID

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

through memory mapped files

User concepts

Access control

Users and groups

yes, based on authentication and database rules

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Weather data visualization and forecasting with QuestDB, Kafka and Grafana
4 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

Write Time: a call for community writers
13 August 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.