DBMS > Dragonfly vs. Firebird vs. Oracle Rdb vs. Snowflake vs. Teradata Aster

System Properties Comparison Dragonfly vs. Firebird vs. Oracle Rdb vs. Snowflake vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines 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

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

Cloud-based data warehousing service for structured and semi-structured data

Platform for big data analytics on multistructured data sources and types

Primary database model

Key-value store

Relational DBMS

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

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

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

www.firebirdsql.org

www.oracle.com/database/technologies/related/rdb.html

www.snowflake.com

Technical documentation

www.dragonflydb.io/docs

www.firebirdsql.org/en/reference-manuals

www.oracle.com/database/technologies/related/rdb-doc.html

docs.snowflake.net/manuals/index.html

Developer

DragonflyDB team and community contributors

Firebird Foundation

Oracle, originally developed by Digital Equipment Corporation (DEC)

Snowflake Computing Inc.

Teradata

Initial release

2023

2000

As fork of Borland's InterBase

1984

2014

2005

Current release

1.0, March 2023

5.0.0, January 2024

7.4.1.1, 2021

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Initial Developer's Public License

commercial

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

C and C++

Server operating systems

Linux

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

HP Open VMS

hosted

Linux

Data scheme

scheme-free

yes

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

yes

support of semi-structured data formats (JSON, XML, Avro)

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

defined schema within the relational store; partial schema or schema free in the Aster File Store

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.

yes

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

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

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

Lua

PSQL

user defined functions

R packages

Triggers

publish/subscribe channels provide some trigger functionality

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

ACID

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

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

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

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable authentication

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.