--- In [email protected], "htshozawa" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], "Rob Eamon" > <reamon@> wrote: > design/solution "might" be use both of these styles. > > > > Some say that "request customer info" is an event. I understand > the > > point of view but I believe events are more along the line > > of "customer info changed" or "order placed" or "inventory below > > threshold" or other such activity. > > > I view "order part" more in line with the business event, > while "customer info changed" is more of a technical event. > > Using a simple REA methodology to find events, an contracts between > two agents would be more of "keep inventory at xxx" and a business > event associated with the contract to fulfill that commitment would > be "order yyy parts". "inventory below threshold" to me is more of > a notification or information (technical) event based on the stated > of the inventory that may be used to invoke a business event.
"Keep inventory at xxx" seems like a policy to me, not an event. The example events seem like they are event that the business cares about. Why would "inventory below threshold" be a technical event? To me that seems to be about as business related as one can get. > Agreed on "-oriented" and "-driven". But should SOA consider events > or just services. An *architecture* should consider services, events and other principles and approaches. Service-orientation is but one aspect--one should not use the SOA label as an umbrella term for things that clearly have nothing to do with service orientation, IMO. -Rob
