Why JIRA should use Neo4j by Pieter-Jan Van Aeken.
From the post:
There are few developers in the world that have never used an issue tracker. But there are even fewer developers who have ever used an issue tracker which uses a graph database. This is a shame because issue tracking really maps much better onto a graph database, than it does onto a relational database. Proof of that is the JIRA database schema.
Now obviously, the example below does not have all of the features that a tool like JIRA provides. But it is only a proof of concept, you could map every feature of JIRA into a Neo4J database. What I’ve done below, is take out some of the core functionalities and implement those.
This caught my eye because I have been in discussions about an upgrade from an older version of JIRA to the latest and greatest.
It’s not every feature but enough to convey the flavor of a possible graph mapping.
Given the openness of a graph model, does this suggest a model for mocking up topic map models?
I first saw this in a tweet by Peter Neubauer.
[…] Another Word For It Patrick Durusau on Topic Maps and Semantic Diversity « Why JIRA should use Neo4j […]
Pingback by GraphGist Wiki « Another Word For It — September 25, 2013 @ 6:18 pm