My preference is option 1 … using a Spring application with a class which wraps a knowledge base / session. This has the advantage that sometimes I really do want to be able to mix up rules results with logic that I want to implement in Java code.
There's obviously a performance impact if you additionally marshall to a separate Drools server, but not a huge amount. The decision should be more about whether you expect all business logic to be implemented in the Drools rules or a combination of rules and business logic code. Steve On 6 Sep 2013, at 00:15, srikanthmalli <[email protected]> wrote: > Hi, > > I am trying Drools/Guvnor for very first time, we are planned to do Rule > Authoring in Guvnor, compile, build and download the package to “Rule > Package Directory”. > > Now the question I am having is, what is the best way to integrate Drools > with our Java application? > Option 1) Build the knowledge agent and start inserting the facts into > memory for rule evaluation in our application. In this case Drools engine > use JVM same as application JVM. > Option 2) Have a Drools Server which builds the knowledge agent, and > application can send the requests to Drools Server for rule evaluation using > REST API. Rules will be executed in separate JVM than application JVM. > > I also wondering is there any performance (in terms of execution time) > difference between the options mentioned above? > > Could you please also let me know if I am thinking in the right direction? > > -Sri > > > > -- > View this message in context: > http://drools.46999.n3.nabble.com/Integrate-Drools-with-Java-application-need-recommendations-tp4025834.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
