Blazegraph Database Platform · Blazegraph™ DB is our ultra high-performance graph database supporting Blueprints and RDF/SPARQL APIs. It supports up to 50 Billion edges on a single machine and has a High Availability and Scale-out architecture. It is in production use for customers such as EMC, Syapse, Wikidata Query Service, the British Museum, and many others. GPU acceleration and High Availability (HA) are available in the Enterprise edition. It contains war, jar, deb, rpm, and tar.gz deployment artifacts.
Group: com.blazegraph - All Dependencies
Blazegraph Executable Jar · Blazegraph Executable Jar file. All files required to run Blazegraph DB in a single jar.
blazegraph-gremlin · Welcome to the Blazegraph/TinkerPop3 project. The TP3 implementation has some significant differences from the TP2 version. The data model has been changed to use RDF*, an RDF reification framework described here: https://wiki.blazegraph.com/wiki/index.php/Reification_Done_Right. The concept behind blazegraph-gremlin is that property graph (PG) data can be loaded and accessed via the TinkerPop3 API, but underneath the hood the data will be stored as RDF using the PG data model described in this document. Once PG data has been loaded you can interact with it just like you would interact with ordinary RDF - you can run SPARQL queries or interact with the data via the SAIL API. It just works. The PG data model is also customizable via a round-tripping interface called the BlazeValueFactory, also described in detail in this document.
Blazegraph Executable Jar (bigdata legacy path) · Single Executable Jar file for running the Blazegraph DB platform
Blazegraph-Based TPF Server · This is a Linked Data Fragment (LDF) server that provides a Triple Pattern Fragment (TPF) interface using the Blazegraph graph database as backend.
Blazegraph Deployment Artifacts · Parent POM for Blazegraph Deployment (war, jar, deb, rpm, tgz) artifacts
Blazegraph Vocabularies · Blazegraph Custom Vocabularies and Inline URI Handlers for commonly used data sets.