Who Uses This Software?
GraphDB is the preferred semantic graph database for Media Companies, Publishers, Museums, Science, Healthcare and Biotech Researches, Insurance, Business and Risk Intelligence, Marketing Services.
Average Ratings15 reviews
- Overall 4.5 / 5
- Ease of Use 4.5 / 5
- Customer Service 4.5 / 5
- Features 4.5 / 5
- Value for Money 4.5 / 5
- Free Version Yes
- Free Trial Yes
Installed - Mac
Cloud, SaaS, Web
Installed - Windows
- Founded 2008
About Graph DB
Graph DB is a semantic graph database that serves organizations to store, organize and manage content in the form of semantically enriched smart data. Graph DB includes Data integration and interlinking, W3C standards compliance, expressive, rich and flexible data model, single interconnected information space formed by structured data and text documents, reasoning, linked open data Compatibility and data provenance.
Graph DB Most Helpful Reviews
Reviewed on 09/03/2018
GraphDB Enterprise is a high-performance semantic repository created by Ontotext. It is implemented.
Graph database seem to be tailor-mode for networking applications.
1. The prototypical example is a social network,where nodes represent users who have various kinds of relationships to each other.Modeling this kind of data using any of the other styles is offten a tough fit,but a graph database would accept it with relish.
2.They are also perfect matches for a object-oriented system.
3.The Model in a graph database is easier to change than in a relation database.
if the type of relationship in an RDBMS changes e.g from 1:N to M:N I need to use DDL to change the model, which may require downtime. I don't have this problem in a graph database where changing the relationships/edges between vertices is much easier.
1. Graph Database not much connectors.
2. Because of the high degree of interconnectedness between nodes,graph database are generall not suitable for network patitioning.
3. Graph databases don't scale out well.
4. Graph database are poor at aggregating data,Don't use it for Business Intelligence.
5. It is difficult to implement versioning/auditing of data in a graph database. while not impossible it is rather awkward though.
by Ontotext on 13/03/2018
thank you for your time reviewing GraphDB on Capterra. I was a bit confused whether you are reviewing GraphDB in particular or Graph Databases as a whole. Could you be more specific, and in the context of graphDB, please?
Witch version of Graph DB are you using?
Reviewed on 07/03/2018
Amazing i will say. Easy to use and interpret the requirements to real.
Pros: Simplicty i liked unlike SQL Databases where relationship becomes so complex and then you Normalize. Being Simple, we can easily handle objects in very easy way.
Cons: The UI should be better like MS Mangement Studio. Also the server services etc should be part of the software rather starting it manually.
Reviewed on 13/03/2018
Review of the free version, its great! Easy and simple to install and use
Comments: Easy setup and install of local graphDB by loading .ttl files. Hdt support would be appreiciated
Pros: The interface is intuitive and it is easy to use tables returned form graph queries to further browse and explore
Visualization of the graph does not work, at least not with the settings I tried (no inference)
If graph visualization would be perfect (e.g. see the RDF2Graph) and vizualization could be used to add paterns to the query, I would definetely give GraphDB 5 stars, it would be awesome
Reviewed on 06/03/2018
This is an excellent platform to get started in graph databases and knowledge representation.
Comments: I learned a tremendous amount about data structures / formats, and through iterative work, I learned more about how to structure an ontology. (Note: Accounting is not my industry, even though this survey suggests I'm in accounting)
1) The ease of import/export.
2) The visualizations, overall platform direction, and ease of updates.
3) Class hierarchies and visual graph.
4) SPARQL Query & Update (Editor and Results) feature.
1) Tutorials. These could be greatly improved.
2) Import fails are difficult to clear?
3) Interdisciplinary users have difficulty interpreting impact of "repository setup" selections.
4) Broad description specific to each feature / utility and how it can be utilized. For example, this is a Graph Database tool, but can any aspect be specifically used for ontologies. If yes, which one and to what specificity?
Reviewed on 06/03/2018
Memory Efficient and easy to understand
Pros: I like its toolkit which provide almost all the feature that you may need while solving any problem. I have used GraphDB for my University assignment , it didn't take much time for me as it is easy to understand and work like plug and play.
Cons: I like graphDB and i didn't find disadvantage of using it but of course it take lots of time to download and bit slow (sometime) when i used 4 GB ram with intel i3 processor.