AllegroGraph vs Raphtory
AllegroGraph is a rdf database; Raphtory is a property graph database. AllegroGraph (2004, Proprietary, Common Lisp) ranks #27 this month; Raphtory (2020-12, GPL-3.0, Rust) ranks #32.
| Attribute | AllegroGraph | Raphtory |
|---|---|---|
| At a glance | ||
| Rank | #27 | #32 |
| Score | 56.9 | 55.3 |
| GitHub stars | — | 641 |
| Popularity | 48.5 | 56.1 |
| Activity | 97.5 | 75.7 |
| Community | 36.3 | 30.6 |
| Research | 55.7 | 68.7 |
| Fundamentals | ||
| Description | An RDF triple store with built-in ontology reasoning capabilities. Supports OWL2 RL materialized reasoning for inferring new triples and federated queries across distributed stores. | An in-memory temporal graph database written in Rust with Python and Rust APIs. Tracks graph changes over time with time-traveling queries across historical states. Supports multilayer graph modeling, built-in graph algorithms, and full-text search. Includes a GraphQL server with a bundled exploration UI. |
| Vendor | Franz Inc | Pometry |
| Model | RDF | Property Graph |
| Kind | database | database |
| Category | Established | Emerging |
| First released | 2004 | 2020-12 |
| Status | active | active |
| License | Proprietary | GPL-3.0 |
| Written in | Common Lisp | Rust |
| Query languages | SPARQL, Prolog | GraphQL |
| gdotv support | yes | no |
Feature scores — not surveyed for Raphtory
| Feature | AllegroGraph | Raphtory |
|---|---|---|
| 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 | ✓ | — |
| 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 | ✓ | — |
| Secondary indexes | ✓ | — |
| Server side procedures | ✓ | — |
| Triggers | ✓ | — |
| Authentication | ✓ | — |
| Authorization | ✓ | — |
| Data encryption | · | — |
Links
- AllegroGraph · website · full profile
- Raphtory · website · github · full profile