DBMS > dBASE vs. MySQL vs. RDF4J vs. Realm

System Properties Comparison dBASE vs. MySQL vs. RDF4J vs. Realm

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

Widely used open source RDBMS

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

RDF store

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	7.41
Rank	#52	Overall
	#8	Document stores

Website

Technical documentation

www.dbase.com/support/knowledgebase

dev.mysql.com/doc

rdf4j.org/documentation

realm.io/docs

Developer

Asthon Tate

Oracle

since 2010, originally MySQL AB, then Sun

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Realm, acquired by MongoDB in May 2019

Initial release

1979

1995

2004

2014

Current release

dBASE 2019, 2019

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

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

Java

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Android
Backend: server-less
iOS
Windows

Data scheme

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

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

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

dBase proprietary IDE

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

Java
PHP
Python

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

proprietary syntax

yes

runs within the applications so server-side scripts are unnecessary

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

not for dBase internal data, but IDE does support transactions when accessing external DBMS

ACID

not for MyISAM storage engine

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-Memory realm

User concepts

Access control

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

yes

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.