DBMS > Amazon DynamoDB vs. Apache Drill vs. EsgynDB vs. Heroic vs. Linter

System Properties Comparison Amazon DynamoDB vs. Apache Drill vs. EsgynDB vs. Heroic vs. Linter

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

RDBMS for high security requirements

Primary database model

Document store
Key-value store

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Website

aws.amazon.com/dynamodb

drill.apache.org

www.esgyn.cn

github.com/spotify/heroic

linter.ru

Technical documentation

docs.aws.amazon.com/dynamodb

drill.apache.org/docs

spotify.github.io/heroic

Developer

Amazon

Apache Software Foundation

Esgyn

Spotify

relex.ru

Initial release

2012

2015

2014

1990

Current release

1.20.3, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2

commercial

Open Source

Apache 2.0

commercial

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

C++, Java

Java

C and C++

Server operating systems

hosted

Linux
OS X
Windows

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

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

via Elasticsearch

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C++

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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.