DBMS > Amazon Aurora vs. ClickHouse vs. FoundationDB vs. GeoSpock vs. Oracle Berkeley DB

System Properties Comparison Amazon Aurora vs. ClickHouse vs. FoundationDB vs. GeoSpock vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

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

Description

MySQL and PostgreSQL compatible cloud service by Amazon

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Ordered key-value store. Core features are complimented by layers.

Spatial and temporal data processing engine for extreme data scale

Widely used in-process key-value store

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Document store

Time Series DBMS

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Website

aws.amazon.com/rds/aurora

clickhouse.com

github.com/apple/foundationdb

geospock.com

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

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

clickhouse.com/docs

apple.github.io/foundationdb

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Amazon

Clickhouse Inc.

FoundationDB

GeoSpock

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2015

2016

2013

1994

Current release

v24.4.1.2088-stable, May 2024

6.2.28, November 2020

2.0, September 2019

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Open Source

commercial license available

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.

ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

C++

Java, Javascript

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

FreeBSD
Linux
macOS

Linux
OS X
Windows

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

schema-free

some layers support schemas

yes

schema-free

Typing

predefined data types such as float or date

yes

some layers support typing

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

only with the Berkeley DB XML edition

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

yes

Close to ANSI SQL (SQL/JSON + extensions)

supported in specific SQL layer only

ANSI SQL for query only (using Presto)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

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

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

in SQL-layer only

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

key based and custom

Sharding

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

in SQL-layer only

Transaction concepts

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

ACID

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Access rights for users can be defined per table

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.