DBMS > Dragonfly vs. MySQL vs. Realm vs. SAP SQL Anywhere

System Properties Comparison Dragonfly vs. MySQL vs. Realm vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Widely used open source RDBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Secondary database models

Document store
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	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

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

www.mysql.com

realm.io

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

www.dragonflydb.io/docs

dev.mysql.com/doc

realm.io/docs

help.sap.com/docs/SAP_SQL_Anywhere

Developer

DragonflyDB team and community contributors

Oracle

since 2010, originally MySQL AB, then Sun

Realm, acquired by MongoDB in May 2019

SAP

formerly Sybase

Initial release

2023

1995

2014

1992

Current release

1.0, March 2023

8.4.0, April 2024

17, July 2015

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Android
Backend: server-less
iOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

scheme-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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC
Proprietary native API

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

yes, in C/C++, Java, .Net or Perl

Triggers

publish/subscribe channels provide some trigger functionality

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

none

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

table locks or row locks depending on storage engine

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

In-Memory realm

yes

User concepts

Access control

Password-based authentication

Users with fine-grained authorization concept

no user groups or roles

yes

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.