4 ms·

We've used Blazegraph at work for a project, and we have used a number of other graph databases. Blazegraph is a very niche product and requires a lot of time

We've used Blazegraph at work for a project, and we have used a number of other graph databases. Blazegraph is a very niche product and requires a lot of time for setting it up and adjusting it for your workload. If Blazegraph peaks your interest then you should also look into Yarc platform by Cray. Should you want to look more into graphs, but don't want to spend endless nights just trying to load your data then I would recommend Stardog, which has just been a pleasure to work with.

kendallgclark 11y ago
http://stardog.com/ http://stardog.com/
- vdaniuk 11y ago
  Stardog is great and would be even better with a friendly licensing policy towards indie developers. Their community version is too limited and enterprise version price is per server, contact sales. Current developer version is for testing only. I would happily pay for a developer license or something like that.
  - kendallgclark 11y ago
    We sell Developer licenses to developers, indie or not, all the time. Send email to sales@complexible.com! :)
    - vdaniuk 11y ago
      Great news, I will. I guess that option wasn't obvious for me when I was looking over http://stardog.com/#plans http://stardog.com/#plans
pudo 11y ago
The promises they make are really tempting. However, when I experimented with Blazegraph last year, it ended up stuck more often than I could count, whether during bulk import or in answering some ad-hoc SPARQL queries. I can imagine that with extensive tuning, BlazeGraph provides a good database. Just don't expect it to have the polish and convenience of a modern RDBMS or a shiny NoSQL store :)
- espeed 11y ago
  WikiData selected BlazeGraph to back its new Query Service: https://lists.wikimedia.org/pipermail/wikidata-tech/2015-March/000740.html https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar... Here's a spreadsheet showing WikiData's evaluation of each candidate graph database: https://docs.google.com/spreadsheets/d/1MXikljoSUVP77w7JKf9EXN40OB-ZkMqT8Y5b2NYVKbU/edit#gid=0 https://docs.google.com/spreadsheets/d/1MXikljoSUVP77w7JKf9E...
  - duncanawoods 11y ago
    I just had a look at some of the urls in your profile. http://proof.social/ http://proof.social/ and http://whybase.com/ http://whybase.com/ are down or dead but sounded interesting.
  - nl 11y ago
    Their selection "process"[1] was.. not what I'd choose to use, especially since they changed the priorities as they evaluated. But then they abandoned that process[2] so I wouldn't read too much into the evaluation. Basically as far as I can see, the main reason BlazeGraph was chosen was this: [they] had me out to their office (a house an hour and half from mine)[3] I'm sure BlazeGraph is fine. We were doing a very similar evaluation at the same time, and the Titan situation screwed us over too. But we took a look at BlazeGraph after Wikidata chose it, and found it pretty rudimentary at that time. [1] https://phabricator.wikimedia.org/T90101 https://phabricator.wikimedia.org/T90101 [2] "As you can also see we didn't finish filling them all out. But we've still pretty much settled on BlazeGraph anyway. Let me first explain what BlazeGraph is and then defend our decision to stop spreadsheet work" https://lists.wikimedia.org/pipermail/wikidata-tech/2015-March/000740.html https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar... [3] https://lists.wikimedia.org/pipermail/wikidata-tech/2015-March/000740.html https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar...
- beebs 11y ago
  We've definitely been working on improving the ease of getting started. The number of configuration options is a strength and a challenge. There's now an updated user's guide on the wiki: https://wiki.blazegraph.com/wiki/index.php/Main_Page https://wiki.blazegraph.com/wiki/index.php/Main_Page and additional code samples: https://github.com/blazegraph/blazegraph-samples/ https://github.com/blazegraph/blazegraph-samples/
leeoniya 11y ago
s/peaks/piques

kendallgclark 11y ago

http://stardog.com/ http://stardog.com/

vdaniuk 11y ago
Stardog is great and would be even better with a friendly licensing policy towards indie developers. Their community version is too limited and enterprise version price is per server, contact sales. Current developer version is for testing only. I would happily pay for a developer license or something like that.
- kendallgclark 11y ago
  We sell Developer licenses to developers, indie or not, all the time. Send email to sales@complexible.com! :)
  - vdaniuk 11y ago
    Great news, I will. I guess that option wasn't obvious for me when I was looking over http://stardog.com/#plans http://stardog.com/#plans

pudo 11y ago

The promises they make are really tempting. However, when I experimented with Blazegraph last year, it ended up stuck more often than I could count, whether during bulk import or in answering some ad-hoc SPARQL queries. I can imagine that with extensive tuning, BlazeGraph provides a good database. Just don't expect it to have the polish and convenience of a modern RDBMS or a shiny NoSQL store :)

espeed 11y ago
WikiData selected BlazeGraph to back its new Query Service: https://lists.wikimedia.org/pipermail/wikidata-tech/2015-March/000740.html https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar... Here's a spreadsheet showing WikiData's evaluation of each candidate graph database: https://docs.google.com/spreadsheets/d/1MXikljoSUVP77w7JKf9EXN40OB-ZkMqT8Y5b2NYVKbU/edit#gid=0 https://docs.google.com/spreadsheets/d/1MXikljoSUVP77w7JKf9E...
- duncanawoods 11y ago
  I just had a look at some of the urls in your profile. http://proof.social/ http://proof.social/ and http://whybase.com/ http://whybase.com/ are down or dead but sounded interesting.
- nl 11y ago
  Their selection "process"[1] was.. not what I'd choose to use, especially since they changed the priorities as they evaluated. But then they abandoned that process[2] so I wouldn't read too much into the evaluation. Basically as far as I can see, the main reason BlazeGraph was chosen was this: [they] had me out to their office (a house an hour and half from mine)[3] I'm sure BlazeGraph is fine. We were doing a very similar evaluation at the same time, and the Titan situation screwed us over too. But we took a look at BlazeGraph after Wikidata chose it, and found it pretty rudimentary at that time. [1] https://phabricator.wikimedia.org/T90101 https://phabricator.wikimedia.org/T90101 [2] "As you can also see we didn't finish filling them all out. But we've still pretty much settled on BlazeGraph anyway. Let me first explain what BlazeGraph is and then defend our decision to stop spreadsheet work" https://lists.wikimedia.org/pipermail/wikidata-tech/2015-March/000740.html https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar... [3] https://lists.wikimedia.org/pipermail/wikidata-tech/2015-March/000740.html https://lists.wikimedia.org/pipermail/wikidata-tech/2015-Mar...
beebs 11y ago
We've definitely been working on improving the ease of getting started. The number of configuration options is a strength and a challenge. There's now an updated user's guide on the wiki: https://wiki.blazegraph.com/wiki/index.php/Main_Page https://wiki.blazegraph.com/wiki/index.php/Main_Page and additional code samples: https://github.com/blazegraph/blazegraph-samples/ https://github.com/blazegraph/blazegraph-samples/

leeoniya 11y ago

s/peaks/piques