Menu
When is a Business Rules Engine used?
What is the difference between Business Rules Engines and scripting/configuration/customization
721
For software developers, a rule engine is useful only if it liberates them from expressing the rule in the code. In order to avoid this pitfall, it is commonly accepted that we should use rule engines only if appropriate, or not use them at all. Over the past decades, that has become a self-fulfilling prophecy.
A business rule engine (BRE) is a specific collection of design-time and runtime software that enables an enterprise to explicitly define, analyze, execute, audit and maintain a wide variety of business logic, collectively referred to as “rules.” A BRE can be purchased independently or comes embedded in a business ...
One of the main benefits of using a business rules engine is that updates to the rules do not require making updates to the rest of the application code. This functionality helps developers: Make it easier to maintain the application. Keep the application flexible as the needs of the business change.
Business Rules Engine is a suite of services, components, and objects that apply advanced logic and automate complex decision-making. The engine contains three core tools: expression sets, decision matrices, and decision tables.
A business rules engine, or a business rules management system, should be used when you are trying to implement a decision in your code. But not just any decision. A decision that:
These are the kinds of decisions that pay off the use of a business rules management system. Don't start with the rules, start with the DECISIONS.
Business rules are verbose (so business people find them easier to read), declarative not procedural and atomic (so they can be stored, managed and reused like data in a database).
More on why to use business rules here in this piece on why I believe in business rules.
176
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
