📄️ Application Architectures
Common architectural patterns for InRule implementations: Rule Services, desktop apps, ESB and messaging, batch processing, and web apps.
📄️ Rule Services
Run rules from a reusable, scalable service layer on dedicated Business Rule Servers, reusable across applications.
📄️ Web Applications
Run InRule in-process on a web application's server using irSDK, with each load-balanced server pulling its own copy of the rules.
📄️ ESB and Messaging
Integrate InRule with an Enterprise Service Bus, running rule execution on dedicated Business Rule Servers.
📄️ Job Scheduling and Batch Processing
A job scheduler queues rule requests, spreading them across a farm of rule servers for batch processing.
📄️ Desktop and Disconnected Applications
Run rules locally on a desktop, laptop, or Windows device with no network connection, using irSDK and a locally stored rule file.