Evaluate using LinkedDataFragments/Server.js instead of custom blazegraph integration
Open, MediumPublic
Actions

Assigned To

None

Authored By

	dcausse
	Jul 2 2020, 8:36 AM

Description

The way we provide the LDF service is not scalable (T161240) and overtime our fork of LinkedDataFragments/Server.Java has diverged from upstream.

LinkedDataFragments/Server.js seems more active than LinkedDataFragments/Server.Java and seems to provide an external layer that can work on top of a sparql service. This could hopefully fix our scalability issue and address the tech debt of having to maintain our own fork of LinkedDataFragments/Server.Java.

The WMCS machine ldf-test.wmflabs has been created for this purpose.

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open		None	T161240 Expose wikidata query service LDF endpoint in a scalable and available way
		Open		None	T256948 Evaluate using LinkedDataFragments/Server.js instead of custom blazegraph integration