Reputation: 164
I am currently building a website which sends SPARQL queries to get information from DBpedia (mostly name of cities which can then be displayed on a map, and further information about this places like number of inhabitants, prominent persons etc).
I would like your opinion about the general use of SPARQL queries and DBpedia:
The second option is much easier for me to implement because and I don't need to worry about the extra database, but if everybody does the same it may surcharge the DBpedia servers?
Upvotes: 1
Views: 136
Reputation: 9434
The public DBpedia endpoint which is made available at no cost to the Web community at large may not be suited to such use as you describe -- being the backend to what seems likely to be a freemium service of some kind.
You can instantiate your own mirror of the DBpedia service on AWS or elsewhere, if you need a more consistently available instance.
Upvotes: 2
Reputation: 4001
DBPedia is frequently down or unresponsive for the reasons you cite - there can be unanticipated periods of high volume on the servers. So the first choice, caching to a local data store, is probably best.
Upvotes: 2