DBMS > Amazon DynamoDB vs. Apache Drill vs. Atos Standard Common Repository vs. etcd vs. Geode

System Properties Comparison Amazon DynamoDB vs. Apache Drill vs. Atos Standard Common Repository vs. etcd vs. Geode

Editorial information provided by DB-Engines

Name

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

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

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

A distributed reliable key-value store

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Primary database model

Document store
Key-value store

Document store
Relational DBMS

Document store
Key-value store

Key-value store

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	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Website

aws.amazon.com/dynamodb

drill.apache.org

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

etcd.io
github.com/etcd-io/etcd

geode.apache.org

Technical documentation

docs.aws.amazon.com/dynamodb

drill.apache.org/docs

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

geode.apache.org/docs

Developer

Amazon

Apache Software Foundation

Atos Convergence Creators

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Initial release

2012

2016

2002

Current release

1.20.3, January 2023

1703

3.4, August 2019

1.1, February 2017

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Server operating systems

hosted

Linux
OS X
Windows

Linux

FreeBSD
Linux
Windows

experimental

All OS with a Java VM

the JDK (8 or later) is also required

Data scheme

schema-free

Schema and schema-less with LDAP views

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 SELECT statement is SQL:2003 compliant

SQL-like query language (OQL)

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

LDAP

gRPC
JSON over HTTP

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C++

All languages with LDAP bindings

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
All JVM based languages
C++
Groovy
Java
Scala

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

by integration with AWS Lambda

yes

yes, watching key changes

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source 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 or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

yes, on a single node

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

yes

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

LDAP bind authentication

Access rights per client and object definable

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.