规则引擎与 CEP
场景：最终用户想要定义对系统内发生的一组数据更改事件的操作。这些操作应该是可配置的。我对此有几个问题：
我的第一个问题是我们如何监控数据变化和数据变化？从数据库层引发事件？因为没有单点进入数据库。据我所知，可能的解决方案是数据库触发器、更改跟踪和更改。更改数据捕获。它们真的是好的选择吗，因为它们都基于 Pull 模型？
谁应该观察这些事件？我们应该把它们排在一张桌子上，然后从那里一一挑选吗？
这是复杂事件处理的正确用例吗？
很明显，动作的可配置性可以直接来自任何规则引擎，如 drools、flexrule 等。这是正确的方法吗？有很多博客都说规则引擎是一个糟糕的选择。 ？
Scenario: The end user wants to define actions on set of data change events that happen within the system. These actions should be configurable. I have few questions regarding it below:
My first questions is how can we monitory data changes & raise events from database tier? as don't have single point entry to database. Possible solutions which I know of is DB Triggers, Change Tracking & Change Data Capture. Are they really good choices as they are all based on Pull model?
Who should observe these events? Should we queue them in a table and pick them from there one by one?
Is it a proper use case of Complex Event Processing?
It seems clearly that configurability of actions can come directly from any Rules engine like drools, flexrule etc. Is it the right approach? There are many blogs that talk about rules engine being bad a choice.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论