- Mastering JBoss Drools 6
- Mauricio Salatino Mariano De Maio Esteban Aliverti
- 388字
- 2021-07-09 19:58:41
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.
- 后稀缺:自動(dòng)化與未來工作
- Hands-On Machine Learning on Google Cloud Platform
- Dreamweaver CS3網(wǎng)頁設(shè)計(jì)50例
- 機(jī)器學(xué)習(xí)與大數(shù)據(jù)技術(shù)
- 數(shù)據(jù)產(chǎn)品經(jīng)理:解決方案與案例分析
- PostgreSQL Administration Essentials
- Blender Compositing and Post Processing
- Implementing AWS:Design,Build,and Manage your Infrastructure
- 傳感器與新聞
- Learning Azure Cosmos DB
- Hands-On Reactive Programming with Reactor
- Godot Engine Game Development Projects
- LMMS:A Complete Guide to Dance Music Production Beginner's Guide
- 水晶石影視動(dòng)畫精粹:After Effects & Nuke 影視后期合成
- 網(wǎng)絡(luò)脆弱性掃描產(chǎn)品原理及應(yīng)用