DBMS > Amazon Neptune vs. JanusGraph vs. Snowflake vs. TigerGraph

System Properties Comparison Amazon Neptune vs. JanusGraph vs. Snowflake vs. TigerGraph

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

A Graph DBMS optimized for distributed clusters

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

Cloud-based data warehousing service for structured and semi-structured data

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

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

Score	2.58
Rank	#112	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	1.91
Rank	#135	Overall
	#12	Graph DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	1.83
Rank	#141	Overall
	#13	Graph DBMS

Website

aws.amazon.com/neptune

janusgraph.org

www.snowflake.com

www.tigergraph.com

Technical documentation

aws.amazon.com/neptune/developer-resources

docs.janusgraph.org

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

Amazon

Linux Foundation; originally developed as Titan by Aurelius

Snowflake Computing Inc.

Initial release

2017

2014

2017

Current release

0.6.3, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

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

hosted

Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (GSQL)

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

Clojure
Java
Python

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

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

yes

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.

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Relationships in graphs

yes

Relationships in graphs

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

with encyption-at-rest

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.

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.