DBMS > Dragonfly vs. Microsoft Access vs. RocksDB vs. Trafodion

System Properties Comparison Dragonfly vs. Microsoft Access vs. RocksDB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Transactional SQL-on-Hadoop DBMS

Primary database model

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

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

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

www.microsoft.com/en-us/microsoft-365/access

rocksdb.org

trafodion.apache.org

Technical documentation

www.dragonflydb.io/docs

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

trafodion.apache.org/documentation.html

Developer

DragonflyDB team and community contributors

Microsoft

Facebook, Inc.

Apache Software Foundation, originally developed by HP

Initial release

2023

1992

2013

2014

Current release

1.0, March 2023

1902 (16.0.11328.20222), March 2019

9.2.1, May 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Bundled with Microsoft Office

Open Source

BSD

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

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

scheme-free

yes

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

yes

but not compliant to any SQL standard

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

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

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C
C++
Go
Java
Perl
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Lua

yes

since Access 2010 using the ACE-engine

Java Stored Procedures

Triggers

publish/subscribe channels provide some trigger functionality

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

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

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

ACID

but no files for transaction logging

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

a simple user-level security was built in till version Access 2003

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.