OpenRules Platform

Relational Database Integration

Rule DB – Architecture

Rule DB supports both traditional application-managed SQL and a direct model in which selection logic and business rules live together in the decision repository.

Two approaches

Choose where SQL selection belongs.

Rule DB integrates SQL queries into a rule-based decision-management system using either SQL Outside Rules or SQL Inside Rules.

Rule DB database-to-rules architecture
Rule DB integration architectureOpen full size ↗

Traditional integration

SQL outside rules creates intermediate objects.

Traditionally, an application uses SQL to create objects extracted from the database—potentially millions of them—and invokes a rule engine for individual objects or collections.

Traditional integration with SQL outside the rule engine
Traditional SQL-outside-rules architectureOpen full size ↗

Direct integration

SQL inside rules keeps selection with the model.

Rule DB removes unnecessary intermediate objects. Record selection and business logic can both be represented in the rules repository.

Pure selection logic moves from SQL into an Excel-based DataSQL table, while business analysts concentrate on business logic in decision tables. See the introductory example or the more complete SQL Inside Rules model.

Rule DB architecture without intermediate application objects
SQL-inside-rules architectureOpen full size ↗
Migration from SQL selection to DataSQL and business rules
From SQL query to decision tablesOpen full size ↗

Try Rule DB

Build a decision model that works directly with your data.

The free evaluation includes Rule DB and ready-to-run database examples.