When OpenRules customers build complex decision support applications, they usually avoid using large monolithic decision models. Instead, they build libraries of small decision microservices that cover the majority of domain-specific business functions. Then they use these microservices to assemble larger decision services. Like in LEGO you construct large objects (vehicles, buildings, etc.) from smaller interlocking parts, with OpenRules you construct large decision services out of small decision microservices which can be reused to build other decision services. Sometimes such microservices require domain-specific decision tables and even supporting Java libraries.
The general architectural schema of a domain-specific library of decision microservices is shown above. It includes multiple decision models that automate smaller business goals and are being tested as stand-alone apps and deployed as loosely-coupled decision services. It also includes a special Orchestration Decision Model that describes how to orchestrate other decision services.
OpenRules provides a sample of such a library for the Loan Origination domain. It is described at Loan Services.
Decision Intelligence Platform 