Would neo4j be good for this hierarchical database?


I have this kind of hierarchical structure that could theoretically go on endlessly. "Tasks" move between "backlog", "ready" and done frequently, and it is going to be possible to customize the "backlog, ready, done" structure for your own board. Would neo4j be the right choice for this type of thing? Or should I just go with PostgreSQL or something?

HI,

This is something where graph database fits perfect. You could use a Label for Backlog, Ready, Done
e.g.
(:Task:Backlog)
(:Task:Ready)
(:Task:Done)

So when you move a Task from Backlog to Ready you just change the Label on the Node

And You can create a relationship between Task nodes for example:
(:Task)-[:HAS_SUB_TASK]->(:Task)

just a simple starter,

regards

Wow, thank you! Seems very neat. I have been playing around with it a bit in the playground.. This opens so many new doors!