DBMS > BigchainDB vs. dBASE vs. MySQL vs. TerminusDB

System Properties Comparison BigchainDB vs. dBASE vs. MySQL vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Document store
RDF store

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

Developer

Asthon Tate

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

2016

1979

1995

2018

Current release

dBASE 2019, 2019

8.3.0, January 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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

Python

C and C++

Prolog, Rust

Server operating systems

Linux

DOS

dBase Classic
Windows

dBase Pro

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

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

SQL-like query language (WOQL)

APIs and other access methods

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

JavaScript
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Multi-source replication
Source-replica replication

Journaling Streams

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

yes

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

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,with MongoDB ord RethinkDB

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

yes

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

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.