Hello, I wanted to clarify few points related to separate service end point for the SPARQL Query Caching feature. I was considering to take up either of the below approach to implement the cache service end point. I am open for both the approach and wanted to discuss further.
Option 1 : create a separate micro service that can be deployed in tomcat or run using jetty server for cache service like external cache service and cache the Sparql query result. The SPARQL_UberServlet can checks the external service if cache data is available then serve the cache data otherwise send the query to SPARQL_Query and copy the data and populate the cache in the separate micro service. Option 2 : Create a separate servlet like Sparql_Cache that run as part of fuseki server and we send all sparql query to Sparql_Cache servlet which checks if the cache data is available then serve or contact Sparql_Query to get latest data and respond. Please let me know your feedback. Regards Saikat On Wed, Feb 11, 2015 at 4:06 PM, Rob Vesse (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/JENA-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Rob Vesse updated JENA-626: > --------------------------- > Labels: java linked_data rdf sparql (was: gsoc java linked_data rdf > sparql) > > > SPARQL Query Caching > > -------------------- > > > > Key: JENA-626 > > URL: https://issues.apache.org/jira/browse/JENA-626 > > Project: Apache Jena > > Issue Type: Improvement > > Reporter: Andy Seaborne > > Labels: java, linked_data, rdf, sparql > > > > Add a caching layer to Fuseki to cache the results of SPARQL Query > requests. This cache should allow for in-memory and disk-based caching, > configuration and cache management, and coordination with data modification. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
