DBMS > dBASE vs. EJDB vs. Newts vs. Spark SQL vs. Transbase

System Properties Comparison dBASE vs. EJDB vs. Newts vs. Spark SQL vs. Transbase

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.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Time Series DBMS based on Cassandra

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

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

Score	14.33
Rank	#42	Overall
	#26	Relational DBMS

Score	0.10
Rank	#314	Overall
	#41	Document stores

Score	0.00
Rank	#354	Overall
	#33	Time Series DBMS

Score	22.86
Rank	#35	Overall
	#21	Relational DBMS

Score	0.07
Rank	#325	Overall
	#147	Relational DBMS

Website

www.dbase.com

ejdb.org

opennms.github.io/newts

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

Technical documentation

www.dbase.com/support/knowledgebase

github.com/Softmotions/ejdb/blob/master/README.md

github.com/OpenNMS/newts/wiki

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

Developer

Asthon Tate

Softmotions

OpenNMS Group

Apache Software Foundation

Transaction Software GmbH

Initial release

1979

2012

2014

1987

Current release

dBASE 2019, 2019

3.2.0, October 2021

Transbase 8.4, September 2020

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

free development license

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

Java

Scala

C and C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

server-less

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL-like DML and DDL statements

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

in-process shared library

HTTP REST
Java API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

dBase proprietary IDE

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Java

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on Cassandra

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

User concepts

Access control

Access rights for users and roles

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.