PieterJanVanAeken

## keybase.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                PieterJanVanAeken
                / keybase.md
            
            
              Created
              May 4, 2016 14:24
            
          
    Keybase proof

I hereby claim:

I am PieterJanVanAeken on github.
I am vanaepi (https://keybase.io/vanaepi) on keybase.
I have a public key whose fingerprint is 6488 5965 196D B9E9 ABA6  157D 1258 FBE0 0ED1 F55E

To claim this, I am signing this object:

  
## gist:6698581
= Why JIRA should use Neo4j

== Introduction

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 https://developer.atlassian.com/download/attachments/4227160/JIRA61_db_schema.pdf?api=v2[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.

== The data set

## gist:6622202
= Enterprise Content Management with Neo4j
:neo4j-version: 2.0.0-RC1
:author: Pieter-Jan Van Aeken
:twitter: @PieterJanVA
:tags: domain:content:enterprise-content-management

== Introduction

There are several challenges in Enterprise Content Management (ECM) that current technologies cannot tackle efficiently. With Neo4j, a whole new world of possibilities opens up. There are few things more "graphy" than ECM, and so the logical next step is the use of graph databases.
	= Why JIRA should use Neo4j

	== Introduction

	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 https://developer.atlassian.com/download/attachments/4227160/JIRA61_db_schema.pdf?api=v2[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.

	== The data set
	= Enterprise Content Management with Neo4j
	:neo4j-version: 2.0.0-RC1
	:author: Pieter-Jan Van Aeken
	:twitter: @PieterJanVA
	:tags: domain:content:enterprise-content-management

	== Introduction

	There are several challenges in Enterprise Content Management (ECM) that current technologies cannot tackle efficiently. With Neo4j, a whole new world of possibilities opens up. There are few things more "graphy" than ECM, and so the logical next step is the use of graph databases.