Hi all,
I have so far seen BPM as a pure business process tool rather than a data management one even thought BPM provides for managing data. If in case, we have a nice Business Process, which also collects plenty of related business data, what would be the suggestion?
1. To store Business Data in RDBMS and provide BPM with just enough info. for the process.
(or)
2. To store Business Data in BPM Business Catalog & do away with RDBMS (ofcourse BPM uses RDBMS for dehydration )
In our project, we are discussing this and some points in favour of approach (1) are:
i. For web based applications with multiple UI forms to collect data, storing data in RDBMS is way better on performance than accessing/storing in BPM business catalog
ii. Data Retention of Business Data in BPM needs special consideration which may lead to dumping data eventually in RDBMS
iii. UI frameworks help build UIs quick with a known data model rather than over APIs exposed by BPM
iv. Reporting over an RDBMS data model is easier than over a Business Catalog in BPM
Are these points valid or is approach (2) having other advantages to consdier?