A more scalable solution may be this: load all transactions from site A, start the rule
engine in a separate thread using fireUntilHalt, then start inserting the transactions
from site B. The rules should retract transactions that match up. (This way ony roughly
half of the transactions are in memory at any given time and you can scale twice as
large.) Once all B transactions have been inserted, what you have left are all
trasnactions that haven't been able to match. You can save them off and reload them
if you want to attempt matching them in the next round of processing.
--- On Wed, 4/15/09, Learning BRMS <rulerhawk(a)gmail.com> wrote:
From: Learning BRMS <rulerhawk(a)gmail.com>
Subject: Re: [rules-users] is this kind of App right for DROOLS?
To: "Rules Users List" <rules-users(a)lists.jboss.org>
Date: Wednesday, April 15, 2009, 4:34 PM
Uaw.. very nice example, Greg... Thanks
I really like these Drools solution.
I will try your example with some more heavy class (with 40
and expand the volume to 2.6 mi objects coming from a
I'll let you know.... I think I will enjoy those tests
On Tue, 2009-04-14 at 23:01 -0700, Greg Barton wrote:
> Yes, drools can handle this, and can handle the
volume. You may want to consider sequential mode execution,
though. See attached code for some simple matching rules.
In the example there's a 5% chance a transaction with a
given id will not be present. You could mock this up
further to have rules to handle matching in the case a
simple match isn't possible.
> --- On Tue, 4/14/09, Learning BRMS
> > From: Learning BRMS <rulerhawk(a)gmail.com>
> > Subject: [rules-users] is this kind of App right
> > To: rules-users(a)lists.jboss.org
> > Date: Tuesday, April 14, 2009, 10:43 PM
> > Hi people...
> > I need to solve a problem on my work and I would
> > you if Drools
> > could help us...
> > I have two kinds of "connected by
> > systems that register our
> > products selling transactions.
> > We need to match dayly every selling transaction
> > both systems
> > and to track any difference for every store.
> > An transaction could happens on system A and not
> > B and
> > vice-versa and on different dates or times
> > problems could
> > delay the synchronizing).
> > The transaction mostly have the same ID, but
> > manual
> > transactions too with no id only date and
> > For each situation I have to fire a different
> > resolution (today
> > we have humanhand resolution).
> > We should have an 1 million of transactions by
> > process...
> > Today we are using a sql script to do reports
that will be
> > humanly
> > analyzed...
> > I want to change this picture as soon as
> > Could Drools help us with this kind of analyze,
> > this volume
> > of objects?
> > How many objects could we have on working memory
> > time for that
> > match?
> > Thanks a lot for any comments
> > Kris
> > _______________________________________________
> > rules-users mailing list
> > rules-users(a)lists.jboss.org
rules-users mailing list rules-users(a)lists.jboss.org
rules-users mailing list