Application Architectures

  • Updated


This section contains examples of common architectural patterns that are used with InRule implementations. Please be aware that many other configurations are possible.

  • Rule Services - The most typical approach used to integrate InRule. A custom developed web service exposes rule execution to multiple consuming applications and user interfaces
  • Web Applications - Typical web application with InRule running locally on each web server in a farm
  • ESB and Messaging - Using InRule as an endpoint for an Enterprise Service Bus, where many disparate systems may reuse a rule service by passing messages to the service
  • Job Scheduling and Batch Processing - Running rules against large volumes of data
  • Desktop and Disconnected Applications - Running rules locally on desktops, laptops, or Windows tablets, even when disconnected from the enterprise network

Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.