DBMS > Amazon Aurora vs. Amazon Redshift vs. IBM Cloudant vs. LevelDB vs. XTDB

System Properties Comparison Amazon Aurora vs. Amazon Redshift vs. IBM Cloudant vs. LevelDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Large scale data warehouse service for use with business intelligence tools

Database as a Service offering based on Apache CouchDB

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Document store

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

aws.amazon.com/rds/aurora

aws.amazon.com/redshift

www.ibm.com/products/cloudant

github.com/google/leveldb

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.aws.amazon.com/redshift

cloud.ibm.com/docs/Cloudant

github.com/google/leveldb/blob/main/doc/index.md

www.xtdb.com/docs

Developer

Amazon

Amazon (based on PostgreSQL)

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Google

Juxt Ltd.

Initial release

2015

2012

2010

2011

2019

Current release

1.23, February 2021

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

MIT 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

Erlang

C++

Clojure

Server operating systems

hosted

Illumos
Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Objective-C
PHP
Ruby

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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.