[dotNetRDF-Support] Best practices for multiple writers

[Edwin T. <Ed...@la...>]

After diving into dotNetRdf over the last week I've made some good progress and have a sample application working pretty much the way I'll need our real application to work.  Now I'm looking into how to best handle multiple readers and writers of the underlying store.  Our goal is to use a triple store to hold our configuration data (with semantics) and to have N applications (or instances of a single application) share that store.  Most of the data access will be reading (for public facing apps) and then the admin apps will be writing to the store.  I started out using the LoadGraph method of the IStorageProvider since it has such handy wrappers around triple handling and lists but after some testing it appears that these load the entire graph into memory and thus the apps would overwrite each other any time I did a SaveGraph.  I then starting looking into IQueryableStorage.Query and IStorageProvider.UpdateGraph but I believe that means I would have to handle any lists on my own as opposed to using the helpers provided by the Graph object.  I'm not opposed to having to handle lists on my own but if I can take advantage of the dotNetRdf implementation I'd rather do that since it is proven.

I looked around on the wiki and couldn't find anything that offered some advice/guidance into how best accomplish this so I was wondering if anyone on the list could provide some?

I'm currently using Virtuoso Open Source for my testing but we haven't decided on what store we will actually use in our production environment.  We will however be sticking with one of the ones that dotNetRdf supports natively.  If another provider supports our use-case more effectively than the others I'd appreciate that insight as well.

Thanks for your time,

Ed Toro