DBMS > dBASE vs. Dgraph vs. EsgynDB vs. RocksDB vs. VoltDB

System Properties Comparison dBASE vs. Dgraph vs. EsgynDB vs. RocksDB vs. VoltDB

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.

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

www.dbase.com/support/knowledgebase

dgraph.io/docs

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Asthon Tate

Dgraph Labs, Inc.

Esgyn

Facebook, Inc.

VoltDB Inc.

Initial release

1979

2016

2015

2013

2010

Current release

dBASE 2019, 2019

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++, Java

C++

Java, C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

Linux
OS X
Windows

Linux

Linux
OS X

for development

Data scheme

yes

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

dBase proprietary IDE

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

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Java Stored Procedures

Java

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

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

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and roles

Planned for future releases

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.