Wikipedia's just a big data set to practice on. I've been musing on information graphs (and doing talks about such) since 2004 or so. It also happens that I'v

Wikipedia's just a big data set to practice on. I've been musing on information graphs (and doing talks about such) since 2004 or so. It also happens that I've done a bit of work in writing fast, embedded databases, so when I realized that none of the off-the-shelf graph databases that I found were fast enough for our needs, and that mapping graphs to an SQL database was abysmally slow, I wrote a small one. Honestly, I was surprised when I discovered some graph databases that advertise being an order of magnitude slower. I'd love for our product to be a graph database, but I'm convinced that product takes too long to get to the market. I'd need probably a year of just concentrating on that, without, say, also having to do business stuff just to get that ready for general purpose use. It'd also be cooler for geeking out to, but I don't know if people would actually pay for it. So right now we've got a database that's really fast at: traversing lots of edges and filtering on tags. That's what we need for finding related stuff. As for shortest path stuff ... well, it's never had much more than novelty value for me. I don't see much of a business case for implementing it, and well, we're a business.