DBMS > Amazon Aurora vs. BoltDB vs. CouchDB vs. EJDB vs. RocksDB

System Properties Comparison Amazon Aurora vs. BoltDB vs. CouchDB vs. EJDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

MySQL and PostgreSQL compatible cloud service by Amazon

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

aws.amazon.com/rds/aurora

github.com/boltdb/bolt

couchdb.apache.org

github.com/Softmotions/ejdb

rocksdb.org

Technical documentation

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

docs.couchdb.org/en/stable

github.com/Softmotions/ejdb/blob/master/README.md

github.com/facebook/rocksdb/wiki

Developer

Amazon

Apache Software Foundation

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

Softmotions

Facebook, Inc.

Initial release

2015

2013

2005

2012

2013

Current release

3.3.3, December 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache version 2

Open Source

GPLv2

Open Source

BSD

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

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

Android
BSD
Linux
OS X
Solaris
Windows

server-less

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

via views

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP/JSON API

in-process shared library

C++ API
Java API

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

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding

improved architecture with release 2.0

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

yes

atomic operations within a single document possible

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Read/Write Locking

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.

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.