DBMS > Amazon DynamoDB vs. Elasticsearch vs. Heroic vs. Percona Server for MySQL

System Properties Comparison Amazon DynamoDB vs. Elasticsearch vs. Heroic vs. Percona Server for MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

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

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Primary database model

Document store
Key-value store

Search engine

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Website

aws.amazon.com/dynamodb

www.elastic.co/elasticsearch

github.com/spotify/heroic

www.percona.com/software/mysql-database/percona-server

Technical documentation

docs.aws.amazon.com/dynamodb

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

spotify.github.io/heroic

www.percona.com/downloads/Percona-Server-LATEST

Developer

Amazon

Elastic

Spotify

Percona

Initial release

2012

2010

2014

2008

Current release

8.6, January 2023

8.0.36-28, 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Elastic License

Open Source

Apache 2.0

Open Source

GPL version 2

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

C and C++

Server operating systems

hosted

All OS with a Java VM

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

via Elasticsearch

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP/JSON API

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

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication
XtraDB Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

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

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Memcached and Redis integration

yes

User concepts

Access control

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

Users with fine-grained authorization concept

no user groups or 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.