Hi!
> For infection control, we must be able to review large volumes of data,
> conceivably millions of records stored in a database. Also the number
> of rules will be quite large (The system will auto generate many
> rules). Do you know of any projects that have used it on this scale?
> (How do you deal with not having all the records in memory at a time?)
I am using Jess in the context of Enterprise Integration where it is used
for the backend integration of legacy systems that can have equally large
databases. Rules in my system are also automatically generated. So are the
facts corresponding to database events, such as insertion, update or
deletion of records in database tables.
Whenever "state" information is needed backward chaining-enabled facts are
used on the rules' LHS. During backward chaining my system automatically
queries the database and asserts facts for the tuples returned in the
result set. In my specific context "used" LHS facts can be retracted by the
rule RHS. Thus, at all times, the number of asserted facts is actually very
low.
Sincerely,
Thomas Barnekow
________________________________
Dipl.-Inform. Thomas Barnekow
Fraunhofer IAO, Competence Center Software Technology
mail: Nobelstra�e 12, D-70569 Stuttgart,
Germany
phone: +49 (0) 711 / 970 - 2346
fax: +49 (0) 711 / 970 - 2300
email: [EMAIL PROTECTED]
web: http://www.swt.iao.fhg.de
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list (use your own address!) List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
