Rule Services

  • Updated

Running Rules from a reusable service layer

Key Points

  • Rule execution occurs only on the Business Rule Server(s)
  • Rule execution can scale-out with demand by spreading load across a server farm
  • A single, generic, rule-processing web service interface can be reused for many different business problems
  • Many different consuming applications and platforms can reuse the same rule-processing web service interface
  • State is passed in the request and the response usually contains modified state and/or related messaging
  • Rule engine instances are created using irSDK code within the .NET web service
  • Business Rule Servers pull a fresh copy of the rules only as needed from the irCatalog Server
  • Multiple Business Rule Servers can use a single irCatalog Server
  • For smaller-scale implementations, the Catalog can be hosted on a Business Rule Server
  • In scale-out and high-availability scenarios, a load balancer can be used to spread requests across a farm of servers

 Running Rules with a Service-Oriented Architecture


Scaling-out the Service-Oriented Architecture to meet growing demand


Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.