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

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

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

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

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

Primary database model

Secondary database models

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.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

phoenix.apache.org

blazegraph.com

janusgraph.org

www.sap.com/products/hana.html

Technical documentation

Developer

Apache Software Foundation

Blazegraph

Linux Foundation; originally developed as Titan by Aurelius

SAP

Initial release

2014

2006

2017

2010

Current release

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

2.1.5, March 2019

0.6.3, February 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

extended commercial license available

Open Source

Apache 2.0

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

Server operating systems

Linux
Unix
Windows

Linux
OS X
Windows

Linux
OS X
Unix
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

RDF literal types

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

SPARQL is used as query language

yes

APIs and other access methods

JDBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
ODBC

Supported programming languages

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

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

yes

SQLScript, R

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

Security and Authentication via Web Application Container (Tomcat, Jetty)

User authentification and security via Rexster Graph Server

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.