In this chapter we've learned about various integration points available in Drools. The Drools Camel module allows us to build very lightweight, platform-agnostic, and quick-to-write clients that can execute rules remotely. It can be provided as a service for our customers who require more fine-grained integration with our rules. For example, to provide the service with a different UI or add their own services on top of it. Another use case might be if we don't want to share our rules with our customers; we just want to give them the ability to execute them.
We've learned that it is better to give the rules/processes a different life cycle than the rest of the application. The rules and processes tend to change more often. We know how to build a KnowledgeBase instance externally and how to dynamically reload it while the application is running.
We've also seen an overview of the Drools Spring integration that allows us not only to define Spring beans but also to work with them through...