Not as a realtime working memory. And don't even think about persisting these things to a database if you're trying to process high volumes of events with minimal latency. I'm assuming that you're trying to process high volumes of events, and you're experiencing performance problems, because otherwise you wouldn't be asking about how to break your application up across multiple servers, right?
I'm pretty sure you're going down the wrong track, trying to think of a way in which you could achieve a single working memory across multiple servers. Start thinking about how to use message queues to do this. Design multiple CEP nodes publishing events to queues and other nodes listening for those events. That's a model that is well proven in thousands of CEP implementations. Steve On 9 Apr 2013, at 13:04, mauro <[email protected]> wrote: > Hi, > > as an alternative, would it be possible to have several independent nodes > persisting their sessions into a remote and shared database, thus a third > "listener" application would load the database content in memory as an > entire session, combining all persisted sessions? > > Is there an out-of-the box way to reach that? > > > Br, > Mauro > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Shared-Facts-across-nodes-tp4023210p4023257.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
