On the Event-Decision Architecture (edA)

Reading Time: < 1 minute

TIBCO’s Don Adams has been mentioned in an Asian IT article describing the “Event Decision Architecture” (hereafter edA to avoid confusion with vanilla Event Driven Architectures…). This approach stresses the importance of matching events (both simple and derived / complex) to high speed decision rules. This approach is supported in TIBCO BusinessEvents which allows for:

  1. Multiple channels and types of events…
  2. … executing in multiple Inference Agents (Event Processing Agents on an Event Processing Network)…
  3. … where Events drive Production Rules with associated (shared) data…
  4. … and event patterns (complex events) are derived from the simple events and also drive Production Rules via inferencing…
  5. … to lead to “real-time” decisions.

Of course, the concept of Event-Decisions is very relevant to EDA. Indeed, some might say EDA “subsumes” edA. However, there is not much recognition yet for the importance of “decision rules” alongside “events”.