Architecture

OpenRules Decision Manager helps enterprises develop operational decision services for their decision-making business applications. The top-level architecture is shown on the above picture where a stateful decision-making application invokes stateless operational decision services. These services are based on business decision models usually created and maintained by business analysts in the Rules Repository using only familiar tools such as Excel (or Google Sheets) and a file manager.

Lifecycle1

Tested decision models can be deployed on-premise or on cloud using the standard frameworks provided by major vendors:

DeploymentSchema

OpenRules Decision Manager supports Serverless Architecture for Decision Microservices. With a push of a button it can deploy decision models as microservices using different deployment options described here.

To support Service Orchestration of decision services it supports special decision tables for assembling new decision services using the existing decision services with orchestrating logic described in business rules.

To support Choreography of decision services with event streams you may use OpenRules  State Machines.

OpenRules Decision Manager supports the development of domain-specific libraries of decision services as described on the following diagram:

Read more by analyzing and executing the Loan Origination decision models.

P.S. If you are interested to know how the OpenRules AWS Tracker works you may look at this diagram