Neptune vs RDF::Trine

Neptune is a multiple database; RDF::Trine is a rdf database. Neptune (2017-11, Proprietary, C++) ranks #4 this month; RDF::Trine (2008-02, Artistic-1.0-Perl OR GPL-1.0-or-later, Perl) ranks #63.

Attribute Neptune #4 ▼3 Leader RDF::Trine #63 ▼1 Growing
At a glance
Rank #4#63
Score 65.546.0
GitHub stars 26
Popularity 81.251.0
Activity 95.533.1
Community 53.749.2
Research 58.449.6
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 Perl RDF framework providing triple store abstractions with in-memory and DBI-backed (MySQL, PostgreSQL, SQLite) storage backends, plus parsers for RDF/XML, Turtle, RDFa, and RDF/JSON.
Vendor Amazon Web ServicesGregory Todd Williams
Model MultipleRDF
Kind databaselibrary
Category EnterpriseEmerging
First released 2017-112008-02
Status activeinactive — Deprecated in favour of the Attean framework. Last release was v1.019 in January 2018.
License ProprietaryArtistic-1.0-Perl OR GPL-1.0-or-later
Written in C++Perl
Query languages Gremlin, SPARQL, openCypherSPARQL
gdotv support yesno

Feature scores — not surveyed for RDF::Trine

Feature NeptuneRDF::Trine
Community & Business
Active development
Commercial support
Live community
Open Source ·
Pricing
Trendiness
Deployment
Containerization ·
Work as dedicated instance
Work as embedded ·
Testing in-memory version ·
Platform
Operating on Linux
Operating on Windows ·
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
Developer Experience
Data types defined 0.5
Logging/Auditing
Object-Graph Mapper ·
Reactive programming
Documentation up-to-date
Binary protocol
CLI
GUI
Data Model
Multi-database ·
Graph-native data
REST API
Query Language
Transactions
Granular locking
Multiple isolation levels
Read committed transaction
Transaction support
Schema & Security
Constraints
Schema support 0.5
Secondary indexes
Server side procedures ·
Triggers ·
Authentication
Authorization
Data encryption