"Fluree: an Immutable, Verifiable, Shareable Database"
summary
Describes a working graph database that stores RDF triples as an immutable ledger with temporal semantics, integer compaction, and signed transactions so provenance and tamper evidence are queryable. Implements HTTP JSON APIs and JSON-LD first‑class support, accepts SPARQL/SQL/GraphQL and an EQL‑style query shape, and pushes authentication and authorization into the database. Claims federated JOINs, vocabulary mapping via OWL inference, and live use in pre‑alpha deployments with public repos and docs.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:53Problem of shipping before containers
- 5:28Why shipping was expensive
- 7:38Broken data sharing
- 15:06Simplifying data sharing
- 18:24Semantic web and RDF
- 22:18Standardizing APIs
- 25:28Fluree’s immutable graph DB
- 30:52Cheap verifiable sharing
- 35:50Rapid application development with Fluree
- 37:34Data provenance in Fluree
- 38:39Fluree state and future
- 40:26Getting started with Fluree
related talks
01h 06mFluree - Cloud-Native Ledger Graph Database
48mA Query Layer for Dapps
26mPutting the Decentralization in DeFi: Addressing the Critical Problem of Data in Crypto
23mSRFI-167, SRFI-168 and the functional store
05mPatrick Reilly - Ignite OSCON 2014
42mA Practical Functional Relational Architecture
01h 06mDesign and Implementation of the RelationalAI Knowledge Graph Management System
26mGraph Databases will change your (freakin') life