jstastny-cz opened a new issue, #2307:
URL: https://github.com/apache/incubator-kie-issues/issues/2307

   In compact architecture setup, when multiple apps share the same relational 
database, various endpoints return data not belonging to particular service 
instance, but rather a superset of data coming from all the apps connected to 
the particular database instance.
   
   To be able to isolate runtime data coming from database based on sense of 
"locality", existing process definition identifiers can be used without the 
need to bring in any notion of deployment topology information into the 
database schema. Such identifier should be process id and version composed key 
- but at given moment, throughout the engine and also DB schema, the uniqueness 
is judged based on process id itself.
   
   To bear such simplification in mind, but also to allow for possible future 
refactoring, the persistence modules for all relevant components should 
implement filtering support. For the time being based on a single column, 
possibly extensible to multiple columns.
   
   The relevant components:
   * runtime persistence addon
   * jbpm usertasks jpa addon
   * Embedded data-index
   * Embedded jobs addon
   * Embedded data-audit
   
   Goals:
   * Make sure all data loading operations apply filtering based on the 
"locality" of queried items.
   * Keep schema changes minimal, no artificial deployment topology information 
added, rely on existing values where possible. Possible schema denormalization 
to facilitate filtering (e.g. extract value from stored JSON column into newly 
added string column).
   * Account for possible future change in filters from single value (id) to 
multiple (e.g. id + version).
   
   Non goals:
   * Any changes to components outside of the compact architecture setup.
   * Any changes to storage options other than relational databases.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to