DBMS > Apache Drill vs. Elasticsearch vs. RocksDB vs. Teradata

System Properties Comparison Apache Drill vs. Elasticsearch vs. RocksDB vs. Teradata

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

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

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

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Document store
Relational DBMS

Search engine

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series 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	132.83
Rank	#7	Overall
	#1	Search engines

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

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

drill.apache.org

www.elastic.co/elasticsearch

rocksdb.org

www.teradata.com

Technical documentation

drill.apache.org/docs

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

github.com/facebook/rocksdb/wiki

docs.teradata.com

Developer

Apache Software Foundation

Elastic

Facebook, Inc.

Teradata

Initial release

2012

2010

2013

1984

Current release

1.20.3, January 2023

8.6, January 2023

9.2.1, May 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Elastic License

Open Source

BSD

commercial

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

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux

hosted
Linux

Data scheme

schema-free

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

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.

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

yes

SQL 2016 + extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Java API
RESTful HTTP/JSON API

C++ API
Java API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C++

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

C
C++
Go
Java
Perl
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

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

Memcached and Redis integration

yes

User concepts

Access control

Depending on the underlying data source

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.