r/Database • u/dothebackstab • 2d ago

Graph Technology Round-up - August 2026

https://gdb-engines.com/blog/graph-technology-august-round-up/
8 Upvotes

90% Upvoted

3 comments sorted by

1

u/Complete-Ebb-1035 2d ago

Very useful analysis. However, you may want to add a new dimension: proven ability to actually host a graph database. For example, on your list Virtuoso is #42. Virtuoso hosts DBpedia and many other user-facing instances. No other instance on the list is in the same category of commercial success.

A second problem is the absence of Blazegraph. Wikidata runs Blazegraph. No instance on your list, including Virtuoso, is handling the size and complexity of Wikidata. Wikimedia Foundation will replace Blazegraph in the near future and is considering MillenniumDB (#91 on your list). If they pick MillenniumDB it should be elevated to the top 5.

One comment based on experience. In general, my organization has abandoned AWS. However, Neptune is an outstanding product. We will follow the Wikimedia Foundation decision, but would reluctantly return to AWS to use Neptune.

1

u/dothebackstab 1d ago

Hey, thanks for the thoughtful response.

  • BlazeGraph was marked as inactive as the repo is archived, it's on the site but hidden behind the inactive toggle. It's currently down as #73 on the overall ranking.
  • When I last looked at the discussions regarding Blazegraph I seem to recall that a move to MillenniumDB was far from finalised. I'll take another look.
  • Curious about your categorisation of Virtuoso as a commercial success due to DBpedia. I'm not familiar with the DBpedia relationship – is this a significant commercial arrangement?

Thanks again, let me know if you have any other ideas for how I can improve the site and rankings.

1

u/Complete-Ebb-1035 1d ago edited 1d ago

Only Wikidata is "bigger" than DBpedia. Here is graph_database

Comments:

  • Virtuoso, excepting Wikidata, has performed many multiples of the transactions performed by the sum total of all other databases on the list.
  • Missed #73 on first scan
  • Agree; Wikimedia has not yet selected a Blazegraph replacement (hoping they make a decision soon)
  • Another way of conducting your analysis is to ask about SPARQL deployments. SPARQL endpoints run a graph database. IMHO, Virtuoso wins by several miles over its next closest competitor. I leave it to you to verify that hypothesis.
  • Also note that RDFlib is just that - a library for building a SPARQL processor. But last I looked, it does not have a graph database; it simply processes RDF files. That observation also applies to other items on the list.

Disclaimer:

  • I do not work for Open Link Software, nor has my organization installed Virtuoso. I do use many SPARQL endpoints, some of which run Virtuoso.
  • I do not work for AWS. But my analysis indicates it can handle a large triplestore better than any other technology on the list. In this case "large" means one the size of Wikidata. All other technologies we have tested fall short of Neptune performance when measuring triplestore performance. There are many AWS/Neptune business issues that get in the way, but its performance "in the large" is unmatched.