DBMS > Dragonfly vs. FatDB vs. Firebase Realtime Database vs. SAP HANA

System Properties Comparison Dragonfly vs. FatDB vs. Firebase Realtime Database vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

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

Primary database model

Key-value store

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/dragonflydb/dragonfly
www.dragonflydb.io

firebase.google.com/products/realtime-database

www.sap.com/products/hana.html

Technical documentation

www.dragonflydb.io/docs

firebase.google.com/docs/database

help.sap.com/hana

Developer

DragonflyDB team and community contributors

FatCloud

Google

acquired by Google 2014

SAP

Initial release

2023

2012

2010

Current release

1.0, March 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

BSL 1.1

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

Server operating systems

Linux

Windows

hosted

Appliance or cloud-service

Data scheme

scheme-free

schema-free

yes

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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

Via inetgration in SQL Server

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

Java
JavaScript
Objective-C

Server-side scripts

Stored procedures

Lua

yes

via applications

limited functionality with using 'rules'

SQLScript, R

Triggers

publish/subscribe channels provide some trigger functionality

yes

via applications

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

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

Atomic execution of command blocks and scripts

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

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

User concepts

Access control

Password-based authentication

Can implement custom security layer via applications

yes, based on authentication and database rules

yes

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.