DBMS > Amazon DynamoDB vs. CouchDB vs. GeoSpock vs. Quasardb

System Properties Comparison Amazon DynamoDB vs. CouchDB vs. GeoSpock vs. Quasardb

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 native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Spatial and temporal data processing engine for extreme data scale

Distributed, high-performance timeseries database

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Time Series 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	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

aws.amazon.com/dynamodb

couchdb.apache.org

geospock.com

quasar.ai

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchdb.org/en/stable

doc.quasar.ai/master

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

GeoSpock

quasardb

Initial release

2012

2005

2009

Current release

3.3.3, December 2023

2.0, September 2019

3.14.1, January 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache version 2

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Erlang

Java, Javascript

C++

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

hosted

BSD
Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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.

Secondary indexes

yes

via views

temporal, categorical

yes

with tags

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

JDBC

HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

View functions in JavaScript

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Automatic sharding

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Immediate 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 operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

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 database

Access rights for users can be defined per table

Cryptographically strong user authentication and audit trail

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.