DBMS > Amazon DocumentDB vs. Apache Drill vs. Blueflood vs. Oracle

System Properties Comparison Amazon DocumentDB vs. Apache Drill vs. Blueflood vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Scalable TimeSeries DBMS based on Cassandra

Widely used RDBMS

Primary database model

Document store

Document store
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

aws.amazon.com/documentdb

drill.apache.org

blueflood.io

www.oracle.com/database

Technical documentation

aws.amazon.com/documentdb/resources

drill.apache.org/docs

github.com/rax-maas/blueflood/wiki

docs.oracle.com/en/database

Developer

Apache Software Foundation

Rackspace

Oracle

Initial release

2019

2012

2013

1980

Current release

1.20.3, January 2023

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

restricted free version is 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.

Implementation language

Java

C and C++

Server operating systems

hosted

Linux
OS X
Windows

Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

schema-free

predefined scheme

yes

Schemaless in JSON and XML columns

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

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC
RESTful HTTP API

HTTP REST

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C++

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

selectable replication factor

based on Cassandra

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

Access rights for users and roles

Depending on the underlying data source

fine grained access rights according to SQL-standard

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.