4store vs JanusGraph

4store is a rdf database; JanusGraph is a property graph database. 4store (2009-10, GPL-3.0, C) ranks #77 this month; JanusGraph (2017-04, Apache-2.0, Java) ranks #10.

Attribute 4store #77 ▼4 Growing JanusGraph #10 ▲13 Strong
At a glance
Rank #77#10
Score 36.158.6
GitHub stars 2995.9k
Popularity 45.973.4
Activity 28.165.3
Community 37.139.5
Research 31.047.0
Fundamentals
Description An RDF triple store written in C, originally developed at Garlik for identity protection workloads. Supports single-machine and clustered deployments using the Raptor and Rasqal RDF libraries for parsing and query processing.An open-source distributed property graph database forked from the Titan codebase. Supports pluggable storage backends (Cassandra, HBase, BerkeleyDB) with ACID transactions and native TinkerPop integration.
Vendor GarlikThe Linux Foundation
Model RDFProperty Graph
Kind databasedatabase
Category EmergingEstablished
First released 2009-102017-04
Status inactive — Sporadic maintenance only. Originally developed circa 2009.active
License GPL-3.0Apache-2.0
Written in CJava
Query languages SPARQLGremlin
gdotv support noyes

Feature scores — not surveyed for 4store

Feature 4storeJanusGraph
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 —·
Replication support —✓
Developer Experience
Data types defined —✓
Logging/Auditing —✓
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 —0.5
Multiple isolation levels —0.5
Read committed transaction —0.5
Transaction support —✓
Schema & Security
Constraints —✓
Schema support —✓
Secondary indexes —✓
Server side procedures —·
Triggers —0.5
Authentication —✓
Authorization —✓
Data encryption —·