官术网_书友最值得收藏!

When not to use a rule engine

Every project, in one way or another, can benefit from using business rules. They are highly performing, easy to change, and self-explanatory software components. However, there are a group of conditions that a project might have that would make use of business rules a bit of overkill. Some of the characteristics that make a project benefit the least from business rules are shown in the following:

  • There are very few, self-contained rules involved in the project: If the business rules identified in the requirement gathering are very simple and span about one or two objects at most, we don't need a rule engine to run them. A good rule of thumb is that if we can write the business rules that we need as the pseudo code in less than a page and with less than two nested if-then clauses, we might not need a rule engine at this particular time.
  • The business logic doesn't change often: If changing rules at runtime is not going to be needed but the logic is still complex, a rule engine might still be a good idea. However, if the complexity behind the rules is not that high and we can assume it will remain that way for a long time, we might not need a rule engine.
  • A very strict control of the execution flow is crucial for the application: As we stated before, a sequence-flow control is not provided when we execute our business rules. If the business logic behind the business rules depends a lot on a strict set of steps that need to be executed sequentially, business rules might not be the right fit. However, if it does change frequently, perhaps a business process would be worth considering.

It is still a responsibility of the project team to determine whether business rules might be a good fit even if these conditions are met. After all, our experience can lead us to think that the amount of rules has a big chance of growing in the future or there might be situations where the rules will eventually need to change more frequently. Each project has its own unique characteristics and it might be that a project with no need for business rules right now cannot be thought without them in the future.

主站蜘蛛池模板: 津市市| 三亚市| 浪卡子县| 凤城市| 特克斯县| 巴林左旗| 凤翔县| 宜川县| 陆河县| 红安县| 东辽县| 祁连县| 灌阳县| 宿迁市| 攀枝花市| 乌拉特中旗| 上虞市| 油尖旺区| 开平市| 博罗县| 红原县| 克什克腾旗| 德阳市| 清新县| 竹北市| 文化| 洪泽县| 长沙县| 甘肃省| 额尔古纳市| 阿城市| 万盛区| 朝阳区| 桐庐县| 金坛市| 南漳县| 建水县| 张家港市| 烟台市| 宜阳县| 郸城县|