评估业务规则引擎的标准
我们正在购买业务规则引擎。 我们希望使我们的核心应用程序能够针对需求略有不同的不同客户进行定制。 真正进行定制的人是分析师。 即技术熟练的非程序员（通常拥有科学学位）。
评估业务规则引擎的标准是什么？ 有开源的和商业的吗？ 您在易用性、文档、支持、价格等方面的体验如何。
我们的应用程序是用 Java 编写的。
We are shopping for Business Rules Engines.
We want to make our core application customizable to different customers with slightly different requirements.
The people who would actually do the customizations are analysts. I.e. non-programmers who are technically skilled (usually have a degree in sciences).
What are the criteria to evaluate business rules engines?
Are there open source and comercial ones?
What are your experiences in ease of use, documentation, support, price, etc.
Our app is in Java.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我在业界领先的规则引擎担任顾问近三年。 您将为商业规则引擎支付大量费用，并且需要确定您可能获得的功能和支持是否物有所值。 所有规则引擎供应商都会声称他们的规则引擎是最好的。 我能给您的最好建议是为您考虑的每个规则引擎制作一个原型，该原型的范围有限，但代表您需要的功能。 不要让销售人员只向您展示精美的演示； 您应该积极构建原型。 我见过太多人购买规则引擎，但实际上并不知道他们购买的是什么。 就我个人而言，如果您热衷于规则引擎，我会选择其中一种开源规则引擎（有人已经提到过 Drools）。 然而，我会认真考虑与规则引擎一起不使用规则引擎的可能性。 最初使用规则引擎可能会节省时间（忽略学习曲线），但从长远来看，自定义解决方案可能更能满足您的特定需求。
以下是 Martin Fowler 网站上与您的问题相关的几个链接：
I worked as a consultant for a leading rule engine in the industry for close to three years. You will pay a LOT of money for a commercial rule engine and need to decide if the features and support you potentially receive are worth the price. All rule engine vendors will claim theirs is the best hands down; the best advice I can give you is to do a prototype with each rule engine you're considering that is limited in scope, but representative of the features you need. Do NOT let sales people just show you a fancy demo; YOU should actively build the prototype. I have seen too many people buy a rule engine that really have no idea what it is they're buying. Personally, I would opt for one of the open source rule engines (someone has already mentioned Drools) if you have your heart set on a rule engine. However, I would seriously consider alongside rule engines the possibility of not using a rule engine. You may save time initially with a rule engine (ignoring the learning curve), but a custom solution is likely to be superior in the long term to meet you specific needs.
Here are a couple links from Martin Fowler's website that are relevant to your question:
Drools（以前是 Drools，然后是 JBoss Rules，然后又是 Drools）是一个非常好的开源规则引擎绝对值得一看。
在我看来，评估规则引擎的最佳标准是：
多个规则引擎都具有业务规则管理系统 (BRMS)，Drools 也不例外。 这使得非技术人员的部署变得更加容易。
通过网络上的文档和教程，甚至通过 IRC 频道，对 Drools 提供了良好的支持。
我还使用了 IBM Websphere Process Server 附带的规则引擎，发现它也非常好（尽管价格昂贵）。
Drools (used to be Drools then JBoss Rules then Drools again) is a very good open-source rules engine and definitely worth a look.
To my mind the best criteria to evaluate a rules engine are:
Several Rules Engines have Business Rules Management Systems (BRMS) and Drools is no exception. This makes deployment much easier for non-techies.
There is good support for Drools via docs and tutorials on the web and even via the IRC channel.
I've also used the Rules Engine that comes with IBM Websphere Process Server and found that to be quite good as well (although pricey).
我与许多商业供应商合作，与马丁不同，我与他们的许多客户交谈。 现实情况是，早在减少维护和增加业务用户参与的好处开始发挥作用之前，业务规则管理系统就在第一个项目中发挥了作用并回报了学习曲线等方面的投资。
Drools 作为一个优秀的开源解决方案，领先的商业产品有：
IBM/ILOG 规则（.Net、Java 和 COBOL）
FICO Blaze Advisor（.Net、Java 和 COBOL）
InRule技术（.Net）
创新软件 (Java)
Oracle 和 SAP 的平台上都有越来越完善的规则引擎。
我在 http://jtonedm.com/category/ 上查看了许多新版本以及少数产品产品新闻/
Forrester 有一份关于业务规则的不错的 Wave 报告，我推荐，并且我的网站上有一篇文章讨论它（我会链接到该报告，但 stackoverflow 还不让我添加第二个链接）-如果您需要答案，请与我联系。
I work with a lot of commercial vendors and, unlike Martin, speak to a lot of their customers. The reality is that business rules management systems do work and repay the investment in learning curve etc in the first project, long before the benefits of reduced maintenance and increased business user involve start kicking in.
Drools is excellent as an open source solution and the leading commercial products are:
IBM/ILOG Rules (.Net, Java and COBOL)
FICO Blaze Advisor (.Net, Java and COBOL)
InRule Technology (.Net)
Innovations Software (Java)
Oracle and SAP both have rules engines in their platforms that are more and more complete.
I review a lot of new releases as well as minority products at http://jtonedm.com/category/product-news/
Forrester has a nice wave report on business rules that I recommend and there is a post on my site discussing it (which I would link to but stackoverflow won't let me add a second link yet) - contact me if you want answers.
许多人决定他们需要一个规则引擎，他们想要的是一个完整的工作流管理过程，其中包括作为执行管道一部分的规则引擎。
工作流程是动作的有向图。 操作是指发生的事情，例如规则集、计算、甚至 Web 服务调用。 您应该能够有一个可以调用其他工作流程的操作。
这允许您的业务分析师进行整个流程的实现，而不仅仅是执行简单的 if-then-else（哈哈，一些商业规则引擎甚至不能做 else！请参阅有关在决定之前评估选项的评论）规则，无论是简单的顺序规则或 FCIRE（前向链接推理规则引擎）。 大多数业务分析师发现简单的顺序规则集更容易思考。 它需要在工作流程级别完成，因为 BA 解释为规则的第三方倾向于在很少通知的情况下更改其整个决策/接受/拒绝/domagick 流程。
Many people decide that they want a rule engine, and what they want is an entire workflow management process that includes rule engines as part of the execution pipeline.
A workflow is a directed graph of actions. Actions are things that happen, e.g., rulesets, calculations, web service calls even. You should be able to have an action that can call other workflows.
This allows your business analysts to do entire-process implementations, not just do simple if-then-else (hah, some commercial rule engines can't even do else! see the comment about evaluating options before deciding) rules, be it simple sequential rules or FCIRE (forward chaining inference rule engine). Most business analysts find simple sequential rulesets easier to think about. It needs to be done at the workflow level because the third parties that the BAs interpret into rules have a tendency to change their entire decision/acceptance/rejection/domagick processes with very little notice.