DBMS > Apache Phoenix vs. Dgraph vs. RethinkDB vs. SAP HANA

System Properties Comparison Apache Phoenix vs. Dgraph vs. RethinkDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed and scalable native Graph DBMS

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

Primary database model

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

phoenix.apache.org

dgraph.io

rethinkdb.com

www.sap.com/products/hana.html

Technical documentation

Developer

Apache Software Foundation

Dgraph Labs, Inc.

The Linux Foundation

since July 2017

SAP

Initial release

2014

2016

2009

2010

Current release

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

2.4.1, August 2020

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2

commercial

Cloud-based only

Only available as a cloud service

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

Linux
Unix
Windows

Linux
OS X
Windows

Appliance or cloud-service

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC
ODBC

Supported programming languages

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

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

Triggers

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

range based

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Synchronous replication via Raft

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Planned for future releases

yes

users and table-level permissions

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.