Ease of installation/use is the most important factor here – not performance.
Small is OK as large datasets are not expected.
Ease of installation/use is the most important factor here – not performance. Small is
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Ease of installation/use is the most important factor here – not performance.
Small is OK as large datasets are not expected.
I’d also recommend sesame, its lightweight, pretty easy to install, and provides good performance for small datasets. Query performance is far better with Sesame 1.2.x than Sesame 2.x because of the addition of context support to the 2.x series.
I’ve tested sesame installation/deployment with tomcat, resin, and jetty, and it worked easily with all of them. I don’t recommend the bindings to RDBMS components such as Postgres or MySQL, at least in the 1.x series, performance was not acceptable, even for prototype applications. The in-memory and native implementations provide good query performance and offer simple persistence, though they lack true transactions.
Jena has a decent API, and a lot more support for databases, reasoners, etc, but has a larger footprint, and is a little more cumbersome to use on the whole.