DBMS > Databricks vs. Fauna vs. Firebird vs. MariaDB

System Properties Comparison Databricks vs. Fauna vs. Firebird vs. MariaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

Firebird is an open source RDBMS forked from Borland's InterBase

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

Primary database model

Document store
Relational DBMS

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	1.52
Rank	#153	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

Score	20.82
Rank	#30	Overall
	#18	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Website

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

Technical documentation

docs.databricks.com

docs.fauna.com

www.firebirdsql.org/en/reference-manuals

mariadb.com/kb/en/library

Developer

Databricks

Fauna, Inc.

Firebird Foundation

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Initial release

2013

2014

2000

As fork of Borland's InterBase

2009

Fork of MySQL, which was first released in 1995

Current release

5.0.0, January 2024

11.3.2, February 2024

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

Open Source

GPL version 2, commercial enterprise subscription 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

Scala

C and C++

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

Dynamic columns are supported

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

with Databricks SQL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Python
R
Scala

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

PSQL

yes

PL/SQL compatibility added with version 10.3

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

consistent hashing

none

several options for horizontal partitioning and Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

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

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

In-memory capabilities

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

yes

with MEMORY storage engine

User concepts

Access control

Identity management, authentication, and access control

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

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.