This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-24
Channels
- # aleph (1)
- # babashka (2)
- # beginners (25)
- # calva (5)
- # cider (8)
- # cljdoc (4)
- # clojure (81)
- # clojure-europe (41)
- # clojure-spec (11)
- # clojurescript (7)
- # conjure (1)
- # data-science (1)
- # datomic (25)
- # defnpodcast (3)
- # events (2)
- # figwheel-main (8)
- # fulcro (5)
- # helix (4)
- # hugsql (1)
- # java (2)
- # off-topic (35)
- # onyx (18)
- # pathom (8)
- # rdf (5)
- # re-frame (9)
- # reagent (3)
- # reitit (1)
- # shadow-cljs (39)
- # tools-deps (53)
- # xtdb (23)
I just discovered Fluree which is apparently some kind of blockchain RDF triple store written in Clojure that seems to be queried using Datalog: • https://docs.flur.ee/guides/0.15.0/intro/what-is-fluree • https://flur.ee/why-fluree/ • https://github.com/fluree I have been reading the whats and whys, but I don’t really understand the purpose of it. It seems to have a tonne of documentation though. I’m guessing it’s meant for fintech stuff? I am trying to figure out what to think of it. Anybody here know what the deal is?
There are a few use cases where true immutability in a graph database has a significant business value, for example land owning rights for a country. But in times of GDPR, if a company is interested in immutable databases then they mostly need overridable immutability (to delete GDPR relevant data). It is possible to build something like this on a blockchain using anonymous identifiers but then you loose a lot of the advantages of a graph databases…. I don’t know how Fluree is addressing this issue.