Replies: 5 comments 5 replies
-
|
Where would the data be stored? |
Beta Was this translation helpful? Give feedback.
-
|
Probably an option of either in-memory or indexeddb |
Beta Was this translation helpful? Give feedback.
-
|
This is definitely something that we should have at some point in the future but it does not have very high priority for the moment. As usual this changes if someone pays for it. Meanwhile I recommend using Oxigraph in WASM, that's what we do as well. |
Beta Was this translation helpful? Give feedback.
-
|
No worries, yeah, I'm using Oxigraph WASM now. Blazegraph is our go to server-side triple store, but I'm always keeping tabs on the landscape as we will eventually need to move away from it (abandonware). As such, I'm working on a project that can switch out "backends" on the client (currently N3.js, Quadstore, and Oxigraph). I also have a server-side version with backends I can switch too. Anyway, I'm sure you know each triple store has slight differences in SPARQL processing, scalability, etc and something like this would allow test driving different techs pretty easily. |
Beta Was this translation helpful? Give feedback.
-
|
@bherr2 I am curious why Blazegraph is still your "go to triple store on the server side". It is not longer maintained and the performance is ... well: https://qlever.dev/evaluation |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Has there been any exploration of compiling qlever to WASM for running queries on browsers client-side?
Beta Was this translation helpful? Give feedback.
All reactions