Kowari vs Neptune

Kowari is a rdf database; Neptune is a multiple database. Kowari (2003-10, MPL-1.1, Java) is not ranked this month; Neptune (2017-11, Proprietary, C++) ranks #4.

Attribute Kowari Neptune #4 ▼3 Leader
At a glance
Rank — Not ranked#4
Score 65.5
GitHub stars
Popularity 81.2
Activity 95.5
Community 53.7
Research 58.4
Fundamentals
Description An RDF triple store written in Java with its own iTQL query language and Lucene full-text indexing, open-sourced by Tucana Technologies from the storage layer of its commercial knowledge server. Development stopped after Northrop Grumman acquired Tucana's assets in 2005; continued as the Mulgara fork.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 Tucana TechnologiesAmazon Web Services
Model RDFMultiple
Kind databasedatabase
Category EmergingEnterprise
First released 2003-102017-11
Status deprecated — No longer developed. Continued as the Mulgara fork from 2005.active
License MPL-1.1Proprietary
Written in JavaC++
Query languages iTQLGremlin, SPARQL, openCypher
gdotv support noyes

Feature scores — not surveyed for Kowari

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