DBMS > Apache Phoenix vs. JanusGraph vs. SAP HANA vs. Vitess

System Properties Comparison Apache Phoenix vs. JanusGraph vs. SAP HANA vs. Vitess

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Spatial DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

phoenix.apache.org

janusgraph.org

www.sap.com/products/hana.html

vitess.io

Technical documentation

Developer

Apache Software Foundation

Linux Foundation; originally developed as Titan by Aurelius

SAP

The Linux Foundation, PlanetScale

Initial release

2014

2017

2010

2013

Current release

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

0.6.3, February 2023

2.0 SPS07 (April 4, 2023), April 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

Linux
Unix
Windows

Linux
OS X
Unix
Windows

Appliance or cloud-service

Docker
Linux
macOS

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

Clojure
Java
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

SQLScript, R

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

User authentification and security via Rexster Graph Server

yes

Users with fine-grained authorization concept

no user groups or roles

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.