DBMS > Dragonfly vs. FoundationDB vs. Microsoft SQL Server vs. Trafodion

System Properties Comparison Dragonfly vs. FoundationDB vs. Microsoft SQL Server vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded 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

Ordered key-value store. Core features are complimented by layers.

Microsofts flagship relational DBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Key-value store

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

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

Score	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

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

github.com/apple/foundationdb

www.microsoft.com/en-us/sql-server

trafodion.apache.org

Technical documentation

www.dragonflydb.io/docs

apple.github.io/foundationdb

learn.microsoft.com/en-US/sql/sql-server

trafodion.apache.org/documentation.html

Developer

DragonflyDB team and community contributors

FoundationDB

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2023

2013

1989

2014

Current release

1.0, March 2023

6.2.28, November 2020

SQL Server 2022, November 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++, Java

Server operating systems

Linux

Linux
OS X
Windows

Linux
Windows

Linux

Data scheme

scheme-free

schema-free

some layers support schemas

yes

Typing

predefined data types such as float or date

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

some layers support typing

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

supported in specific SQL layer only

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
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

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Lua

in SQL-layer only

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Java Stored Procedures

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

yes, but depending on the SQL-Server Edition

yes, via HBase

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

Linearizable consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

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

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.