




GraphDB data repository





Supported Operating System(s):
Windows 7, Windows Vista, Windows XP, Mac OS, Linux, Windows 8, Windows 10About GraphDB
GraphDB is a database management solution that helps businesses in finance, publishing, healthcare and other industries create knowledge graphs and streamline data indexing operations. The built-in NoSQL database system allows IT teams to manage storage and retrieval of data from relational databases.
The platform enables employees to parse structured data in JSON, XML, CSV, XLS and other formats and perform semantic searches in real-time. Features of GraphDB include data storage management, reporting, semantic tagging, data visualization and more. Additionally, it lets IT professionals generate and store the resource description framework (RDF) data in a centralized repository.
GraphDB facilitates integration with a document-based database system, Mo...
GraphDB data repository
Supported Operating System(s):
Windows 7, Windows Vista, Windows XP, Mac OS, Linux, Windows 8, Windows 10Average User Ratings
Overall
Ease-of-use
4.5
Value for money
4.5
Customer support
4.5
Functionality
4.5
Likelihood to Recommend
Not likely
Very likely
March 2018
Peter from Morris Catholic H.S.
Company Size: 51-200 employees
Industry: Education Management
Time Used: Less than 12 months
Review Source: Capterra
Ease-of-use
4.0
Value for money
3.0
Customer support
5.0
Functionality
5.0
March 2018
Very easy to use. Great support.
Ease of use.
Pros
Very easy to use when trying to parse through qualitative data for my dissertation. Needed to code data from multiple reflections and interviews.
Cons
was very easy to use.. took a little while to get up to speed, but once I did, I found it very intuitive and easy to use.
October 2019
Mark from University of Pennsylvania
Company Size: 10,000+ employees
Industry: Research
Time Used: More than 2 years
Review Source: Capterra
Ease-of-use
5.0
Value for money
5.0
Customer support
5.0
Functionality
4.0
October 2019
Nearly instantaneous, rich-featured semantic repository
There are other triple stores with different feature sets, but it don't think there's any triplestore that is better than GraphDB.
Pros
It's very quick and easy to deploy GraphDB, ingest some RDF data, build queries in a IDE-like environment, and visualize relationships. A semantic similarity search tool is provided.
Cons
The OntoRefine tool is great for converting tabular data files into semantic triples, but there's no support for reading from relational databases. There are nice free text indexing & search tools, but no natural language parser for discovering entities and relationships. There are several pre-configured reasoning levels plus support for writing one's own rules, but no support for SWRL. Like most triplesotres, OWL2 reasoning over complex axioms and millions of data triples isn't fun/fast/realistic? (I say that based on a single node, two threads, and 256 GB RAM.)
Reasons for Choosing GraphDB
Great SPARQL query building environment. Built in visualizations. Fully functional 2-core version and reasonable academic prices.
Reasons for Switching to GraphDB
Easier to deploy and configure. Better SPARQL query building environment. Built in visualizations. GUI for importing tabular data.
Response from Ontotext
Replied November 2019
Thank you for your feedback, dear Mark! We will address all the recommendations you have left to the production team. Be well
November 2019
Alexander from TU Braunschweig
Company Size: 1,001-5,000 employees
Industry: Research
Time Used: Less than 12 months
Review Source: Capterra
Ease-of-use
4.0
Functionality
3.0
November 2019
review of graphdb in the production planning
We are currently using graphdb in a PoC as semantic web stack compliant database for data integration in a laboratory environment.
Pros
- ease of use (compared to other semantic web stack solutions) - degree of inferencing implementation - solution for transforming relational data into RDF with OpenRefine integration - query performance (for SELECT, a evaluation for INSERT queries could not be given due to use of free version) - good support even at free version
Cons
- versioning of data (see changes over time) - better controllability of role and rights (give rights for specific graphs in repository) - no IdP based authentiaction like OpenID Connect (or something based on oAuth2 or at least SAML) - easy to use integration for object storage (like AWS S3) - documentation could be more detailed in some places
Reasons for Choosing GraphDB
- extensive free version - ease of use (frist time usage of an rdf triplestore / graph database) - visualization - beginner-friendly documentation
Response from Ontotext
Replied November 2019
Thank you for your feedback!
November 2019
Joop from Cultural Heritage Agency of the Netherlands
Company Size: 201-500 employees
Industry: Government Administration
Time Used: Less than 2 years
Review Source: Capterra
Ease-of-use
5.0
Value for money
5.0
Functionality
4.0
November 2019
GraphDB
We use GraphDB together with PoolParty as part of the Semantic Integrator solution. We use GraphDB as our test triple store. We use GraphDB to publish our "small" linked open data sets.
Pros
I can be very short about my (our) experiences so far with GraphDB. GraphDB is a clear winner for our usecases now. The learning curve is not steep, almost self-explanatory. It’s fast and it fits our needs; for now. We loved the graphics of GraphDB.
Cons
OntoRefine. It looks fine but we missed some modeling features. We switched back to OpenRefine.
Reasons for Choosing GraphDB
Stardog is very good, but some things, like sharing the databases, adding data were not so straight forward. Stardog had problems with gzip files or any other files than trig.
Reasons for Switching to GraphDB
Virtuoso was too big and too complicated for our use.
Response from Ontotext
Replied November 2019
Thank you for your feedback, Joop. Be well!
October 2019
Adonay Andres from Geckode.mx
Company Size: 2-10 employees
Industry: Information Technology and Services
Time Used: More than 2 years
Review Source: Capterra
Ease-of-use
5.0
Value for money
5.0
Customer support
5.0
Functionality
5.0
October 2019
The best Ontological Database Engine
We've had a really good time working with it. Once we have a good model definition (which applies for any graph engine) it simply works and works really well.
Pros
Over the last years, GraphDB has improved a lot, speaking about performance and inference. Graph DBs have always had the problem of being too slow for solving queries, we always had to structure them in a way that it was optimal for the engine to solve them. Graph DB has been always the most performant one. Another feature that I loved from it is that, in order to install it, you simply copy a single jar file and you're almost ready to go. The user interface helps a lot. And its compliance with several standards for the interchange formats makes the way pretty straight forward no matter what tool was used to generate an interchange file.
Cons
The con I find with the product is about updates. When a new version comes up (which sometimes I don't know about the fact that there's a new release), I need to manually download it and deploy it. Also it would be desirable if we had access to connectors for different platforms. We work a lot with node.js and there's almost no libraries to use it with graphDB that are backed by ontotext.
Reasons for Choosing GraphDB
Not specifically switched from another product. About 8 or 9 years ago, we tested several engines. It turned out that graphDB had the best performance and it was really easy to deploy. So, we decided to stay with it.
Response from Ontotext
Replied November 2019
Dear Adonay, thank you for your great feedback! It is always great to see some extended prons and cons of the product you create! Regarding the cons: If you are part of the GraphDB Update announcements list you should receive a note about every update of GraphDB, so you won't be missing anything new. About the connectors: Latest releases of GraphDB support connectors and plugins to MongoDB Lucene, SOLR, Elasticsearch. If you need connectors to other popular services, you should make a request to the GraphDB Production team. Best Regards