Scenario: The end user wants to define actions for a set of data change events that occur in the system. These actions must be customizable. I have a few questions regarding this below:
My first questions are: how can monitoring data change and trigger events from the database level? since there is no single record in the database. Possible solutions that I know of are DB triggers, change tracking, and changing data capture. Are they really a good choice as they are all based on the Pull model?
Who should observe these events? Should we put them on the table and choose from them one by one?
Is this a suitable option for integrated event handling?
It seems that configurability of actions can arise directly from any rule engine, such as drools, flexrule, etc. Is the right approach? There are many blogs that say the rule engine is a poor choice.
source
share