AnsweredAssumed Answered

Runtime persistence in graph database

Question asked by michal.warecki on Nov 28, 2011
I'm wondering about usage of graph database (like neo4j) as a runtime process persistence. Process written in BPMN is a 100% graph so it is natural to persist it in graph database.
When IT project evolves in time there are many changes/improvements/bugs fixes etc. in business processes so upgrade (minor and major) is a must. Using graph database upgrade is very easy becouse of flexible structure (we are not attached to relational db schema). There is possibility to save old processes and create new with changes or insert/remove BPMN elements to existing processes.

What do you think about that? What are the pros and cons?