1. What are the options to scale? If many rule requests are coming from different nodes ( server nodes ) OR many rule requests are coming from the same node, but with a very high frequency: WHAT ARE THE BEST PRACTICE(S) to: Create Expose Access All the knowledge artifacts? ( KnowledgeBase, Session, etc... ) Guvnor is not production ready, hence I am looking for ways / best practices with production ready components. 2. I understand that "session creation is very light", but how light? We have certain SLAs in milliseconds for the whole "request / response" travel, which would include throwing facts into the engine and getting results. 3. Seems like caching a KnowlegeBase ( e.g. GemFire, Terracotta, etc.. ) across nodes would be one way to go, what are others? 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

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