DBMS > Blazegraph vs. JanusGraph vs. Memcached vs. SAP HANA

System Properties Comparison Blazegraph vs. JanusGraph vs. Memcached 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

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 key-value store, originally intended for caching

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	0.75
Rank	#219	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

blazegraph.com

janusgraph.org

www.memcached.org

www.sap.com/products/hana.html

Technical documentation

wiki.blazegraph.com

docs.janusgraph.org

github.com/memcached/memcached/wiki

help.sap.com/hana

Developer

Blazegraph

Linux Foundation; originally developed as Titan by Aurelius

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SAP

Initial release

2006

2017

2003

2010

Current release

2.1.5, March 2019

0.6.3, February 2023

1.6.25, March 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

extended commercial license available

Open Source

Apache 2.0

Open Source

BSD license

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
OS X
Windows

Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

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

SPARQL is used as query language

yes

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Proprietary protocol

JDBC
ODBC

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Clojure
Java
Python

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

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)

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Repcached, a Memcached patch, provides this functionallity

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

User authentification and security via Rexster Graph Server

yes

using SASL (Simple Authentication and Security Layer) protocol

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.