Hello,
I would like to know if you are interested by the proposal I made at:
https://meta.wikimedia.org/wiki/Grants:Project/WDQS_On_FoundationDB
Like I said previously on wikidata mailing list, I can address the following problems related to WDQS:
In an ideal world, WDQS should:
* scale in terms of data size * scale in terms of number of edits * have low update latency * expose a SPARQL endpoint for queries * allow anyone to run any queries on the public WDQS endpoint * provide great query performance * provide a high level of availability
ref: https://lists.wikimedia.org/pipermail/wikidata/2019-June/013124.html
The other proposal I made is about replacing both wikibase and blazegraph:
https://meta.wikimedia.org/wiki/Grants:Project/Iamamz3/Prototype_A_Scalable_...
nomunofu is a working prototype I made to micro benchmark (again) GNU Guile:
https://github.com/amirouche/nomunofu
What do you think?
Hello all,
I would like to know what you think of the proposal I made at:
https://meta.wikimedia.org/wiki/Grants:Project/Future-proof_WDQS
Like I said previously on wikidata mailing list, I can address the following problems related to WDQS:
In an ideal world, WDQS should:
- scale in terms of data size
- scale in terms of number of edits
- have low update latency
- expose a SPARQL endpoint for queries
- allow anyone to run any queries on the public WDQS endpoint
- provide great query performance
- provide a high level of availability
ref: https://lists.wikimedia.org/pipermail/wikidata/2019-June/013124.html
The other proposal I made is about replacing both wikibase and blazegraph:
https://meta.wikimedia.org/wiki/Grants:Project/Iamamz3/Prototype_A_Scalable_...
What do you think?
wikidata-tech@lists.wikimedia.org