Dydra vs Neptune

Dydra is a rdf database; Neptune is a multiple database. Dydra (2011, Proprietary, Common Lisp) ranks #79 this month; Neptune (2017-11, Proprietary, C++) ranks #4.

Attribute Dydra #79 ▲20 Growing Neptune #4 ▼3 Leader
At a glance
Rank #79#4
Score 42.365.5
GitHub stars
Popularity 58.181.2
Activity 95.5
Community 54.253.7
Research 50.458.4
Fundamentals
Description A cloud-hosted RDF triplestore written in Common Lisp with a revisioned graph store that maintains versioned snapshots of previous states, queryable via a REVISION clause in SPARQL. Uses LMDB for storage and RonDB for scaled deployments. Supports MQTT streaming for incremental changes.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).
Vendor Datagraph GmbHAmazon Web Services
Model RDFMultiple
Kind databasedatabase
Category EmergingEnterprise
First released 20112017-11
Status inactive — Public SDK last updated 2012. Core engine is closed-source with limited visibility.active
License ProprietaryProprietary
Written in Common LispC++
Query languages SPARQL, GraphQLGremlin, SPARQL, openCypher
gdotv support noyes

Feature scores — not surveyed for Dydra

Feature DydraNeptune
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