Neptune vs TigerGraph

Neptune is a multiple database; TigerGraph is a property graph database. Neptune (2017-11, Proprietary, C++) ranks #4 this month; TigerGraph (2017-09, Proprietary, C++) ranks #26. They differ on 26 of 46 surveyed features.

Attribute Neptune #4 ▼3 Leader TigerGraph #26 ▲3 Strong
At a glance
Rank #4#26
Score 65.557.0
GitHub stars
Popularity 81.247.8
Activity 95.583.8
Community 53.752.1
Research 58.460.0
Fundamentals
Description A fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries).A distributed property graph database (formerly GraphSQL) built for massively parallel processing and graph analytics. Uses the SQL-like GSQL query language and supports ACID transactions. Available in developer, cloud, and enterprise editions.
Vendor Amazon Web ServicesTigerGraph
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2017-112017-09
Status activeactive
License ProprietaryProprietary
Written in C++C++
Query languages Gremlin, SPARQL, openCypherGSQL
gdotv support yesno

Feature scores 26 of 46 rows differ

Feature NeptuneTigerGraph
Community & Business
Active development
Commercial support
Live community 0.5
Open Source ··
Pricing ·
Trendiness 0.5
Deployment
Containerization ·
Work as dedicated instance
Work as embedded ·
Testing in-memory version ·0.5
Platform
Operating on Linux
Operating on Windows ·0.5
SaaS offering ·
Operations
Automatic updates ·
Client side caching ·
Data versioning support ··
Live backups
Distribution
Cluster Re-balancing ··
Data Distribution ·
High-Availability
Query Distribution 0.5
Replication support 0.5
Developer Experience
Data types defined 0.5
Logging/Auditing 0.5
Object-Graph Mapper ··
Reactive programming ·
Documentation up-to-date 0.75
Binary protocol ·
CLI
GUI
Data Model
Multi-database ·
Graph-native data
REST API
Query Language
Transactions
Granular locking ·
Multiple isolation levels ·
Read committed transaction 0.5
Transaction support
Schema & Security
Constraints ·
Schema support 0.5
Secondary indexes ·
Server side procedures ·
Triggers ··
Authentication
Authorization
Data encryption