Hi Paolo, thanks for the quick response! The reason for doing this is, because I think it would be useful to have a RDF-Database with SPARQL-Interface which can be used as a PAAS offering like Amazon RDS or Amazon Dynamo DB: For the developer this would mean no hassle about replication, or scaling etc. To some extend you can achieve that when using Jena SDB on top of something like Amazon RDS or MS SQL Azure. I want to try how far I can get when I use Jena as API and map it to something like Dynamo DB or MS Azure Tables which have quite unique Scalability/Availability characteristics. There is for example http://datomic.com/ which also goes along those lines. They implemented it on top of Dynamo DB but with a custom query language.
Does that make sense from your perspective? On Tue, Apr 24, 2012 at 3:32 PM, Paolo Castagna <castagna.li...@googlemail.com> wrote: > Hi Tobias, > I do not have general and useful hints other that looking at the SDB source > code > if you are planning to develop a custom "backend" or a relational database or > on > a storage system which offers you an SQL-like query language and look at the > TDB > source code if you are planning to experiment with your own indexes on disk. > > I have a question for you, what's the reason why are you thinking to develop a > custom "Backend" for Jena? > > Thanks, > Paolo > > Tobias Neef wrote: >> Hi, >> >> I am currently thinking about developing a custom "Backend" for Jena >> just like the relational one and the native TDB. It would be great if >> you could give me some general hints how the process of developing >> such a backend would look like. >> >> Best regards, >> Tobias Neef >
