Re: [rules-users] A few general questions on scaling StatefulKnowledgeSessions

Actually, I do mean that! :D But maybe I should explain… To be more precise, most of the time in my apps is taken in marshalling facts and inserting them into the session. From firing rules, it tends to take 10s of microseconds for a decision to be made. Obviously if the RHS is doing more than just making a decision based on facts already in the system (i.e. the RHS code queries databases, etc) then firing can get very slow. However, I tend to follow the best practices that I learned from various FICO (!) consultants, who recommended against doing anything heavy in the RHS, but rather getting back out of the rules engine ASAP and doing those heavy tasks in the invoking application. This approach works nicely, because the rules engine does what it's good at (making decisions based on facts that are in working memory) and my Java (Spring) app does what it's good at (getting data and integrating with other systems). The added benefit is that if I need to synchronise access to the session, it's not such an issue if each request is back out of the rules engine in microseconds. Steve On 17 Aug 2012, at 13:01, Wolfgang Laun <wolfgang.laun(a)gmail.com&gt; wrote: