DBMS > Amazon DynamoDB vs. etcd vs. GeoSpock vs. Postgres-XL

System Properties Comparison Amazon DynamoDB vs. etcd vs. GeoSpock vs. Postgres-XL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

A distributed reliable key-value store

Spatial and temporal data processing engine for extreme data scale

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

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

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	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

aws.amazon.com/dynamodb

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

geospock.com

www.postgres-xl.org

Technical documentation

docs.aws.amazon.com/dynamodb

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

www.postgres-xl.org/documentation

Developer

Amazon

GeoSpock

Initial release

2012

2014

since 2012, originally named StormDB

Current release

3.4, August 2019

2.0, September 2019

10 R1, October 2018

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

commercial

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

Java, Javascript

Server operating systems

hosted

FreeBSD
Linux
Windows

experimental

hosted

Linux
macOS

Data scheme

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

gRPC
JSON over HTTP

JDBC

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

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

.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

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

horizontal partitioning

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.

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)

Access rights for users can be defined per table

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.