DBMS > Apache Drill vs. Elasticsearch vs. Graph Engine vs. Snowflake vs. Tarantool

System Properties Comparison Apache Drill vs. Elasticsearch vs. Graph Engine vs. Snowflake vs. Tarantool

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

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

Cloud-based data warehousing service for structured and semi-structured data

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Relational DBMS

Search engine

Graph DBMS
Key-value store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

drill.apache.org

www.elastic.co/elasticsearch

www.graphengine.io

www.snowflake.com

www.tarantool.io

Technical documentation

drill.apache.org/docs

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

www.graphengine.io/docs/manual

docs.snowflake.net/manuals/index.html

www.tarantool.io/en/doc

Developer

Apache Software Foundation

Elastic

Microsoft

Snowflake Computing Inc.

Initial release

2012

2010

2014

2008

Current release

1.20.3, January 2023

8.6, January 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Elastic License

Open Source

MIT License

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

.NET and C

C and C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

.NET

hosted

BSD
Linux
macOS

Data scheme

schema-free

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

yes

support of semi-structured data formats (JSON, XML, Avro)

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like query language

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Java API
RESTful HTTP/JSON API

RESTful HTTP API

CLI Client
JDBC
ODBC

Open binary protocol

Supported programming languages

C++

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

C#
C++
F#
Visual Basic

JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Lua, C and SQL stored procedures

Triggers

yes

by using the 'percolation' feature

similar concept for controling cloud resources

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

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

yes

yes, write ahead logging

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Depending on the underlying data source

Users with fine-grained authorization concept, user roles and pluggable authentication

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
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.