We have covered all the important aspects of using Drools as a rule engine. We've explored stateless and stateful Kie Sessions and interaction with business processes, and seen how complex event processing is managed. The last step we need to take is to understand the different ways Drools can interact with the rest of our application.
Drools is a framework; as such, it can interact with other frameworks in as many ways as we can imagine. In the next sections, we will discuss some of the most common design and architecture approaches to integrating Drools with the rest of our design, including some pros and cons for each approach. We will cover an in-detail explanation of:
Types of Drools integration and architecture considerations
How to integrate Drools with popular integration frameworks such as Spring and Camel
Available examples of integrations, such as the Kie Server