DBMS > Amazon DocumentDB vs. Apache Druid vs. Google BigQuery vs. Oracle Berkeley DB vs. SwayDB

System Properties Comparison Amazon DocumentDB vs. Apache Druid vs. Google BigQuery vs. Oracle Berkeley DB vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Large scale data warehouse service with append-only tables

Widely used in-process key-value store

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

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

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

aws.amazon.com/documentdb

druid.apache.org

cloud.google.com/bigquery

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

swaydb.simer.au

Technical documentation

aws.amazon.com/documentdb/resources

druid.apache.org/docs/latest/design

cloud.google.com/bigquery/docs

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

Developer

Apache Software Foundation and contributors

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Simer Plaha

Initial release

2019

2012

2010

1994

2018

Current release

29.0.1, April 2024

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

commercial license available

Open Source

GNU Affero GPL V3.0

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

Java

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

Scala

Server operating systems

hosted

Linux
OS X
Unix

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

schema-less columns are supported

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL for querying

yes

SQL interfaced based on SQLite is available

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
RESTful HTTP/JSON API

RESTful HTTP/JSON API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.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

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes, via HDFS, S3 or other storage engines

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

Atomic single-document operations

Since BigQuery is designed for querying data

ACID

Atomic execution of operations

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

Access rights for users and roles

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.