[Wikidata-bugs] [Maniphest] T289760: Evaluate Oxigraph as alternative to Blazegraph

2021-11-19 Thread BenAtOlive
BenAtOlive added a comment. @Thadguidry - that's a very good point. We've done the non-temporary N replica model with Fuseki before and have the pods fronted by an ALB, but this doesn't really distribute anything--it just gives some horizontal scalability. I don't want to take over

[Wikidata-bugs] [Maniphest] T289760: Evaluate Oxigraph as alternative to Blazegraph

2021-11-19 Thread BenAtOlive
BenAtOlive added a comment. @Tpt - thank you for the detailed response. I've been wondering about this lately, and the tradeoffs you outlined are definitely a strong reason to not do it. Distributed SQL/NoSQL databases have proven to be quite powerful and it is inevitable to think can we

[Wikidata-bugs] [Maniphest] T289760: Evaluate Oxigraph as alternative to Blazegraph

2021-11-19 Thread BenAtOlive
BenAtOlive added a comment. @Tpt - is there a plan to decouple the Sled store and the query handlers in Oxigraph to allow the use case that @Thadguidry was asking about? Under high, concurrent write situations (i.e. if writers to Oxigraph weren't limited to a constrained number that kept

[Wikidata-bugs] [Maniphest] T206560: [Epic] Evaluate alternatives to Blazegraph

2021-11-19 Thread BenAtOlive
BenAtOlive added a comment. Hey all, apologies if this has already been covered elsewhere, but I'm curious why Apache Jena Fuseki is not on the list of Blazegraph alternatives? It seems to meet the We've used Jena from time to time and really like it (it has a lot of features out