DBMS > Apache Drill vs. Datomic vs. dBASE vs. EJDB vs. RocksDB

System Properties Comparison Apache Drill vs. Datomic vs. dBASE vs. EJDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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)

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Key-value store

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	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

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

Website

drill.apache.org

www.datomic.com

www.dbase.com

github.com/Softmotions/ejdb

rocksdb.org

Technical documentation

drill.apache.org/docs

docs.datomic.com

www.dbase.com/support/knowledgebase

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

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Cognitect

Asthon Tate

Softmotions

Facebook, Inc.

Initial release

2012

1979

2012

2013

Current release

1.20.3, January 2023

1.0.6735, June 2023

dBASE 2019, 2019

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

commercial

Open Source

GPLv2

Open Source

BSD

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, Clojure

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

DOS

dBase Classic
Windows

dBase Pro

server-less

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

in-process shared library

C++ API
Java API

Supported programming languages

C++

Clojure
Java

dBase proprietary IDE

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Transaction Functions

The IDE can access stored procedures in other database systems.

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

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

Depending on the underlying data source

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

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

recommended only for testing and development

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.