DBMS > Amazon DynamoDB vs. Drizzle vs. Memcached vs. Postgres-XL

System Properties Comparison Amazon DynamoDB vs. Drizzle vs. Memcached vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

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

In-memory key-value store, originally intended for caching

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial 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	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

aws.amazon.com/dynamodb

www.memcached.org

www.postgres-xl.org

Technical documentation

docs.aws.amazon.com/dynamodb

github.com/memcached/memcached/wiki

www.postgres-xl.org/documentation

Developer

Amazon

Drizzle project, originally started by Brian Aker

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Initial release

2012

2008

2003

2014

since 2012, originally named StormDB

Current release

7.2.4, September 2012

1.6.27, May 2024

10 R1, October 2018

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

GNU GPL

Open Source

BSD license

Open Source

Mozilla public license

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++

Server operating systems

hosted

FreeBSD
Linux
OS X

FreeBSD
Linux
OS X
Unix
Windows

Linux
macOS

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

JDBC

Proprietary protocol

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C++
Java
PHP

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

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

MVCC

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.

User concepts

Access control

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

using SASL (Simple Authentication and Security Layer) protocol

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.