Re: [rules-users] Single Session versus Multiple Sessions
On 23/11/2010, at 6:37 PM, Wolfgang Laun wrote:
Is the processing of individual Incidents independent from each other
except that, perhaps, Persons may reoccur in different Incidents, without this having any
influence on the processing?
Yes.
If so, each Incident could be handled in a session of its own, which
(since the number of objects around a single Incident is relatively small) could be
restarted upon the arrival of new data, fire all rules and go back to the data base.
(Similar operations will have to be there anyway, because you'll need this for system
restarts. This does not sound like an application where you need 24/7.)
It does need to be available 24/7 but the timing is not critical. As I said I am new to
Drools. I'm not familiar with stoping/saving/restarting sessions. I'll have a bit
of a read about that. I need to get an understanding of the persistence and transactional
stuff as well.
We have an event bus in the system and as new documents arrive in the system and event is
published with the details and I was planning on using an event pipeline to feed these
into the session(s) as facts (converted from the incoming event data). Not sure how this
would work with stopping/restarting sessions.
The workflow described is not the only one we need to implement, just the first off the
rank. I am hoping to have a rules/flow framework flexible enough to cope with other
workflows that we want to introduce over time so I really want the interface to the event
bus and to the existing domain model (to introduce initial facts) to be flexible. Early
days yet, I have a lot to learn.
thanks.
Brian Wallis
InfoMedix | Architect
p: 3 8615 4553 | f: 3 8615 4501
e: brian.wallis(a)infomedix.com.au
Level 5, 451 Little Bourke Street, Melbourne VIC 3000