DBMS > Apache Drill vs. dBASE vs. Lovefield vs. RocksDB vs. SQL.JS

System Properties Comparison Apache Drill vs. dBASE vs. Lovefield vs. RocksDB vs. SQL.JS

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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 relational database for web apps written in pure JavaScript

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

Port of SQLite to JavaScript

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Website

drill.apache.org

www.dbase.com

google.github.io/lovefield

rocksdb.org

sql.js.org

Technical documentation

drill.apache.org/docs

www.dbase.com/support/knowledgebase

github.com/google/lovefield/blob/master/docs/spec_index.md

github.com/facebook/rocksdb/wiki

sql.js.org/documentation/index.html

Developer

Apache Software Foundation

Asthon Tate

Google

Facebook, Inc.

Alon Zakai

enhancements implemented by others

Initial release

2012

1979

2014

2013

2012

Current release

1.20.3, January 2023

dBASE 2019, 2019

2.1.12, February 2017

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache 2.0

Open Source

BSD

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.

Implementation language

JavaScript

C++

JavaScript

Server operating systems

Linux
OS X
Windows

DOS

dBase Classic
Windows

dBase Pro

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

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

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

C++ API
Java API

JavaScript API

Supported programming languages

C++

dBase proprietary IDE

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

user defined functions

The IDE can access stored procedures in other database systems.

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

except by serializing a db to a file

In-memory capabilities

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

Depending on the underlying data source

yes

using MemoryDB

yes

User concepts

Access control

Depending on the underlying data source

Access rights for users and roles

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.