Reasoning for using rule engines

This is rather a general question. But I'm trying to understand the concept of using a tool and why this tool is needed. I keep spinning.

q) Why are the rules needed?

I read about the mechanisms of the Drools and ILOG rules, and it’s still unclear if I understand what benefits the organization can use with these tools.

q) Is it just giving business users the ability to run queries (called rules) into a database (repository)?

Does this extra piece of s / w not lead to more money spent on licenses and support compared to the benefits achieved?

We always have all the applications that do the same.

Example: If sales are <$ 5,000,000, then submit the order = No

The above is an example of business logic. This is easy to implement in the program. So what is the advantage of going through the rule engine?

Any input would be wonderful! Thank.

+5
source share
2 answers

You looked at this document: Why should I use the rules engine?

This is pretty clear when you need to use and not use the rule engine.

Take a look at these two paragraphs:

1.2.5. Strong and loose connection

, , " " " " . , "" "" , , . " " "" . , "" ..; , ( ) . , , , , . . , , . , , , .

, , , - . , , . . , , .       --

,

+2

- -. - , , , . , , .

. , , . , , .

, :)

+1

All Articles