+/- 1 + on the numbering POV. And on the notion that EDA is something new.
- on the characterization of EDA. Just as SOA is not simply web services neither is EDA simply a messaging style. It is architecture centered around the notion that business-related events are of enough importance as to be addressed at the architectural level rather than dealt with as a lower-level technical detail. I offer this example. A car crashes into a tree. After a time, the driver files a claim with the insurance company. The company processes the claim and makes payment. Insurance companies have found that the faster that claims are settled, the lower the payout [editor note: no comment on causality vs. correlation here]. So the insurance company strives to settle claims as quickly as possible. What is the significant business event here? Is it when the adjuster is notified by the claims system? Is it when the claim hits the processing system? Is it when the claim is entered into the claim system? It was when the car hit the tree. Which can, depending upon the circumstances, be far in advance of any of the other candidate event points. Clearly the technology now exists to do capture that early event (plug into OnStar and you're set!), but if one thinks of events as something that is simply on the ESB or handled by MOM, then we miss things. Event orientation at the higher levels of architecture-- asking what are the significant business level events--can make just has much impact as service orientation. At least that's the theory! :-) -Rob
