DBMS > Amazon Neptune vs. Google BigQuery vs. Hive vs. JanusGraph

System Properties Comparison Amazon Neptune vs. Google BigQuery vs. Hive vs. JanusGraph

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

Large scale data warehouse service with append-only tables

data warehouse software for querying and managing large distributed datasets, built on Hadoop

A Graph DBMS optimized for distributed clusters

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

Primary database model

Graph DBMS
RDF store

Relational DBMS

Graph 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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Website

aws.amazon.com/neptune

cloud.google.com/bigquery

hive.apache.org

janusgraph.org

Technical documentation

aws.amazon.com/neptune/developer-resources

cloud.google.com/bigquery/docs

cwiki.apache.org/confluence/display/Hive/Home

docs.janusgraph.org

Developer

Amazon

Google

Apache Software Foundation

initially developed by Facebook

Linux Foundation; originally developed as Titan by Aurelius

Initial release

2017

2010

2012

2017

Current release

3.1.3, April 2022

0.6.3, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache 2.0

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

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Unix
Windows

Data scheme

schema-free

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

SQL-like DML and DDL statements

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

RESTful HTTP/JSON API

JDBC
ODBC
Thrift

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Java
PHP
Python

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

user defined functions and integration of map-reduce

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

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

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.

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying 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

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)

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users, groups and roles

User authentification and security via Rexster Graph Server

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.