Real-time decisions with BRMS

The standard deployment scenario for a BRMS application includes the following steps:

1. Create POJO fact classes.
2. Creating business rules.
3. Use the KIE API to create a KieContainer or the production memory, which is a repository holding the whole knowledge of the application. 
4. Create a KieSession object to maintain a conversation state with the Business Engine.
5. Insert POJO Facts in the session.
6. Fire rules.
7. Handle Facts.

For an external application, there are various mechanisms to interact with a business rule:

• The fat jar approach: This is the possibility given to developers to incorporate rules in their applications, code and provide a single deployment unit. Once a rule or code changes, the whole package needs to be redelivered. This option relies on the KieService API provided to load business rules from the application classpath.
• The second option is to connect remote Maven repositories; in this case, the KieScanner pulls artifact releases periodically, and the KieServices...