DBMS > Amazon DocumentDB vs. Apache Phoenix vs. OceanBase vs. SAP HANA

System Properties Comparison Amazon DocumentDB vs. Apache Phoenix vs. OceanBase vs. SAP HANA

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

A distributed, high available RDBMS compatible with Oracle and MySQL

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Wide column store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.91
Rank	#124	Overall
	#22	Document stores

Score	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	1.97
Rank	#119	Overall
	#58	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

aws.amazon.com/documentdb

phoenix.apache.org

en.oceanbase.com

www.sap.com/products/hana.html

Technical documentation

aws.amazon.com/documentdb/resources

phoenix.apache.org

en.oceanbase.com/docs/oceanbase-database

help.sap.com/hana

Developer

Apache Software Foundation

OceanBase

previously Alibaba and Ant Group

SAP

Initial release

2019

2014

2010

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

4.3.0, April 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

hosted

Linux
Unix
Windows

Linux

Appliance or cloud-service

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

yes

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

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

Server-side scripts

Stored procedures

user defined functions

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

yes

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

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

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

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access rights for users, groups and roles according to SQL-standard

yes

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.