DBMS > Amazon Aurora vs. Firebase Realtime Database vs. JanusGraph vs. mSQL vs. MySQL

System Properties Comparison Amazon Aurora vs. Firebase Realtime Database vs. JanusGraph vs. mSQL vs. MySQL

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	7.84
Rank	#44	Overall
	#28	Relational DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1.85
Rank	#134	Overall
	#12	Graph DBMS

Score	1.26
Rank	#163	Overall
	#74	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/rds/aurora

firebase.google.com/products/realtime-database

janusgraph.org

hughestech.com.au/products/msql

www.mysql.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

firebase.google.com/docs/database

docs.janusgraph.org

dev.mysql.com/doc

Developer

Amazon

Google

acquired by Google 2014

Linux Foundation; originally developed as Titan by Aurelius

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2015

2012

2017

1994

1995

Current release

1.0.0, October 2023

4.4, October 2021

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free licenses can be provided

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.

Implementation language

Java

C and C++

Server operating systems

hosted

Linux
OS X
Unix
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

Android
iOS
JavaScript API
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Java
JavaScript
Objective-C

Clojure
Java
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

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

yes

limited functionality with using 'rules'

yes

proprietary syntax

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

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

Eventual Consistency
Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

User authentification and security via Rexster Graph Server

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.