You may wish to consider a 3-tier architecture - thin client, Tomcat for
the application layer and Fuseki for the database layer (which can be
another tomcat or even the same one but if it's a separate process or
server, using the integrated Jetty server is less work).
Andy
On
On 02/05/13 13:57, Andy Seaborne wrote:
You may wish to consider a 3-tier architecture - thin client, Tomcat for
the application layer and Fuseki for the database layer (which can be
another tomcat or even the same one but if it's a separate process or
server, using the integrated Jetty server
I would like to ask for your opinion guys...
I am building a prototype client-server architecture using the semantic
web. I have decided to make a thick server (Server does all the semantic
related stuff using Jena (querying, instantiating, storing)) and a very
thin Android mobile client (client
My experience is with medical research on large distributed SPARQL servers
queried from a single server. Our server rewrote queries which it sent to
endpoints and then recombined to present solutions to the clients. In this
configuration we were dealing with fairly large data sets. In the end
