DBMS > Amazon Redshift vs. Dragonfly vs. Firebase Realtime Database vs. SQLite

System Properties Comparison Amazon Redshift vs. Dragonfly vs. Firebase Realtime Database vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

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 embeddable, in-process RDBMS

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

aws.amazon.com/redshift

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

firebase.google.com/products/realtime-database

www.sqlite.org

Technical documentation

docs.aws.amazon.com/redshift

www.dragonflydb.io/docs

firebase.google.com/docs/database

www.sqlite.org/docs.html

Developer

Amazon (based on PostgreSQL)

DragonflyDB team and community contributors

Google

acquired by Google 2014

Dwayne Richard Hipp

Initial release

2012

2023

2012

2000

Current release

1.0, March 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

BSL 1.1

commercial

Open Source

Public Domain

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

Server operating systems

hosted

Linux

hosted

server-less

Data scheme

yes

scheme-free

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

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

yes

not rigid because of 'dynamic typing' concept.

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protocol

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages supporting JDBC/ODBC

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

limited functionality with using 'rules'

Triggers

publish/subscribe channels provide some trigger functionality

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

via file-system locks

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

fine grained access rights according to SQL-standard

Password-based authentication

yes, based on authentication and database rules

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.