AllegroGraph vs TerminusDB
AllegroGraph is a rdf database; TerminusDB is a multiple database. AllegroGraph (2004, Proprietary, Common Lisp) ranks #27 this month; TerminusDB (2019-10, Apache-2.0, Prolog) ranks #34. They differ on 24 of 46 surveyed features.
| Attribute | AllegroGraph | TerminusDB |
|---|---|---|
| At a glance | ||
| Rank | #27 | #34 |
| Score | 56.9 | 53.8 |
| GitHub stars | — | 3.4k |
| Popularity | 48.5 | 61.6 |
| Activity | 97.5 | 68.9 |
| Community | 36.3 | 35.3 |
| Research | 55.7 | 49.6 |
| 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. | A graph database and document store that builds knowledge graphs from JSON documents. Uses git-like delta encoding with an append-only layered data model, enabling version control and collaboration workflows. |
| Vendor | Franz Inc | DFRNT |
| Model | RDF | Multiple |
| Kind | database | database |
| Category | Established | Emerging |
| First released | 2004 | 2019-10 |
| Status | active | active |
| License | Proprietary | Apache-2.0 |
| Written in | Common Lisp | Prolog |
| Query languages | SPARQL, Prolog | WOQL, GraphQL |
| gdotv support | yes | no |
Feature scores 24 of 46 rows differ
| Feature | AllegroGraph | TerminusDB |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | · | 0.75 |
| 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 | · | 0.75 |
| 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 | ✓ | 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 | ✓ | 0.5 |
| 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
- TerminusDB · website · github · full profile