DBMS > Amazon DynamoDB vs. CouchDB vs. OrigoDB vs. QuestDB vs. SAP SQL Anywhere

System Properties Comparison Amazon DynamoDB vs. CouchDB vs. OrigoDB vs. QuestDB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

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.

A fully ACID in-memory object graph database

A high performance open source SQL database for time series data

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Document store
Key-value store

Document store

Document store
Object oriented DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Relational DBMS

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	7.46
Rank	#51	Overall
	#7	Document stores

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Website

aws.amazon.com/dynamodb

couchdb.apache.org

origodb.com

questdb.io

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchdb.org/en/stable

origodb.com/docs

questdb.io/docs

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Amazon

Apache Software Foundation

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

Robert Friberg et al

QuestDB Technology Inc

SAP

formerly Sybase

Initial release

2012

2005

2009

under the name LiveDB

2014

1992

Current release

3.3.3, December 2023

17, July 2015

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache version 2

Open Source

Apache 2.0

commercial

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 (Zero-GC), C++, Rust

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL with time-series extensions

yes

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

ADO.NET
HTTP API
JDBC
ODBC

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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

yes, in C/C++, Java, .Net or Perl

Triggers

yes

by integration with AWS Lambda

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning (by timestamps)

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Source-replica replication

Source-replica replication with eventual consistency

Source-replica replication

Database mirroring

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

ACID

ACID for single-table writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

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

yes

through memory mapped files

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 can be defined per database

Role based authorization

fine grained access rights according to SQL-standard

More information provided by the system vendor

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Weather data visualization and forecasting with QuestDB, Kafka and Grafana
4 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

Write Time: a call for community writers
13 August 2024

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.