Neptune vs Sparksee

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

Attribute Neptune #4 ▼3 Leader Sparksee #98 ▲20 Growing
At a glance
Rank #4#98
Score 65.538.3
GitHub stars
Popularity 81.226.1
Activity 95.531.9
Community 53.735.3
Research 58.449.8
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 property graph database (formerly DEX) that stores graphs as labelled multigraphs using bitmap data structures for compact representation. Supports ACID transactions and offers free licenses for evaluation and research use.
Vendor Amazon Web ServicesSparsity Technologies
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2017-112008
Status activeactive
License ProprietaryProprietary
Written in C++C++
Query languages Gremlin, SPARQL, openCypheropenCypher
gdotv support yesno

Feature scores 23 of 46 rows differ

Feature NeptuneSparksee
Community & Business
Active development ·
Commercial support
Live community ·
Open Source ··
Pricing ·
Trendiness 0.5
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