DBMS > Amazon DynamoDB vs. Apache Impala vs. Atos Standard Common Repository vs. Drizzle vs. Ehcache

System Properties Comparison Amazon DynamoDB vs. Apache Impala vs. Atos Standard Common Repository vs. Drizzle vs. Ehcache

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

Analytic DBMS for Hadoop

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A widely adopted Java cache with tiered storage options

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Key-value store

Relational DBMS

Key-value store

Secondary database models

Document store

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

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Website

aws.amazon.com/dynamodb

impala.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.ehcache.org

Technical documentation

docs.aws.amazon.com/dynamodb

impala.apache.org/impala-docs.html

www.ehcache.org/documentation

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

Terracotta Inc, owned by Software AG

Initial release

2012

2013

2016

2008

2009

Current release

4.1.0, June 2022

1703

7.2.4, September 2012

3.10.0, March 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2

commercial

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available

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

C++

Java

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X

All OS with a Java VM

Data scheme

schema-free

yes

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

LDAP

JDBC

JCache

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages supporting JDBC/ODBC

All languages with LDAP bindings

C
C++
Java
PHP

Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Triggers

yes

by integration with AWS Lambda

yes

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

by using Terracotta Server

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Tunable Consistency (Strong, Eventual, Weak)

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

Atomic execution of specific operations

ACID

yes

supports JTA and can work as an XA resource

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

In-memory capabilities

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

yes

User concepts

Access control

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

LDAP bind authentication

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.