Smalyshev added a comment.

> Primarily it's that we can't cache them in Varnish like we should be able to

Caching SPARQL results via Varnish is not a good idea in most cases. For two 
reasons:

1. Usually the same query is not repeated very often (unless somebody has a 
buggy script, etc.). Every client would run its own query and once the result 
is returned, it will go away and another client would use another query.
2. When the query **is** repeated, it is usually because the client expects 
something to change - like getting update from Wikidata. Since we do not have 
any real way to invalidate Varnish when underlying data changes, caching here 
would only hinder the clients.

Also, these results can be pretty big - so we'd be storing tons of information 
which is not useful. Of course, there are exceptions and some scenarios would 
still benefit from caching, but most would not.

> but as mentioned before it's going to affect how multi-DC request routing 
> works as well,

There are no plans of multi-DC setup for WDQS, as far as I know.

> AFAICS there is no general solution to this problem.

We do not need a general solution for the whole HTTP world. We need a 
particular solution for specific practical issue, and we have everything we 
need to actually solve it - except willingness to solve it.

> But still, trying to stick to standards here isn't just a matter of theory 
> trumping user requests.

I think in this particular case it is exactly that, as all objections so far, 
when applied to what happens with WDQS, appear to be only theoretical.

All proposed solutions require creating a whole new middleware layer, and I 
don't think anybody is ready to allocate resources to develop and maintain this 
layer.

> If there's a problem with client tooling, we can submit patches to those 
> client projects

Not all of those are open source projects, and they would not spend resources 
on rewriting their tools just because one particular endpoint (ours) does not 
support POST. Also, who exactly would be spending time on learning these tools, 
developing and submitting those patches?


TASK DETAIL
  https://phabricator.wikimedia.org/T112151

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Smalyshev
Cc: chasemp, JanZerebecki, BBlack, Andrew, Deskana, Joe, gerritbot, nichtich, 
Jneubert, Karima, Aklapper, Smalyshev, jkroll, Wikidata-bugs, Jdouglas, aude, 
Manybubbles, Mbch331



_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to