Re: [rules-users] Time to Scale some Drools
There will be some differences based on the underlying implementations
that you choose. Drools grid will be just a common way to use those
technologies. Right now I'm focused in hosting/access (using diferent
transports) not in caching, but this could be easily added. About
gridgain, I'm willing to test their drools integration and provide
that solution integrated with grid too. As far as I saw, gridgain it's
a map reduce solution, so I'm looking forward to some ode running
using it.
Greetings!
- CTO @ http://www.plugtree.com
- MyJourney @ http://salaboy.wordpress.com
- Co-Founder @ http://www.jbug.com.ar
- Mauricio "Salaboy" Salatino -
On Jul 1, 2010, at 1:31, tolitius <webakaunt(a)gmail.com> wrote:
Hey Mauricio,
Different SLAs for different clients. But the most sensitive one
is a 60
milliseconds transaction round trip.
I know you were working on "grid", maybe it is too early to ask,
but how
would that be different from already existing / mature solutions:
placing
kbases to Tarraccota / Hazelcast / Gemfire, and spicing it up with
GridGain
for the hosting / access?
Thank you,
/Anatoly
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Time-to-Scale-some-Dr...
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users