DBMS > Amazon Neptune vs. AnzoGraph DB vs. SAP HANA vs. VoltDB

System Properties Comparison Amazon Neptune vs. AnzoGraph DB vs. SAP HANA vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Graph DBMS
RDF store

Relational DBMS

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	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/neptune

cambridgesemantics.com/anzograph

www.sap.com/products/hana.html

www.voltdb.com

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

help.sap.com/hana

docs.voltdb.com

Developer

Amazon

Cambridge Semantics

SAP

VoltDB Inc.

Initial release

2017

2018

2010

Current release

2.3, January 2021

2.0 SPS07 (April 4, 2023), April 2023

11.3, April 2022

License

Commercial or Open Source

commercial

free trial version available

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Appliance or cloud-service

Linux
OS X

for development

Data scheme

schema-free

Schema-free and OWL/RDFS-schema support

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

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

only a subset of SQL 99

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C++
Java
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

SQLScript, R

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

Multi-source replication in MPP-Cluster

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

not needed in graphs

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

Snapshots and command logging

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 can be defined via the AWS Identity and Access Management (IAM)

Access rights for users and roles

yes

Users and roles with access to stored procedures

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.