DBMS > Dragonfly vs. jBASE vs. Microsoft Access vs. MySQL vs. PostGIS

System Properties Comparison Dragonfly vs. jBASE vs. Microsoft Access vs. MySQL vs. PostGIS

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

A robust multi-value DBMS comprising development tools and middleware

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

Widely used open source RDBMS

Spatial extension of PostgreSQL

Primary database model

Key-value store

Multivalue DBMS

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational 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.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

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

www.mysql.com

postgis.net

Technical documentation

www.dragonflydb.io/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

developer.microsoft.com/en-us/access

dev.mysql.com/doc

postgis.net/documentation

Developer

DragonflyDB team and community contributors

Rocket Software (formerly Zumasys)

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2023

1991

1992

1995

2005

Current release

1.0, March 2023

5.7

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.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.

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

AIX
Linux
Windows

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

scheme-free

schema-free

yes

Typing

predefined data types such as float or date

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

optional

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

Embedded SQL for jBASE in BASIC

yes

but not compliant to any SQL standard

yes

with proprietary extensions

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

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
Basic
Jabbascript
Java

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

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

Server-side scripts

Stored procedures

Lua

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

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

but no files for transaction logging

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

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

Access rights can be defined down to the item level

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

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

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.