DBMS > Drizzle vs. Firebase Realtime Database vs. SwayDB vs. Trafodion vs. XTDB

System Properties Comparison Drizzle vs. Firebase Realtime Database vs. SwayDB vs. Trafodion vs. XTDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Transactional SQL-on-Hadoop DBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

firebase.google.com/products/realtime-database

swaydb.simer.au

trafodion.apache.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

firebase.google.com/docs/database

trafodion.apache.org/documentation.html

www.xtdb.com/docs

Developer

Drizzle project, originally started by Brian Aker

Google

acquired by Google 2014

Simer Plaha

Apache Software Foundation, originally developed by HP

Juxt Ltd.

Initial release

2008

2012

2018

2014

2019

Current release

7.2.4, September 2012

2.3.0, February 2019

1.19, September 2021

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

GNU Affero GPL V3.0

Open Source

Apache 2.0

Open Source

MIT License

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++

Scala

C++, Java

Clojure

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

with proprietary extensions

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

C
C++
Java
PHP

Java
JavaScript
Objective-C

Java
Kotlin
Scala

All languages supporting JDBC/ODBC/ADO.Net

Clojure
Java

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Java Stored Procedures

Triggers

hooks for callbacks inside the server can be used.

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes, via HBase

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

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

ACID

yes

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes, based on authentication and database rules

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
18 January 2024, Atos

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Google Firebase may have exposed 125M records from misconfigurations
19 March 2024, SC Media

Google launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

provided by Google News

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Share this page