DBMS > Amazon DocumentDB vs. Oracle vs. Percona Server for MongoDB vs. Qdrant

System Properties Comparison Amazon DocumentDB vs. Oracle vs. Percona Server for MongoDB vs. Qdrant

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

Widely used RDBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

A high-performance vector database with neural network or semantic-based matching

Primary database model

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	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Website

aws.amazon.com/documentdb

www.oracle.com/database

www.percona.com/mongodb/software/percona-server-for-mongodb

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

aws.amazon.com/documentdb/resources

docs.oracle.com/en/database

docs.percona.com/percona-distribution-for-mongodb

qdrant.tech/documentation

Developer

Oracle

Percona

Qdrant

Initial release

2019

1980

2015

2021

Current release

23c, September 2023

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL Version 2

Open Source

Apache Version 2.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

C and C++

C++

Rust

Server operating systems

hosted

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

Linux

Docker
Linux
macOS
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

proprietary protocol using JSON

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication
Source-replica replication

Source-replica replication

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency, tunable 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

In-memory capabilities

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

yes

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

yes

via In-Memory Engine

yes

User concepts

Access control

Access rights for users and roles

fine grained access rights according to SQL-standard

Access rights for users and roles

Key-based authentication

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.