DBMS > Apache Drill vs. dBASE vs. Elasticsearch vs. Graph Engine

System Properties Comparison Apache Drill vs. dBASE vs. Elasticsearch vs. Graph Engine

Please select another system to include it in the comparison.

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.

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Primary database model

Document store
Relational DBMS

Relational DBMS

Search engine

Graph DBMS
Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	2.89
Rank	#106	Overall
	#20	Document stores
	#55	Relational DBMS

Score	14.33
Rank	#42	Overall
	#26	Relational DBMS

Score	157.69
Rank	#8	Overall
	#1	Search engines

Score	0.91
Rank	#184	Overall
	#16	Graph DBMS
	#30	Key-value stores

Website

drill.apache.org

www.dbase.com

www.elastic.co/elasticsearch

www.graphengine.io

Technical documentation

drill.apache.org/docs

www.dbase.com/support/knowledgebase

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.graphengine.io/docs/manual

Developer

Apache Software Foundation

Asthon Tate

Elastic

Microsoft

Initial release

2012

1979

2010

Current release

1.19.0, June 2021

dBASE 2019, 2019

7.8.0, June 2020

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Elastic License

Open Source

MIT 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

.NET and C

Server operating systems

Linux
OS X
Windows

DOS

dBase Classic
Windows

dBase Pro

All OS with a Java VM

.NET

Data scheme

schema-free

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

Java API
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

C++

dBase proprietary IDE

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Server-side scripts

Stored procedures

user defined functions

The IDE can access stored procedures in other database systems.

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Memcached and Redis integration

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.