With regards failover, there is session persistence, but you won't have a 'hot' failover node to switch to there. However, if your primary servers fail for some reason, you could bring up another instance to take over that session.
There may be issues if you have a CEP environment with realtime streaming data passing through. You may not be able to afford the performance impact of persisting the state of working memory. A number of those environments need to replay events into the failover system. Using a queue system, you could be streaming events into both live and failover systems, but whether that's workable may depend on your specific case. For instance, in an email system, you wouldn't want live & failover systems both sending emails. Hopefully those give you some ideas… :) On 9 Apr 2013, at 14:18, mauro <mdurant...@gmail.com> wrote: > Steve, > > the system is not implemented yet, but that's what I'm worried about, you're > right. > > I'll take a look at CEP and distributed queues.. haven't thought of that > before. > > Moreover, does Drools provide any failover solution? > > Thanks for the light!! > Mauro > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Shared-Facts-across-nodes-tp4023210p4023261.html > Sent from the Drools: User forum mailing list archive at Nabble.com. > _______________________________________________ > rules-users mailing list > rules-users@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-users _______________________________________________ rules-users mailing list rules-users@lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users
